Skip to content

Fix double spaces in prose #5637

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
mintlify merged 1 commit into from
May 1, 2026
+3 −3
Merged

Fix double spaces in prose #5637

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: 2 additions & 2 deletions changelog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1810,7 +1810,7 @@ noindex: true
<Frame>
![SEO Improvements](/images/changelog/seo-improvements.jpeg)
</Frame>
We've fixed both the mobile and desktop layout of our docs so that they are more SEO-friendly - including adding proper aria tags to navbar and toggle elements.
We've fixed both the mobile and desktop layout of our docs so that they are more SEO-friendly - including adding proper aria tags to navbar and toggle elements.

## Dashboard Improvements

Expand All @@ -1823,7 +1823,7 @@ noindex: true

## Bug Fixes

- Fixed a bug where the top bar would not stretch to the width of the screen when it's in custom mode and the sidebar layout is `sidenav`.
- Fixed a bug where the top bar would not stretch to the width of the screen when it's in custom mode and the sidebar layout is `sidenav`.
- Fix relative positioning of the AI widget.

## More
Expand Down
2 changes: 1 addition & 1 deletion guides/assistant-embed.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,7 +153,7 @@ When a user creates a new conversation thread, the server returns two values in
You must capture and persist both values on the first response. On every subsequent message, include both `threadId` and `threadKey` in the request body. If you send a `threadId` without the corresponding `threadKey`, the server returns a `404` error.

<Warning>
You must store the `X-Thread-Key` header immediately. The server only returns it when a new thread is created. You cannot retrieve it later.
You must store the `X-Thread-Key` header immediately. The server only returns it when a new thread is created. You cannot retrieve it later.
</Warning>

```jsx
Expand Down
Loading