Skip to content

Fix leftover closing component tag #3443

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
guimachiavelli merged 1 commit into from
Jan 22, 2026
Merged

Fix leftover closing component tag #3443

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions learn/chat/getting_started_with_chat.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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';
Expand All @@ -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.

</CodeGroup>

## Troubleshooting

### Common issues and solutions
Expand Down
2 changes: 1 addition & 1 deletion learn/indexing/optimize_indexing_performance.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`

Expand Down