i18n(ko-KR): update code highlights

[jsparkdev]

Description

• docs: small code highlight update #106

Summary by CodeRabbit

• Documentation
  • Updated code snippet formatting in multiple plugin documentation pages to improve code highlighting and readability. No changes to code content or functionality.

[coderabbitai]

Walkthrough

The changes update the code block metadata in several Korean documentation markdown files for StudioCMS plugins. Specifically, the ins= prefix is removed from the twoslash code fence line range specifiers, altering how specific lines are highlighted in code snippets. No changes are made to the code content, logic, or any exported or public entities.

Changes

Files	Change Summary
src/content/docs/ko/package-catalog/studiocms-plugins/studiocms-blog.mdx	Removed ins= prefix from twoslash code block metadata for line highlighting.
src/content/docs/ko/package-catalog/studiocms-plugins/studiocms-markdoc.mdx	Removed ins= prefix from twoslash code block metadata for line highlighting.
src/content/docs/ko/package-catalog/studiocms-plugins/studiocms-mdx.mdx	Removed ins= prefix from twoslash code block metadata for line highlighting.
src/content/docs/ko/package-catalog/studiocms-plugins/studiocms-wysiwyg.mdx	Removed ins= prefix from twoslash code block metadata for line highlighting.

Possibly related PRs

• docs: small code highlight update #106: Makes identical changes to the same markdown documentation files by removing the ins= prefix from twoslash code block metadata to adjust code line highlighting.

Suggested labels

i18n

Suggested reviewers

• Adammatthiesen

Poem

In the docs where code lines gleam,
A rabbit hopped with a quiet dream.
"ins=" is gone, the lines still shine,
Highlighting code, all neat and fine.
With every tweak, the docs grow clear—
Hippity-hop, more helpful here!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3682f88 and 88e7ee8.

📒 Files selected for processing (4)

• src/content/docs/ko/package-catalog/studiocms-plugins/studiocms-blog.mdx (1 hunks)
• src/content/docs/ko/package-catalog/studiocms-plugins/studiocms-markdoc.mdx (1 hunks)
• src/content/docs/ko/package-catalog/studiocms-plugins/studiocms-mdx.mdx (1 hunks)
• src/content/docs/ko/package-catalog/studiocms-plugins/studiocms-wysiwyg.mdx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Run Starlight Link Check

🔇 Additional comments (4)

src/content/docs/ko/package-catalog/studiocms-plugins/studiocms-mdx.mdx (1)

28-28: Remove ins= prefix from twoslash metadata
The diff replaces ins={2, 6} with {2, 6} in the TypeScript twoslash code fence, aligning with the updated syntax for line highlighting. This change standardizes the code snippet presentation without altering any example logic.

src/content/docs/ko/package-catalog/studiocms-plugins/studiocms-markdoc.mdx (1)

28-28: Standardize twoslash highlight syntax
Updating from ins={2, 6} to {2, 6} ensures the MDX plugin correctly interprets the highlighted lines. The snippet content remains identical, and the documentation is now consistent with other language variants.

src/content/docs/ko/package-catalog/studiocms-plugins/studiocms-blog.mdx (1)

28-28: Align twoslash code fence metadata
By removing the ins= prefix, the fence header now correctly uses {2, 6} to highlight lines 2 and 6. This matches the expected twoslash syntax and is consistent across all plugin docs.

src/content/docs/ko/package-catalog/studiocms-plugins/studiocms-wysiwyg.mdx (1)

28-28: Normalize twoslash annotation format
Changing the fence from ins={2, 6} to {2, 6} brings the WYSIWYG plugin docs in line with the other code samples and the updated highlighting rules. No code content is modified.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[studiocms-no-reply]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
ko/package-catalog/studiocms-plugins/studiocms-blog.mdx	Localization changed, will be marked as complete.
ko/package-catalog/studiocms-plugins/studiocms-markdoc.mdx	Localization changed, will be marked as complete.
ko/package-catalog/studiocms-plugins/studiocms-mdx.mdx	Localization changed, will be marked as complete.
ko/package-catalog/studiocms-plugins/studiocms-wysiwyg.mdx	Localization changed, will be marked as complete.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[dreyfus92]

thank you @jsparkdev 😁