minor fixes

Author: itsjerryokolo

website/pages/en/cookbook/sorting.mdx

@@ -4,9 +4,11 @@ title: GraphQL Sorting Strategies
 
 ## Sort by IDs
 
-When creating subgraphs in The Graph, it's important to consider the type of ID used for your entities. This choice can have a significant impact on the performance and ease of use of your subgraph.
+When creating subgraphs in The Graph, it's important to use Bytes! as ID for your entities. This can have significant impact on the performance and ease of use of your subgraph.
 
-If accurate sorting is desired, both Strings and Bytes for IDs are not optimal as the sorting is done non-sequentially which can lead to unexpected results. If attempting to sort by id of type "ID" (which is a string), the ordered sequence might look like this:
+Unless for cases like nft traits or unique names where a type ID (which is a string) would be more appropriate.
+
+If accurate sorting of numerical values is desired, both Strings and Bytes for IDs are not optimal as the sorting is done non-sequentially which can lead to unexpected results. If attempting to sort by id of type "ID" (which is a string), the ordered sequence might look like this:
 
 schema.graphql:
 
@@ -116,7 +118,7 @@ Query Response:
 }
 ```
 
-## Ideal Sorting Strategy of IDs
+## Ideal Sorting for Numerical Values
 
 To improve the sorting, creating another property on the entity that is a BigInt (in this example it is tokenId) will allow for sorting to be optimized sequentially.