Skip to content

docs(README): correct spanish translation errors in .es.md#4332

Open
dignodev wants to merge 1 commit intoPanJiaChen:masterfrom
dignodev:docs/update-spanish-readme
Open

docs(README): correct spanish translation errors in .es.md#4332
dignodev wants to merge 1 commit intoPanJiaChen:masterfrom
dignodev:docs/update-spanish-readme

Conversation

@dignodev
Copy link

@dignodev dignodev commented Jan 9, 2026

¡Hola! Soy hablante nativo de español y he notado algunos errores en la traducción del README. He corregido:

  • Errores ortográficos (tildes, acentuación)
  • Términos técnicos mal traducidos
  • Mejorado la fluidez y claridad

Los cambios son solo de texto, no afectan el código. ¿Podrían revisarlos?


Description

This PR fixes grammar, spelling, and consistency issues in the Spanish translation of the README.es.md file. The changes include accent corrections, proper tildes usage, grammatical agreement, and appropriate Spanish technical terminology.

Changes Made

  • Spelling corrections:

    • "interfáz" → "interfaz" (correct according to RAE - Royal Spanish Academy)
    • "liberación" → "versión" (context-appropriate translation)
    • "antigüas" → "antiguas"
    • "pudiera" → "podrá" (verb tense correction)
  • Grammar fixes:

    • Added missing period at end of sentences
    • Gender/number agreement: "menú" (singular) vs "menus" → "menús"
    • Preposition corrections: "basado en" → "está basado en"
  • Standardized technical terms:

    • "Dialog" → "Diálogo" (consistent Spanish translation)
    • "Patrocinantes" → "Patrocinadores"
    • "LEEME" → "README" (keeping English technical term)
    • Removed unnecessary anglicisms
  • Clarity improvements:

    • "Aplicacones" → "aplicaciones"
    • "de mucha ayuda" → "de ayuda" (more natural Spanish)
    • "2017-presente" → "2017-Hoy" (more common format)

Type of Change

  • Documentation fix (non-breaking change)

Context

As a native Spanish speaker and developer, I noticed several inconsistencies in the translation that could affect readability and professionalism. These corrections improve the experience for Spanish-speaking developers consulting this project.

Checklist

  • I have reviewed grammar and spelling changes
  • I maintained the original Markdown format
  • I preserved all links and functionality
  • I verified technical terms are correct
  • Changes are text-only, no code affected

Additional Notes

  • All corrections follow Royal Spanish Academy (RAE) rules
  • English technical terms were kept when standard (README, i18n, SPA)
  • Reading fluency was improved without altering original meaning

Benefits

  1. Professionalism: A well-written README projects quality
  2. Accessibility: Better understanding for Spanish speakers
  3. Consistency: Alignment with other localized READMEs in the project
  4. Maintainability: Clearer text for future updates

Before merging: I recommend having another native Spanish speaker review the changes to confirm accuracy.

Testing

The changes can be verified by:

  1. Reviewing the diff line by line
  2. Checking that all links still work
  3. Ensuring no content was accidentally removed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant