docs: fix formatting related build issue

[HiDeoo]

What kind of changes does this PR include?

• Minor content fixes (broken links, typos, etc.)

Description

This PR fixes a build issue with the docs following the merge of #1250. If I get this right, I think this is what happened:

• docs(i18n): Add Indonesian translation for site search documentation #1250 was building fine in the PR
• docs(i18n): Add Indonesian translation for site search documentation #1250 was rendering fine in the PR
• After merging docs(i18n): Add Indonesian translation for site search documentation #1250, the live docs are rendering fine
• After CI applied formatting, it somehow formatted the file in way that broke the build

My assumption was that if some Markdown was rendering fine, applying Prettier would never break it but I guess this is a wrong assumption?

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4d8fab3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
starlight	✅ Ready (Inspect)	Visit Preview	Dec 8, 2023 5:01pm

[kevinzunigacuellar]

I've noticed that if there isn't a new line before and after codeblocks the formatter sometimes will break the syntax

Edit: when using the tab component

[HiDeoo]

I've noticed that if there isn't a new line before and after codeblocks the formatter sometimes will break the syntax

Oh, thanks for sharing, I totally did not know about that kind of edge cases 🤔

[HiDeoo]

Fixed by @delucis with 5df5798

[delucis]

Oh boy — sorry for not noticing this PR! I saw the failing build on main and just jumped to getting it passing, sorry. Should have checked for anyone else working on it first!