multiple minor fixes

Author: guimachiavelli

guides/ai/mcp.mdx

@@ -153,11 +153,14 @@ You can also request your search uses other Meilisearch features such as filters
 Search the "products" index for "chair" where the price is less than 200 and the category is "Furniture". Sort results by price in ascending order.
 ```
 
-<Capsule intent="warning" title="Important note about LLM limitation">
+<Warning>
+
+### Important note about LLM limitation
+
 Large Language Models like Claude tend to say "yes" to most requests, even if they can't actually perform them. 
 
 Claude can only perform actions that are exposed through the Meilisearch API and implemented in the MCP server. If you're unsure whether a particular operation is possible, refer to the [Meilisearch documentation](https://docs.meilisearch.com) and the [MCP server README](https://github.com/meilisearch/meilisearch-mcp).
-</Capsule>
+</Warning>
 
 ## Troubleshooting
 

learn/ai_powered_search/choose_an_embedder.mdx

@@ -29,8 +29,8 @@ Although it returns very relevant search results, the Hugging Face embedder must
 
 That said, Hugging Face can be a good embedder for datasets under 10k documents that you don't plan to update often. 
 
-<Capsule intent="note">
+<Note>
 Meilisearch Cloud does not support embedders with `{"source": "huggingFace"}`.
 
-To use  Hugging Face in the Cloud,  use [HuggingFace inference points with the REST embedder](/guides/ai/huggingface).
- </Capsule>
+To implement Hugging Face embedders in the Cloud, use [HuggingFace inference points with the REST embedder](/guides/ai/huggingface).
+</Note>

learn/multi_search/implement_sharding.mdx

@@ -3,15 +3,18 @@ title: Implement sharding with remote federated search
 description: This guide walks you through implementing a sharding strategy by activating the `/network` route, configuring the network object, and performing remote federated searches.
 ---
 
+import { NoticeTag } from '/snippets/notice_tag.mdx';
+
 import CodeSamplesMultiSearchRemoteFederated1 from '/snippets/samples/code_samples_multi_search_remote_federated_1.mdx';
 
 Sharding is the process of splitting an index containing many documents into multiple smaller indexes, often called shards. This horizontal scaling technique is useful when handling large databases. In Meilisearch, the best way to implement a sharding strategy is to use remote federated search.
 
 This guide walks you through activating the `/network` route, configuring the network object, and performing remote federated searches.
 
-<Capsule intent="tip" title="Configuring multiple instances">
+<Tip>
+## Configuring multiple instances
 To minimize issues and limit unexpected behavior, instance, network, and index configuration should be identical for all shards. This guide describes the individual steps you must take on a single instance and assumes you will replicate them across all instances.
-</Capsule>
+</Tip>
 
 ## Prerequisites
 

learn/self_hosted/configure_meilisearch_at_launch.mdx

@@ -249,11 +249,13 @@ Migrates the database to a new Meilisearch version after you have manually updat
 
 [Learn more about updating Meilisearch to a new release](/learn/update_and_migration/updating).
 
-<Capsule intent="danger" title="Create a snapshot before a dumpless upgrade">
+<Warning>
+#### Create a snapshot before a dumpless upgrade
+
 Take a snapshot of your instance before performing a dumpless upgrade.
 
 Dumpless upgrade are not currently atomic. It is possible some processes fail and Meilisearch still finalizes the upgrade. This may result in a corrupted database and data loss.
-</Capsule>
+</Warning>
 
 ### Dump directory
 

learn/update_and_migration/updating.mdx

@@ -156,9 +156,9 @@ Meilisearch should launch normally and immediately create a new `UpgradeDatabase
 
 While the task is processing, you may continue making search queries. You may also enqueue new tasks. Meilisearch will only process new tasks once `UpgradeDatabase` is completed.
 
-<Capsule intent="warning">
+<Warning>
 If after the upgrade is completed the task status is set to `failed` or Meilisearch returns internal error messages to your queries, [restart your instance from the snapshot](/learn/advanced/snapshots#starting-from-a-snapshot) you generated during step 1. You may then retry the upgrade, or upgrade using a dump. You are also welcome to open an issue on the [Meilisearch repository](https://github.com/meilisearch/meilisearch).
-</Capsule>
+</Warning>
 
 ### Using a dump
 

reference/api/batches.mdx

@@ -125,8 +125,7 @@ List of the number of tasks in the batch separated by the indexes they affect.
 
 ## Get batches
 
-<RouteHighlighter method="GET" path="/batches
-" />
+<RouteHighlighter method="GET" path="/batches" />
 
 List all batches, regardless of index. The batch objects are contained in the `results` array.
 
@@ -213,8 +212,7 @@ For example, `?uids=0` returns a batch containing the task with a `taskUid` equa
 
 ## Get one batch
 
-<RouteHighlighter method="GET" path="/batches/{batch_uid}
-" />
+<RouteHighlighter method="GET" path="/batches/{batch_uid}" />
 
 Get a single batch.
 

reference/api/documents.mdx

@@ -5,7 +5,7 @@ description: The /documents route allows you to create, manage, and delete docum
 ---
 
 import { RouteHighlighter } from '/snippets/route_highlighter.mdx'
-
+import { NoticeTag } from '/snippets/notice_tag.mdx';
 
 import CodeSamplesAddOrReplaceDocuments1 from '/snippets/samples/code_samples_add_or_replace_documents_1.mdx';
 import CodeSamplesAddOrUpdateDocuments1 from '/snippets/samples/code_samples_add_or_update_documents_1.mdx';
@@ -23,8 +23,7 @@ The `/documents` route allows you to create, manage, and delete documents.
 
 ## Get documents with POST
 
-<RouteHighlighter method="POST" path="/indexes/{index_uid}/documents/fetch
-" />
+<RouteHighlighter method="POST" path="/indexes/{index_uid}/documents/fetch" />
 
 Get a set of documents.
 
@@ -106,8 +105,7 @@ Sending an empty payload (`--data-binary '{}'`) will return all documents in the
 This endpoint will be deprecated in the near future. Consider using POST `/indexes/{index_uid}/documents/fetch` instead.
 </Warning>
 
-<RouteHighlighter method="GET" path="/indexes/{index_uid}/documents
-" />
+<RouteHighlighter method="GET" path="/indexes/{index_uid}/documents" />
 
 Get a set of documents.
 
@@ -182,8 +180,7 @@ Using the query parameters `offset` and `limit`, you can browse through all your
 ```
 
 ## Get one document
-<RouteHighlighter method="GET" path="/indexes/{index_uid}/documents/{document_id}
-" />
+<RouteHighlighter method="GET" path="/indexes/{index_uid}/documents/{document_id}" />
 
 Get one document using its unique id.
 
@@ -218,8 +215,7 @@ Get one document using its unique id.
 
 ## Add or replace documents
 
-<RouteHighlighter method="POST" path="/indexes/{index_uid}/documents
-" />
+<RouteHighlighter method="POST" path="/indexes/{index_uid}/documents" />
 
 Add an array of documents or replace them if they already exist. If the provided index does not exist, it will be created.
 
@@ -337,8 +333,7 @@ You can use this `taskUid` to get more details on [the status of the task](/refe
 
 ## Add or update documents
 
-<RouteHighlighter method="PUT" path="/indexes/{index_uid}/documents
-" />
+<RouteHighlighter method="PUT" path="/indexes/{index_uid}/documents" />
 
 Add a list of documents or update them if they already exist. If the provided index does not exist, it will be created.
 
@@ -406,10 +401,9 @@ The documents are matched because they have the same [primary key](/learn/gettin
 
 You can use this `taskUid` to get more details on [the status of the task](/reference/api/tasks#get-one-task).
 
-## Update documents with function (experimental)
+## Update documents with function <NoticeTag type="experimental" label="experimental">
 
-<RouteHighlighter method="POST" path="/indexes/{index_uid}/documents/edit
-" />
+<RouteHighlighter method="POST" path="/indexes/{index_uid}/documents/edit" />
 
 Use a [RHAI function](https://rhai.rs/book/engine/hello-world.html) to edit one or more documents directly in Meilisearch.
 
@@ -465,8 +459,7 @@ curl \
 
 ## Delete all documents
 
-<RouteHighlighter method="DELETE" path="/indexes/{index_uid}/documents
-" />
+<RouteHighlighter method="DELETE" path="/indexes/{index_uid}/documents" />
 
 Delete all documents in the specified index.
 
@@ -496,8 +489,7 @@ You can use this `taskUid` to get more details on [the status of the task](/refe
 
 ## Delete one document
 
-<RouteHighlighter method="DELETE" path="/indexes/{index_uid}/documents/{document_id}
-" />
+<RouteHighlighter method="DELETE" path="/indexes/{index_uid}/documents/{document_id}" />
 
 Delete one document based on its unique id.
 
@@ -528,8 +520,7 @@ You can use this `taskUid` to get more details on [the status of the task](/refe
 
 ## Delete documents by filter
 
-<RouteHighlighter method="POST" path="/indexes/{index_uid}/documents/delete
-" />
+<RouteHighlighter method="POST" path="/indexes/{index_uid}/documents/delete" />
 
 Delete a set of documents based on a filter.
 
@@ -579,8 +570,7 @@ You can use this `taskUid` to get more details on [the status of the task](/refe
 This endpoint will be deprecated in the near future. Consider using POST `/indexes/{index_uid}/documents/delete` instead .
 </Warning>
 
-<RouteHighlighter method="POST" path="/indexes/{index_uid}/documents/delete-batch
-" />
+<RouteHighlighter method="POST" path="/indexes/{index_uid}/documents/delete-batch" />
 
 Delete a set of documents based on an array of document ids.
 

reference/api/experimental_features.mdx

@@ -40,8 +40,7 @@ The experimental API route is not compatible with all experimental features. Con
 
 ## Get all experimental features
 
-<RouteHighlighter method="GET" path="/experimental-features
-" />
+<RouteHighlighter method="GET" path="/experimental-features" />
 
 Get a list of all experimental features that can be activated via the `/experimental-features` route and whether or not they are currently activated.
 
@@ -63,8 +62,7 @@ Get a list of all experimental features that can be activated via the `/experime
 
 ## Configure experimental features
 
-<RouteHighlighter method="PATCH" path="/experimental-features
-" />
+<RouteHighlighter method="PATCH" path="/experimental-features" />
 
 Activate or deactivate experimental features.
 

reference/api/facet_search.mdx

@@ -21,8 +21,7 @@ Internally, Meilisearch represents numbers as [`float64`](https://en.wikipedia.o
 
 Search for a facet value within a given facet.
 
-<RouteHighlighter method="POST" path="/indexes/{index_uid}/facet-search
-" />
+<RouteHighlighter method="POST" path="/indexes/{index_uid}/facet-search" />
 
 <Warning>
 This endpoint will not work without first explicitly adding attributes to the [`filterableAttributes`](/reference/api/settings#update-filterable-attributes) list. [Learn more about facets in our dedicated guide.](/learn/filtering_and_sorting/search_with_facet_filters)

reference/api/health.mdx

@@ -13,8 +13,7 @@ The `/health` route allows you to verify the status and availability of a Meilis
 
 ## Get health
 
-<RouteHighlighter method="GET" path="/health
-" />
+<RouteHighlighter method="GET" path="/health" />
 
 Get health of Meilisearch server.