Update website/pages/en/querying/querying-best-practices.mdx

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

Author: idalithb

website/pages/en/querying/querying-best-practices.mdx

@@ -196,9 +196,7 @@ GraphQL became famous for its "Ask for what you want" tagline.
 For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
 - When querying GraphQL APIs, always think of querying only the fields that will be actually used.
-- A common cause of over-fetching is collections of entities. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user.
-- Queries should always be set first explicitly.
-  - Make sure queries only fetch as many entities as they actually need. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
 For example, in the following query: