Update website/pages/en/developing/creating-a-subgraph.mdx

Co-authored-by: Benoît Rouleau <[email protected]>

Author: idalithb

website/pages/en/developing/creating-a-subgraph.mdx

@@ -423,7 +423,7 @@ Before defining entities, it is important to take a step back and think about ho
 
 - All queries will be made against the data model defined in the subgraph schema and the entities indexed by the subgraph. As a result, it is good to define the subgraph schema in a way that matches the needs of your dapp.
 - It may be useful to imagine entities as "objects containing data", rather than as events or functions.
-- You define entity types in `schema.graphql`, and Graph Node will generate top level fields for querying single instances and collections of that entity type.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
 - Each type that should be an entity is required to be annotated with an `@entity` directive.
 - By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
   - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.