docs: improve documentation by removing some typos

docs/agent-customization/fields/filter.md

@@ -13,7 +13,7 @@ Disabling filtering can be made without any code [in the field settings](https:/
 
 Filtering operators can be disabled one by one.
 
-This is used mostly for performance reasons: on big collections, it can be intesting to let users filter only on fields that are indexed in your database to avoid [full-table-scans](https://en.wikipedia.org/wiki/Full_table_scan).
+This is used mostly for performance reasons: on big collections, it can be interesting to let users filter only on fields that are indexed in your database to avoid [full-table-scans](https://en.wikipedia.org/wiki/Full_table_scan).
 
 ```javascript
 collection.replaceFieldOperator('fullName', 'Equal', null);

docs/agent-customization/relationships/under-the-hood.md

@@ -37,5 +37,5 @@ SELECT authors.id, authors.firstName, authors.lastName FROM authors WHERE id IN
 {% hint style="warning" %}
 Automatic query splitting is a very powerful tool however not all queries are created equal.
 
-In this simple example, it is a straighforward three step process, but the feature can come at the cost of performance on more complex queries.
+In this simple example, it is a straightforward three-step process, but the feature can come at the cost of performance on more complex queries.
 {% endhint %}

docs/agent-customization/search.md

@@ -6,7 +6,7 @@ In Forest Admin, pages which show lists of records have a free-text search widge
 
 Two search modes are supported: normal and extended.
 
-- All searchs start by being a "normal search".
+- All searches start by being a "normal search".
 - If the result the user is looking for is not found, it is possible to trigger an extended search from the user interface.
 
 ![Extended search call to action](../assets/search-bar-extended.png)