fix typo, minor structural changes to reference

guimachiavelli · guimachiavelli · commit 3b890669536e · 2025-10-06T16:06:04.000+02:00
diff --git a/learn/chat/conversational_search.mdx b/learn/chat/conversational_search.mdx
@@ -47,7 +47,7 @@ Meilisearch's chat completions API consolidates RAG creation into a single proce
 Follow the [chat completions tutorial](/learn/chat/getting_started_with_chat) for information on how to implement a RAG with Meilisearch.
 
 <Warning>
-Conversational search is still in early development. Conversational agents may occasionally hallucinate innacurate and misleading information, so it is important to closely monitor it in production environments.
+Conversational search is still in early development. Conversational agents may occasionally hallucinate inaccurate and misleading information, so it is important to closely monitor it in production environments.
 </Warning>
 
 ### Model Context Protocol (MCP)
diff --git a/learn/chat/getting_started_with_chat.mdx b/learn/chat/getting_started_with_chat.mdx
@@ -30,7 +30,7 @@ curl \
 ```
 
 <Warning>
-Conversational search is still in early development. Conversational agents may occasionally hallucinate innacurate and misleading information, so it is important to closely monitor it in production environments.
+Conversational search is still in early development. Conversational agents may occasionally hallucinate inaccurate and misleading information, so it is important to closely monitor it in production environments.
 </Warning>
 
 ### Find your chat API key
diff --git a/reference/api/chats.mdx b/reference/api/chats.mdx
@@ -22,16 +22,20 @@ curl \
 </Note>
 
 <Warning>
-Conversational search is still in early development. Conversational agents may occasionally hallucinate innacurate and misleading information, so it is important to closely monitor it in production environments.
+Conversational search is still in early development. Conversational agents may occasionally hallucinate inaccurate and misleading information, so it is important to closely monitor it in production environments.
 </Warning>
 
 ## Authorization
 
-When implementing conversational search, use an API key with access to both the `search` and `chatCompletions` actions such as the default chat API key. You may also use tenant tokens instead of an API key, provided you generate the tokens with access to the required actions.
+When implementing conversational search, use an API key with access to both the `search` and `chatCompletions` actions such as the default chat API key. You may also use tenant tokens instead of an API key, provided you generate the tokens with a key that has access to the required actions.
 
-Chat queries only search indexes its API key can access. The default chat API key has access to all indexes. To limit chat access to specific indexes, you must either create a new key, or [generate a tenant token](/learn/security/generate_tenant_token_sdk) from the default chat API key.
+Chat queries only search the indexes its API key can access. The default chat API key has access to all indexes. To limit access, you must either create a new key, or [generate a tenant token](/learn/security/generate_tenant_token_sdk) from the default chat API key.
 
-## Chat workspace object
+## Chat workspaces
+
+Workspaces are groups of chat settings tailored towards specific use cases. You must configure at least on workspace to use chat completions.
+
+### Chat workspace object
 
 ```json
 {
@@ -43,79 +47,6 @@ Chat queries only search indexes its API key can access. The default chat API ke
 | :---------- | :----- | :--------------------------------------------------- |
 | **`uid`**   | String | Unique identifier for the chat completions workspace |
 
-## List chat workspaces
-
-<RouteHighlighter method="GET" path="/chats" />
-
-List all chat workspaces. Results can be paginated by using the `offset` and `limit` query parameters.
-
-### Query parameters
-
-| Query parameter | Description                    | Default value |
-| :-------------- | :----------------------------- | :------------ |
-| **`offset`**    | Number of workspaces to skip   | `0`           |
-| **`limit`**     | Number of workspaces to return | `20`          |
-
-### Response
-
-| Name          | Type    | Description                          |
-| :------------ | :------ | :----------------------------------- |
-| **`results`** | Array   | An array of [workspaces](#chat-workspace-object) |
-| **`offset`**  | Integer | Number of workspaces skipped            |
-| **`limit`**   | Integer | Number of workspaces returned           |
-| **`total`**   | Integer | Total number of workspaces              |
-
-### Example
-
-```sh
-  curl \
-    -X GET 'MEILISEARCH_URL/chats?limit=3'
-```
-
-#### Response: `200 Ok`
-
-```json
-{
-  "results": [
-    { "uid": "WORKSPACE_1" },
-    { "uid": "WORKSPACE_2" },
-    { "uid": "WORKSPACE_3" }
-  ],
-  "offset": 0,
-  "limit": 20,
-  "total": 3
-}
-```
-
-## Get one chat workspace
-
-<RouteHighlighter method="GET" path="/chats/{workspace_uid}" />
-
-Get information about a workspace.
-
-### Path parameters
-
-| Name              | Type   | Description                                                               |
-| :---------------- | :----- | :------------------------------------------------------------------------ |
-| **`workspace_uid`** * | String | `uid` of the requested index |
-
-### Example
-
-```sh
-  curl \
-    -X GET 'MEILISEARCH_URL/chats/WORKSPACE_UID'
-```
-
-#### Response: `200 Ok`
-
-```json
-{
-  "uid": "WORKSPACE_UID"
-}
-```
-
-## Chat workspace settings
-
 ### Chat workspace settings object
 
 ```json
@@ -188,6 +119,77 @@ The prompts object accepts the following fields:
 - `prompts.QParam`: Description of expected user input and the desired output. Example: "Users will ask about Meilisearch. Provide short and direct keyword-style queries."
 - `prompts.IndexUidParam`: Instructions describing each index the agent has access to and how to use them. Example: "If user asks about code or API or parameters, use the index called `documentation`."
 
+### List chat workspaces
+
+<RouteHighlighter method="GET" path="/chats" />
+
+List all chat workspaces. Results can be paginated by using the `offset` and `limit` query parameters.
+
+#### Query parameters
+
+| Query parameter | Description                    | Default value |
+| :-------------- | :----------------------------- | :------------ |
+| **`offset`**    | Number of workspaces to skip   | `0`           |
+| **`limit`**     | Number of workspaces to return | `20`          |
+
+#### Response
+
+| Name          | Type    | Description                          |
+| :------------ | :------ | :----------------------------------- |
+| **`results`** | Array   | An array of [workspaces](#chat-workspace-object) |
+| **`offset`**  | Integer | Number of workspaces skipped            |
+| **`limit`**   | Integer | Number of workspaces returned           |
+| **`total`**   | Integer | Total number of workspaces              |
+
+#### Example
+
+```sh
+  curl \
+    -X GET 'MEILISEARCH_URL/chats?limit=3'
+```
+
+##### Response: `200 Ok`
+
+```json
+{
+  "results": [
+    { "uid": "WORKSPACE_1" },
+    { "uid": "WORKSPACE_2" },
+    { "uid": "WORKSPACE_3" }
+  ],
+  "offset": 0,
+  "limit": 20,
+  "total": 3
+}
+```
+
+### Get one chat workspace
+
+<RouteHighlighter method="GET" path="/chats/{workspace_uid}" />
+
+Get information about a workspace.
+
+#### Path parameters
+
+| Name              | Type   | Description                                                               |
+| :---------------- | :----- | :------------------------------------------------------------------------ |
+| **`workspace_uid`** * | String | `uid` of the requested index |
+
+#### Example
+
+```sh
+  curl \
+    -X GET 'MEILISEARCH_URL/chats/WORKSPACE_UID'
+```
+
+##### Response: `200 Ok`
+
+```json
+{
+  "uid": "WORKSPACE_UID"
+}
+```
+
 ### Get chat workspace settings
 
 <RouteHighlighter method="GET" path="/chats/{workspace_uid}/settings" />
@@ -398,9 +400,13 @@ curl \
 
 ## Chat completions
 
+After creating a workspace, you can use the chat completions API to create a conversational search agent.
+
+### Stream chat completions
+
 <RouteHighlighter method="POST" path="/chats/{workspace_uid}/chat/completions" />
 
-Create a chat completion using Meilisearch's OpenAI-compatible interface. The endpoint searches relevant indexes and generates responses based on the retrieved content.
+Create a chat completions stream using Meilisearch's OpenAI-compatible interface. This endpoint searches relevant indexes and generates responses based on the retrieved content.
 
 ### Path parameters
 
