Final feedback

Author: MichaelMacaulay

website/src/pages/en/subgraphs/querying/graphql-api.mdx

@@ -30,7 +30,7 @@ GraphQL queries in The Graph target entities defined in the Subgraph schema. Eac
 
 > Note: The `query` keyword is not required at the top level of GraphQL queries.
 
-### Single Entity Queries
+### Single Entity Queries Example
 
 Query for a single `Token` entity:
 
@@ -45,7 +45,7 @@ Query for a single `Token` entity:
 
 > Note: Single entity queries require the `id` parameter as a string.
 
-### Collection Queries
+### Collection Queries Example
 
 Query format for all `Token` entities:
 
@@ -58,14 +58,14 @@ Query format for all `Token` entities:
 }
 ```
 
-### Sorting
+### Sorting Example
 
 Collection queries support the following sort parameters:
 
 - `orderBy`: Specifies the attribute for sorting
 - `orderDirection`: Accepts `asc` (ascending) or `desc` (descending)
 
-#### Standard Sorting
+#### Standard Sorting Example
 
 ```graphql
 {
@@ -76,7 +76,7 @@ Collection queries support the following sort parameters:
 }
 ```
 
-#### Nested Entity Sorting
+#### Nested Entity Sorting Example
 
 ```graphql
 {
@@ -91,7 +91,7 @@ Collection queries support the following sort parameters:
 
 > Note: Nested sorting supports one-level-deep `String` or `ID` types on `@entity` and `@derivedFrom` fields.
 
-### Pagination
+### Pagination Example
 
 When querying a collection, it is best to:
 
@@ -100,7 +100,7 @@ When querying a collection, it is best to:
 - Use the `skip` parameter to skip entities and paginate. For instance, `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities.
 - Avoid using `skip` values in queries because they generally perform poorly. To retrieve a large number of items, it's best to page through entities based on an attribute as shown in the previous example above.
 
-#### Standard Pagination
+#### Standard Pagination Example
 
 ```graphql
 {
@@ -111,7 +111,7 @@ When querying a collection, it is best to:
 }
 ```
 
-#### Offset Pagination
+#### Offset Pagination Example
 
 ```graphql
 {
@@ -122,7 +122,7 @@ When querying a collection, it is best to:
 }
 ```
 
-#### Cursor-based Pagination
+#### Cursor-based Pagination Example
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -137,7 +137,7 @@ query manyTokens($lastID: String) {
 
 The `where` parameter filters entities based on specified conditions.
 
-#### Basic Filtering
+#### Basic Filtering Example
 
 ```graphql
 {
@@ -151,7 +151,7 @@ The `where` parameter filters entities based on specified conditions.
 }
 ```
 
-#### Numeric Comparison
+#### Numeric Comparison Example
 
 ```graphql
 {
@@ -163,7 +163,7 @@ The `where` parameter filters entities based on specified conditions.
 }
 ```
 
-#### Block-based Filtering
+#### Block-based Filtering Example
 
 ```graphql
 {
@@ -175,7 +175,7 @@ The `where` parameter filters entities based on specified conditions.
 }
 ```
 
-#### Nested Entity Filtering
+#### Nested Entity Filtering Example
 
 ```graphql
 {
@@ -191,7 +191,7 @@ The `where` parameter filters entities based on specified conditions.
 
 #### Logical Operators
 
-##### AND Operations
+##### AND Operations Example
 
 The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 }
 ```
 
-##### OR Operations
+##### OR Operations Example
 
 ```graphql
 {
@@ -241,7 +241,7 @@ Global filter parameter:
 _change_block(number_gte: Int)
 ```
 
-### Time-travel Queries
+### Time-travel Queries Example
 
 Queries support historical state retrieval using the `block` parameter:
 
@@ -250,7 +250,7 @@ Queries support historical state retrieval using the `block` parameter:
 
 > Note: The current implementation is still subject to certain limitations that might violate these guarantees. The implementation can not always tell that a given block hash is not on the main chain at all, or if a query result by a block hash for a block that is not yet considered final could be influenced by a block reorganization running concurrently with the query. They do not affect the results of queries by block hash when the block is final and known to be on the main chain. [This issue](https://github.com/graphprotocol/graph-node/issues/1405) explains what these limitations are in detail.
 
-#### Block Number Query
+#### Block Number Query Example
 
 ```graphql
 {
@@ -264,7 +264,7 @@ Queries support historical state retrieval using the `block` parameter:
 }
 ```
 
-#### Block Hash Query
+#### Block Hash Query Example
 
 ```graphql
 {
@@ -278,7 +278,7 @@ Queries support historical state retrieval using the `block` parameter:
 }
 ```
 
-### Full-Text Search
+### Full-Text Search Example
 
 Full-text search query fields provide an expressive text search API that can be added to the Subgraph schema and customized. Refer to [Defining Full-text Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add full-text search to your Subgraph.
 
@@ -342,7 +342,7 @@ Entity types require:
 - `@entity` directive
 - `ID` field
 
-### Subgraph Metadata
+### Subgraph Metadata Example
 
 The `_Meta_` object provides subgraph metadata: