diff --git a/learn/chat/getting_started_with_chat.mdx b/learn/chat/getting_started_with_chat.mdx index a2e2afed1..328235bf9 100644 --- a/learn/chat/getting_started_with_chat.mdx +++ b/learn/chat/getting_started_with_chat.mdx @@ -238,7 +238,7 @@ In most cases, that is only the beginning of adding conversational search to you Meilisearch's chat endpoint was designed to be OpenAI-compatible. This means you can use the official OpenAI SDK in any supported programming language, even if your provider is not OpenAI. -Integrating Meiliearch and the OpenAI SDK with JavaScript would look lik this: +Integrating Meilisearch and the OpenAI SDK with JavaScript would look like this: ```javascript JavaScript import OpenAI from 'openai'; @@ -260,8 +260,6 @@ for await (const chunk of completion) { Take particular note of the last lines, which output the streamed responses to the browser console. In a real-life application, you would instead print the response chunks to the user interface. - - ## Troubleshooting ### Common issues and solutions diff --git a/learn/indexing/optimize_indexing_performance.mdx b/learn/indexing/optimize_indexing_performance.mdx index dec198ba0..78b4ff14d 100644 --- a/learn/indexing/optimize_indexing_performance.mdx +++ b/learn/indexing/optimize_indexing_performance.mdx @@ -62,7 +62,7 @@ Focus on the **longest-running steps** and investigate which index settings or d | Description | Optimization | |--------------|--------------| -| Time spent waiting for CPU-bound extraction. | No direct optimization possible. Indicates a CPU bottleneck. Use more cores or scale horizontally with [sharding](/learn/advanced/sharding). | +| Time spent waiting for CPU-bound extraction. | No direct optimization possible. Indicates a CPU bottleneck. Use more cores or scale horizontally with [sharding](/learn/multi_search/implement_sharding). | ### `post processing facets > strings bulk` / `numbers bulk`