PCX Review

Author: Oxyjun

src/content/docs/autorag/configuration/metadata-filtering.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 Metadata filtering narrows down search results based on metadata, so only relevant content is retrieved. The filter narrows down results prior to retrieval, so that you only query the scope of documents that matter.
 
-Here is an example of metadata filtering in [Workers Binding](/autorag/usage/workers-binding/) but it can be easily adapted to use the [REST API](/autorag/usage/rest-api/) instead.
+Here is an example of metadata filtering using [Workers Binding](/autorag/usage/workers-binding/) but it can be easily adapted to use the [REST API](/autorag/usage/rest-api/) instead.
 
 ```js
 const answer = await env.AI.autorag("my-autorag").search({
@@ -38,7 +38,7 @@ You can currently filter by the `folder` and `modified_date` of an R2 object. Cu
 
 The directory to the object. For example, the `folder` of the object at `llama/logistics/llama-logistics.mdx` is `llama/logistics/`. Note that the `folder` does not include a leading `/`.
 
-Note that `folder` filter only includes files exactly on that folder, so files in subdirectories are not included. For example, specifying `folder: "llama/"` will match files in `llama/` but does not match files in `llama/logistics`.
+Note that `folder` filter only includes files exactly in that folder, so files in subdirectories are not included. For example, specifying `folder: "llama/"` will match files in `llama/` but does not match files in `llama/logistics`.
 
 ### `modified_date`
 
@@ -50,7 +50,7 @@ You can create simple comparison filters or an array of comparison filters using
 
 ### Comparison filter
 
-You can compare a metadata attribute (e.g. `folder` or `modified_date`) with a target value using a comparison filter.
+You can compare a metadata attribute (for example, `folder` or `modified_date`) with a target value using a comparison filter.
 
 ```js
 filters: {
@@ -89,7 +89,7 @@ Note the following limitations with the compound operators:
 - No nesting combinations of `and`'s and `or`'s, meaning you can only pick 1 `and` or 1 `or`.
 - When using `or`:
   - Only the `eq` operator is allowed.
-  - All conditions must filter on the **same key** (e.g. all on `folder`)
+  - All conditions must filter on the **same key** (for example, all on `folder`)
 
 ## Response
 

src/content/docs/autorag/how-to/bring-your-own-generation-model.mdx

@@ -18,7 +18,7 @@ import {
 
 When using `AI Search`, AutoRAG leverages a Workers AI model to generate the response. If you want to use a model outside of Workers AI, you can use AutoRAG for search while leveraging a model outside of Workers AI to generate responses.
 
-Here is an example of how you can use an OpenAI model to generate your responses. This example is done using [Workers Binding](/autorag/usage/workers-binding/) but can be easily adapted to use the [REST API](/autorag/usage/rest-api/) instead.
+Here is an example of how you can use an OpenAI model to generate your responses. This example uses [Workers Binding](/autorag/usage/workers-binding/), but can be easily adapted to use the [REST API](/autorag/usage/rest-api/) instead.
 
 ```ts
 import { openai } from "@ai-sdk/openai";

src/content/docs/autorag/how-to/multitenancy.mdx

@@ -19,7 +19,7 @@ customer-a/contracts/
 customer-b/contracts/
 ```
 
-When indexing, AutoRAG will automatically store the folder path as metadata under the `folder` attribute. It’s recommended to enforce folder separation during upload or indexing to prevent accidental data access across tenants.
+When indexing, AutoRAG will automatically store the folder path as metadata under the `folder` attribute. It is recommended to enforce folder separation during upload or indexing to prevent accidental data access across tenants.
 
 ## 2. Search Using Folder Filters
 

src/content/docs/autorag/how-to/simple-search-engine.mdx

@@ -5,11 +5,11 @@ sidebar:
   order: 5
 ---
 
-Using the `search` method you can implement a simple but fast search engine. This example is done using [Workers Binding](/autorag/usage/workers-binding/) but can be easily adapted to use the [REST API](/autorag/usage/rest-api/) instead.
+By using the `search` method, you can implement a simple but fast search engine. This example uses [Workers Binding](/autorag/usage/workers-binding/), but can be easily adapted to use the [REST API](/autorag/usage/rest-api/) instead.
 
 To replicate this example remember to:
 
-- Disable `rewrite_query` as you want to match the original user query
+- Disable `rewrite_query`, as you want to match the original user query
 - Configure your AutoRAG to have small chunk sizes, usually 256 tokens is enough
 
 ```ts

src/content/partials/autorag/ai-search-api-params.mdx

@@ -33,4 +33,4 @@ Returns a stream of results as they are available. Defaults to `false`.
 
 `filters` <Type text="object" /> <MetaInfo text="optional" />
 
-Narrow down search results based on metadata, like folder and date, so only relevant content is retrieved. For more details, see [Metadata filtering](/autorag/configuration/metadata-filtering).
+Narrow down search results based on metadata, like folder and date, so only relevant content is retrieved. For more details, refer to [Metadata filtering](/autorag/configuration/metadata-filtering).

src/content/partials/autorag/search-api-params.mdx

@@ -25,4 +25,4 @@ Configurations for customizing result ranking. Defaults to `{}`.
 
 `filters` <Type text="object" /> <MetaInfo text="optional" />
 
-Narrow down search results based on metadata, like folder and date, so only relevant content is retrieved. For more details, see [Metadata filtering](/autorag/configuration/metadata-filtering).
+Narrow down search results based on metadata, like folder and date, so only relevant content is retrieved. For more details, refer to [Metadata filtering](/autorag/configuration/metadata-filtering).