i18n(es): update ui strings

[dreyfus92]

Description

• What does this PR change? Give us a brief description.
  Updates UI strings

Summary by CodeRabbit

• New Features

  • Added new Spanish translations for a quick update message and several sidebar labels, including guides and version-related sections.

• Style

  • Minor formatting updates to localization files for consistency.

[coderabbitai]

Walkthrough

This update adds new Spanish localization entries to two JSON files. In src/content/i18n/es.json, a new translation key "quick-update" is introduced with an accompanying Spanish message. In src/starlight-sidebar/es.json, five new sidebar-related keys are added, each with their corresponding Spanish translations. Minor formatting changes, such as adding trailing commas, were also made to accommodate the new entries. No existing translation keys or values were removed or otherwise modified.

Changes

File(s)	Change Summary
src/content/i18n/es.json	Added "quick-update" translation key and value; added trailing comma to previous entry.
src/starlight-sidebar/es.json	Added five new sidebar translation keys and values; added trailing comma to previous entry.

Possibly related PRs

• i18n(ko-KR): update ko.json #95: Both PRs add the same new translation key "quick-update" and several sidebar localization entries to their respective language JSON files, indicating they are related localization updates for different languages.
• i18n(es): update i18n/es.json & translate starlight-sidebar/es.json #22: The main PR adds a new Spanish translation key for a quick update message and new sidebar entries, while the retrieved PR adds different translation keys related to docsearch and a broader set of sidebar translations; both modify the same localization files but do not overlap in the specific keys or content changed.

Suggested labels

i18n

Suggested reviewers

• Adammatthiesen

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

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
src/content/i18n/es.json	Localization changed, will be marked as complete.
src/starlight-sidebar/es.json	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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/content/i18n/es.json (1)

48-48: Suggest more natural Spanish word order
Consider swapping the adverb and verb for a smoother imperative:

- "quick-update": "Rápidamente actualiza a la última versión ejecutando el siguiente comando"
+ "quick-update": "Actualiza rápidamente a la última versión ejecutando el siguiente comando"

This reads more naturally in Spanish.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e785e32 and 0efb761.

📒 Files selected for processing (2)

• src/content/i18n/es.json (1 hunks)
• src/starlight-sidebar/es.json (1 hunks)

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

• GitHub Check: Run Starlight Link Check

🔇 Additional comments (4)

src/content/i18n/es.json (1)

47-48: Ensure valid JSON by adding the trailing comma and new key
The comma after "Háganoslo saber." is necessary to keep the file valid when appending "quick-update". Both the comma insertion and the new key follow the established style.

src/starlight-sidebar/es.json (3)

15-15: Confirm comma for valid JSON
Adding a comma after "Auto Generado" is correct to support the following entries without syntax errors.

---

16-17: Approve new sidebar translations
The entries for "topic-guides", "database", "version", and "latest" are consistent with the existing naming conventions and provide clear Spanish labels.

Also applies to: 19-20

---

18-18: Verify translation choice for "upgrade"
The key "upgrade" is translated as "Actualizar" (verb), while the surrounding entries are mostly nouns (e.g., “Guías de Versión”). Please confirm whether it should remain an imperative verb or switch to a noun like "Actualización".

[trueberryless]

Thanks for the translation 🙌

As a non-native speaker, I reviewed this PR using the Docs Translation Review Checklist and I left one small suggestion!

[trueberryless]

LGTM 🎉