Mirror: The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.

docs: fix typo of normalized (#3539)

Changed files
+2 -2
docs
+1 -1
docs/graphcache/cache-updates.md
···
As we've learned [on the page on "Normalized
Caching"](./normalized-caching.md#normalizing-relational-data), when Graphcache receives an API
-
result it will traverse and store all its data to its cache in a normalised structure. Each entity
that is found in a result will be stored under the entity's key.
A query's result is represented as a graph, which can also be understood as a tree structure,
···
As we've learned [on the page on "Normalized
Caching"](./normalized-caching.md#normalizing-relational-data), when Graphcache receives an API
+
result it will traverse and store all its data to its cache in a normalized structure. Each entity
that is found in a result will be stored under the entity's key.
A query's result is represented as a graph, which can also be understood as a tree structure,
+1 -1
docs/graphcache/errors.md
···
This error occurs when the cache can't generate a key for an entity. The key
would then effectively be `null`, and the entity won't be cached by a key.
-
Conceptually this means that an entity won't be normalised but will indeed
be cached by the parent's key and field, which is displayed in the first
part of the warning.
···
This error occurs when the cache can't generate a key for an entity. The key
would then effectively be `null`, and the entity won't be cached by a key.
+
Conceptually this means that an entity won't be normalized but will indeed
be cached by the parent's key and field, which is displayed in the first
part of the warning.