Fix grammatical issue in optimization guides (#1941)

This commit is contained in:
el2e10 2022-01-03 15:36:13 +05:30 committed by GitHub
parent a1fb70bbbd
commit 377c20b8b1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 4 additions and 4 deletions

View File

@ -42,7 +42,7 @@ which is why we recommend using the `PreProcessor` class to clean and split your
For **sparse retrievers**, very long documents pose a challenge since the signal of the relevant section of text
can get washed out by the rest of the document.
To get a good balance between Reader speed and Retriever performance, we splitting documents to a maximum of 500 words.
To get a good balance between Reader speed and Retriever performance, we split documents to a maximum of 500 words.
If there is no Reader in the pipeline following the Retriever, we recommend that **documents be no longer than 10,000 words**.
**Dense retrievers** are limited in the length of text that they can read in one pass.

View File

@ -42,7 +42,7 @@ which is why we recommend using the `PreProcessor` class to clean and split your
For **sparse retrievers**, very long documents pose a challenge since the signal of the relevant section of text
can get washed out by the rest of the document.
To get a good balance between Reader speed and Retriever performance, we splitting documents to a maximum of 500 words.
To get a good balance between Reader speed and Retriever performance, we split documents to a maximum of 500 words.
If there is no Reader in the pipeline following the Retriever, we recommend that **documents be no longer than 10,000 words**.
**Dense retrievers** are limited in the length of text that they can read in one pass.

View File

@ -42,7 +42,7 @@ which is why we recommend using the `PreProcessor` class to clean and split your
For **sparse retrievers**, very long documents pose a challenge since the signal of the relevant section of text
can get washed out by the rest of the document.
To get a good balance between Reader speed and Retriever performance, we splitting documents to a maximum of 500 words.
To get a good balance between Reader speed and Retriever performance, we split documents to a maximum of 500 words.
If there is no Reader in the pipeline following the Retriever, we recommend that **documents be no longer than 10,000 words**.
**Dense retrievers** are limited in the length of text that they can read in one pass.

View File

@ -42,7 +42,7 @@ which is why we recommend using the `PreProcessor` class to clean and split your
For **sparse retrievers**, very long documents pose a challenge since the signal of the relevant section of text
can get washed out by the rest of the document.
To get a good balance between Reader speed and Retriever performance, we splitting documents to a maximum of 500 words.
To get a good balance between Reader speed and Retriever performance, we split documents to a maximum of 500 words.
If there is no Reader in the pipeline following the Retriever, we recommend that **documents be no longer than 10,000 words**.
**Dense retrievers** are limited in the length of text that they can read in one pass.