Skip to content

Commit c66e325

Browse files
committed
Update outdated meilisearch documentation links
1 parent ba862f3 commit c66e325

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

packages/autocomplete-client/README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,11 @@
66

77
<h4 align="center">
88
<a href="https://github.com/meilisearch/meilisearch">Meilisearch</a> |
9-
<a href="https://docs.meilisearch.com">Documentation</a> |
9+
<a href="https://www.meilisearch.com/docs">Documentation</a> |
1010
<a href="https://discord.meilisearch.com">Discord</a> |
1111
<a href="https://roadmap.meilisearch.com/tabs/1-under-consideration">Roadmap</a> |
1212
<a href="https://www.meilisearch.com">Website</a> |
13-
<a href="https://docs.meilisearch.com/faq">FAQ</a>
13+
<a href="https://www.meilisearch.com/docs/faq">FAQ</a>
1414
</h4>
1515

1616
<p align="center">
@@ -23,7 +23,7 @@
2323

2424
**Meilisearch** is an open-source search engine. [Discover what Meilisearch is!](https://github.com/meilisearch/meilisearch)
2525

26-
This library is the search client that you should use to make [Meilisearch](https://github.com/meilisearch/meilisearch) work with [autocomplete](https://github.com/algolia/autocomplete). Autocomplete, an open-source project developed by Algolia, is a JavaScript library that lets you quickly build an autocomplete experiences.
26+
This library is the search client that you should use to make [Meilisearch](https://github.com/meilisearch/meilisearch) work with [autocomplete](https://github.com/algolia/autocomplete). Autocomplete, an open-source project developed by Algolia, is a library that lets you quickly build an autocomplete experience.
2727

2828
Since `autocomplete.js` provides the possibility to use a custom `data source`, we are able to plug into it. Nonetheless, it has been created by Algolia and thus some of its components only works with Algolia.
2929

@@ -41,7 +41,7 @@ Since `autocomplete.js` provides the possibility to use a custom `data source`,
4141

4242
## 📖 Documentation
4343

44-
For general information on how to use Meilisearch—such as our API reference, tutorials, guides, and in-depth articles—refer to our [main documentation website](https://docs.meilisearch.com/).
44+
For general information on how to use Meilisearch—such as our API reference, tutorials, guides, and in-depth articles—refer to our [main documentation website](https://www.meilisearch.com/docs/).
4545

4646
For information on how to use the `autocomplete` library refer to its [documentation](https://www.algolia.com/doc/ui-libraries/autocomplete/introduction/what-is-autocomplete/). It provides all the necessary information to set up your autocomplete experience.
4747

@@ -153,7 +153,7 @@ When placeholder search is set to `false`, no results appears when the search bo
153153

154154
### Primary key
155155

156-
Specify the field in your documents containing the [unique identifier](https://docs.meilisearch.com/learn/core_concepts/documents.html#primary-field) (`undefined` by default). By adding this option, we avoid errors that are thrown in some environments. For example, In `React` particularly, this option removes the `Each child in a list should have a unique "key" prop` error.
156+
Specify the field in your documents containing the [unique identifier](https://www.meilisearch.com/docs/learn/core_concepts/documents#primary-field) (`undefined` by default). By adding this option, we avoid errors that are thrown in some environments. For example, In `React` particularly, this option removes the `Each child in a list should have a unique "key" prop` error.
157157

158158
```js
159159
{ primaryKey : 'id' } // default: undefined
@@ -186,7 +186,7 @@ genres:
186186

187187
### Matching strategy
188188

189-
`matchingStrategy` gives you the possibility to choose how Meilisearch should handle the presence of multiple query words, see [documentation](https://docs.meilisearch.com/reference/api/search.html#matching-strategy).
189+
`matchingStrategy` gives you the possibility to choose how Meilisearch should handle the presence of multiple query words, see [documentation](https://www.meilisearch.com/docs/reference/api/search#matching-strategy).
190190

191191
For example, if your query is `hello world` by default Meilisearch returns documents containing either both `hello` and `world` or documents that only contain `hello`. This is the `last` strategy, where words are stripped from the right.
192192
The other strategy is `all`, where both `hello` and `world` **must** be present in a document for it to be returned.

0 commit comments

Comments
 (0)