minor fixes

Author: guimachiavelli

learn/analytics/analytics_metrics_reference.mdx

@@ -5,11 +5,11 @@ description: This reference describes the metrics you can find in the Meilisearc
 
 ## Total searches
 
-Total number of searches made in the selected indexes during the specified period. Multi-search and federated search requests count as a single search.
+Total number of searches made during the specified period. Multi-search and federated search requests count as a single search.
 
 ## Total users
 
-Total number of users who performed a search in the selected indexes.
+Total number of users who performed a search in the specified period.
 
 Include the [user ID](/learn/analytics/bind_events_user) in your search request headers for the most accurate metrics. If search requests do not provide any user ID, the total amount of unique users will increase, as each request is assigned to a unique user ID.
 
@@ -31,9 +31,13 @@ Meilisearch does not have access to this information by default. You must [confi
 
 ## Conversion
 
-The percentage of searches resulting in a [conversion event](/learn/analytics/configure_analytics_events) in your application. Conversion events vary depending on your application and indicate a user has performed a specific desired action. For example, a conversion for an e-commerce website might mean a user has bought a product.
+The percentage of searches resulting in a conversion event in your application. Conversion events vary depending on your application and indicate a user has performed a specific desired action. For example, a conversion for an e-commerce website might mean a user has bought a product.
 
-You must explicitly configure your application to send conversion events when conditions are met.
+You must explicitly [configure your application to send conversion](/learn/analytics/configure_analytics_events) events when conditions are met.
+
+<Note>
+It is not possible to associate multiple `conversion` events with the same query.
+</Note>
 
 ## Search requests
 
@@ -53,4 +57,4 @@ Most common query terms that did not return any search results.
 
 ## Countries with most searches
 
-List of countries that generate the largest amount of search requests.
+List of countries that generate the largest amount of search requests.

learn/analytics/bind_events_user.mdx

@@ -24,7 +24,7 @@ You can assign user IDs to search requests by including an `X-MS-USER-ID` header
 Replace `SEARCH_USER_ID` with any value that uniquely identifies that user. This may be an authenticated user's ID when running searches from your own back end, or a hash of the user's IP address.
 
 <Note>
-Assigning user IDs to search requests is optional. If a Meilisearch Cloud search request does not have an ID, Meilisearch will automaticalle generate one.
+Assigning user IDs to search requests is optional. If a Meilisearch Cloud search request does not have an ID, Meilisearch will automatically generate one.
 </Note>
 
 ## Assign user IDs to analytics events

learn/analytics/configure_analytics_events.mdx

@@ -14,21 +14,21 @@ You must have a [Meilisearch Cloud](https://meilisearch.com/cloud) account to ac
 
 To track click-through rate and average click position, Meilisearch Cloud needs to know when users click on search results.
 
-Every time a user clicks on a search result, your application must send a `click` event to the `POST` endpoint of Meilisearch Cloud analytics route:
+Every time a user clicks on a search result, your application must send a `click` event to the `POST` endpoint of Meilisearch Cloud's `/events` route:
 
 <CodeSamplesAnalyticsEventClick1 />
 
-You must explicitly submit a `userId` associated with the event. This can be any arbitrary string you can use to identify the user, such as their profile ID in your application or their hashed IP address. You may submit user IDs directly on the event payload, or setting a `X-MS-USER-ID` request header.
+You must explicitly submit a `userId` associated with the event. This can be any arbitrary string you use to identify the user, such as their profile ID in your application or their hashed IP address. You may submit user IDs directly on the event payload, or setting a `X-MS-USER-ID` request header.
 
-Specifying a `queryUid` is optional but recommended as it ensures Meilisearch correctly associates the search query with the event. You can find the query UID in the `metadata` field present in Meilisearch Cloud's search query response.
+Specifying a `queryUid` is optional but recommended as it ensures Meilisearch correctly associates the search query with the event. You can find the query UID in the [`metadata` field present in Meilisearch Cloud's search query responses](/reference/api/overview#search-metadata).
 
 For more information, consult the [analytics events endpoint reference](/learn/analytics/events_endpoint).
 
 ## Configure conversion rate
 
-To track conversion rate, first identify what should count as a conversion for your application. For example, in a web shop, a conversion might be a user finalizing the checkout process.
+To track conversion rate, first identify what should count as a conversion for your application. For example, in a web shop a conversion might be a user finalizing the checkout process.
 
-Once you have established what counts as a conversion in your application, configure it to send a `conversion` event to the `POST` endpoint of Meilisearch Cloud analytics route:
+Once you have established what is a conversion in your application, configure it to send a `conversion` event to the `POST` endpoint of Meilisearch Cloud analytics route:
 
 <CodeSamplesAnalyticsEventConversion1 />
 

learn/analytics/events_endpoint.mdx

@@ -37,12 +37,12 @@ Send an analytics event to Meilisearch Cloud.
 ```
 
 <Note>
-You must provide a string identifying your user if you want Meilisearch Cloud to track analytics and click events.
+You must provide a string identifying your user if you want Meilisearch Cloud to track conversion and click events.
 
 You may do that in two ways:
 
 - Specify the user ID in the payload, using the `userId` field
-- Specify the user ID with the `X-MS-USER-ID` header when sending search and other analytics events
+- Specify the user ID with the `X-MS-USER-ID` header with your `/events` and search requests
 </Note>
 
 #### Example