fixes

Author: shahednasser

www/apps/book/app/learn/fundamentals/module-links/query/page.mdx

@@ -127,7 +127,7 @@ const { data: posts } = await query.graph({
 })
 ```
 
-`.*` means that all of data model's properties should be retrieved. You can also retrieve specific properties by replacing the `*` with the property name, for each property.
+`.*` means that all of the data model's properties should be retrieved. You can also retrieve specific properties by replacing the `*` with the property name for each property.
 
 For example:
 
@@ -166,7 +166,7 @@ In the example above, you retrieve all products linked to a post.
 
 ### Apply Filters and Pagination on Linked Records
 
-Consider you want to apply filters or pagination configurations on the product(s) linked to `post`. To do that, you must query the module link's table instead.
+Consider that you want to apply filters or pagination configurations on the product(s) linked to a `post`. To do that, you must query the module link's table instead.
 
 As mentioned in the [Module Link](../page.mdx) documentation, Medusa creates a table for your module link. So, not only can you retrieve linked records, but you can also retrieve the records in a module link's table.
 
@@ -199,7 +199,7 @@ const { data: productCustoms } = await query.graph({
 In the object passed to the `graph` method:
 
 - You pass the `entryPoint` property of the link definition as the value for `entity`. So, Query will retrieve records from the module link's table.
-- You pass three items to the `field` property:
+- You pass three items to the `fields` property:
     - `*` to retrieve the link table's fields. This is useful if the link table has [custom columns](../custom-columns/page.mdx).
     - `product.*` to retrieve the fields of a product record linked to a `Post` record.
     - `post.*` to retrieve the fields of a `Post` record linked to a product record.
@@ -272,7 +272,7 @@ Under the hood, Query uses one of the following methods from the data model's mo
 - `listX` if you don't pass [pagination parameters](#apply-pagination). For example, `listPosts`.
 - `listAndCountX` if you pass pagination parameters. For example, `listAndCountPosts`.
 
-Both methods accepts a filter object that can be used to filter records.
+Both methods accept a filter object that can be used to filter records.
 
 Those filters don't just allow you to filter by exact values. You can also filter by properties that don't match a value, match multiple values, and other filter types.
 
@@ -497,7 +497,7 @@ In the example above, you retrieve only deleted posts by enabling the `withDelet
 
 ## Configure Query to Throw Errors
 
-By default, if Query doesn't find records matching your query, it returns an empty array. You can add option to configure Query to throw an error when no records are found.
+By default, if Query doesn't find records matching your query, it returns an empty array. You can add an option to configure Query to throw an error when no records are found.
 
 The `query.graph` method accepts as a second parameter an object that can have a `throwIfKeyNotFound` property. Its value is a boolean indicating whether to throw an error if no record is found when filtering by IDs. By default, it's `false`.
 
@@ -536,7 +536,7 @@ const { data: posts } = await query.graph({
 })
 ```
 
-In the example above, Query throws an error either if no post is found with the ID `post_123` or if its found but its author ID isn't `author_123`.
+In the example above, Query throws an error either if no post is found with the ID `post_123` or if it's found but its author ID isn't `author_123`.
 
 In the above example, it's assumed that a post belongs to an author, so it has an `author_id` property. However, this also works in the opposite case, where an author has many posts.
 
@@ -615,7 +615,7 @@ The `validateAndTransformQuery` accepts two parameters:
     4. `order`: The fields to order the returned items by in ascending or descending order.
 2. A Query configuration object. It accepts the following properties:
     1. `defaults`: An array of default fields and relations to retrieve in each resource.
-    2. `isList`: A boolean indicating whether a list of items are returned in the response.
+    2. `isList`: A boolean indicating whether a list of items is returned in the response.
     3. `allowed`: An array of fields and relations allowed to be passed in the `fields` query parameter.
     4. `defaultLimit`: A number indicating the default limit to use if no limit is provided. By default, it's `50`.
 
@@ -631,7 +631,7 @@ As of [Medusa v2.2.0](https://github.com/medusajs/medusa/releases/tag/v2.2.0), `
 
 </Note>
 
-For example, Create the file `src/api/customs/route.ts` with the following content:
+For example, create the file `src/api/customs/route.ts` with the following content:
 
 export const queryConfigHighlights = [
   ["17", "req.queryConfig", "Pass the parsed request Query configurations to the Query graph execution."]
@@ -667,7 +667,7 @@ In the API route, you pass `req.queryConfig` to `query.graph`. `queryConfig` has
 
 ### Test it Out
 
-To test it out, start your Medusa application and send a `GET` request to the `/customs` API route. A list of records are retrieved with the specified fields in the middleware.
+To test it out, start your Medusa application and send a `GET` request to the `/customs` API route. A list of records is retrieved with the specified fields in the middleware.
 
 ```json title="Returned Data"
 {
@@ -684,6 +684,6 @@ Try passing one of the Query configuration parameters, like `fields` or `limit`,
 
 <Note>
 
-Learn more about [specifing fields and relations](!api!/store#select-fields-and-relations) and [pagination](!api!/store#pagination) in the API reference.
+Learn more about [specifying fields and relations](!api!/store#select-fields-and-relations) and [pagination](!api!/store#pagination) in the API reference.
 
 </Note>

www/apps/book/generated/edit-dates.mjs

@@ -66,7 +66,7 @@ export const generatedEditDates = {
   "app/learn/fundamentals/module-links/custom-columns/page.mdx": "2025-03-11T13:29:54.752Z",
   "app/learn/fundamentals/module-links/directions/page.mdx": "2025-03-17T12:52:06.161Z",
   "app/learn/fundamentals/module-links/page.mdx": "2025-04-17T08:50:17.036Z",
-  "app/learn/fundamentals/module-links/query/page.mdx": "2025-06-26T15:22:09.672Z",
+  "app/learn/fundamentals/module-links/query/page.mdx": "2025-06-26T15:24:54.686Z",
   "app/learn/fundamentals/modules/db-operations/page.mdx": "2025-04-25T14:26:25.000Z",
   "app/learn/fundamentals/modules/multiple-services/page.mdx": "2025-03-18T15:11:44.632Z",
   "app/learn/fundamentals/modules/page.mdx": "2025-03-18T07:51:09.049Z",

www/apps/book/public/llms-full.txt

@@ -12237,7 +12237,7 @@ const { data: posts } = await query.graph({
 })
 ```
 
-`.*` means that all of data model's properties should be retrieved. You can also retrieve specific properties by replacing the `*` with the property name, for each property.
+`.*` means that all of the data model's properties should be retrieved. You can also retrieve specific properties by replacing the `*` with the property name for each property.
 
 For example:
 
@@ -12276,7 +12276,7 @@ In the example above, you retrieve all products linked to a post.
 
 ### Apply Filters and Pagination on Linked Records
 
-Consider you want to apply filters or pagination configurations on the product(s) linked to `post`. To do that, you must query the module link's table instead.
+Consider that you want to apply filters or pagination configurations on the product(s) linked to a `post`. To do that, you must query the module link's table instead.
 
 As mentioned in the [Module Link](https://docs.medusajs.com/learn/fundamentals/module-links/index.html.md) documentation, Medusa creates a table for your module link. So, not only can you retrieve linked records, but you can also retrieve the records in a module link's table.
 
@@ -12302,7 +12302,7 @@ const { data: productCustoms } = await query.graph({
 In the object passed to the `graph` method:
 
 - You pass the `entryPoint` property of the link definition as the value for `entity`. So, Query will retrieve records from the module link's table.
-- You pass three items to the `field` property:
+- You pass three items to the `fields` property:
   - `*` to retrieve the link table's fields. This is useful if the link table has [custom columns](https://docs.medusajs.com/learn/fundamentals/module-links/custom-columns/index.html.md).
   - `product.*` to retrieve the fields of a product record linked to a `Post` record.
   - `post.*` to retrieve the fields of a `Post` record linked to a product record.
@@ -12371,7 +12371,7 @@ Under the hood, Query uses one of the following methods from the data model's mo
 - `listX` if you don't pass [pagination parameters](#apply-pagination). For example, `listPosts`.
 - `listAndCountX` if you pass pagination parameters. For example, `listAndCountPosts`.
 
-Both methods accepts a filter object that can be used to filter records.
+Both methods accept a filter object that can be used to filter records.
 
 Those filters don't just allow you to filter by exact values. You can also filter by properties that don't match a value, match multiple values, and other filter types.
 
@@ -12565,7 +12565,7 @@ In the example above, you retrieve only deleted posts by enabling the `withDelet
 
 ## Configure Query to Throw Errors
 
-By default, if Query doesn't find records matching your query, it returns an empty array. You can add option to configure Query to throw an error when no records are found.
+By default, if Query doesn't find records matching your query, it returns an empty array. You can add an option to configure Query to throw an error when no records are found.
 
 The `query.graph` method accepts as a second parameter an object that can have a `throwIfKeyNotFound` property. Its value is a boolean indicating whether to throw an error if no record is found when filtering by IDs. By default, it's `false`.
 
@@ -12604,7 +12604,7 @@ const { data: posts } = await query.graph({
 })
 ```
 
-In the example above, Query throws an error either if no post is found with the ID `post_123` or if its found but its author ID isn't `author_123`.
+In the example above, Query throws an error either if no post is found with the ID `post_123` or if it's found but its author ID isn't `author_123`.
 
 In the above example, it's assumed that a post belongs to an author, so it has an `author_id` property. However, this also works in the opposite case, where an author has many posts.
 
@@ -12683,7 +12683,7 @@ The `validateAndTransformQuery` accepts two parameters:
    4. `order`: The fields to order the returned items by in ascending or descending order.
 2. A Query configuration object. It accepts the following properties:
    1. `defaults`: An array of default fields and relations to retrieve in each resource.
-   2. `isList`: A boolean indicating whether a list of items are returned in the response.
+   2. `isList`: A boolean indicating whether a list of items is returned in the response.
    3. `allowed`: An array of fields and relations allowed to be passed in the `fields` query parameter.
    4. `defaultLimit`: A number indicating the default limit to use if no limit is provided. By default, it's `50`.
 
@@ -12695,7 +12695,7 @@ The middleware transforms these parameters to configurations that you can pass t
 
 As of [Medusa v2.2.0](https://github.com/medusajs/medusa/releases/tag/v2.2.0), `remoteQueryConfig` has been deprecated in favor of `queryConfig`. Their usage is still the same, only the property name has changed.
 
-For example, Create the file `src/api/customs/route.ts` with the following content:
+For example, create the file `src/api/customs/route.ts` with the following content:
 
 ```ts title="src/api/customs/route.ts"
 import {
@@ -12727,7 +12727,7 @@ In the API route, you pass `req.queryConfig` to `query.graph`. `queryConfig` has
 
 ### Test it Out
 
-To test it out, start your Medusa application and send a `GET` request to the `/customs` API route. A list of records are retrieved with the specified fields in the middleware.
+To test it out, start your Medusa application and send a `GET` request to the `/customs` API route. A list of records is retrieved with the specified fields in the middleware.
 
 ```json title="Returned Data"
 {
@@ -12742,7 +12742,7 @@ To test it out, start your Medusa application and send a `GET` request to the `/
 
 Try passing one of the Query configuration parameters, like `fields` or `limit`, and you'll see its impact on the returned result.
 
-Learn more about [specifing fields and relations](https://docs.medusajs.com/api/store#select-fields-and-relations) and [pagination](https://docs.medusajs.com/api/store#pagination) in the API reference.
+Learn more about [specifying fields and relations](https://docs.medusajs.com/api/store#select-fields-and-relations) and [pagination](https://docs.medusajs.com/api/store#pagination) in the API reference.
 
 
 # Read-Only Module Link