docs: some spelling and grammar corrections for Spanish

[jackestar]

Description

docs: Superficial spelling correction for Spanish

Much of the Spanish localization has errors both superficial (accents) and grammatical and translation errors. In this PR I simply focused on certain errors.
I consider that much of the Spanish documentation is totally understandable... in the context of a programmer, where words like build, frontmatter, asset, path have meaning but some can be perfectly translated (like path) without losing context.
On the other hand there are translations that are very synthetic (they are understandable but not natural)

vitepress/docs/en/guide/custom-theme.md

Line 103 in d200f4e

The [`useData()`](../reference/runtime-api#usedata) helper provides us with all the runtime data we need to conditionally render different layouts. One of the other data we can access is the current page's frontmatter. We can leverage this to allow the end user to control the layout in each page. For example, the user can indicate the page should use a special home page layout with:

vitepress/docs/es/guide/custom-theme.md

Line 103 in d200f4e

El auxiliar [`useData()`](../reference/runtime-api#usedata) proporciona todos los datos en tiempo de ejecución que necesitamos para mostrar layouts diferentes. Uno de los otros datos que podemos accesar es el frontmatter de la página actual. Podemos aprovechar esto para permitir que el usuario final controle el layout en cada página. Por ejemplo, el usuario puede indicar que la página debe usar un layout especial de la pagina inicial con:

in the sentence One of the other data we can access is the current page's frontmatter translated as Uno de los otros datos que podemos accesar es el frontmatter de la página actual It is more understandable Otro de los datos que podemos acceder es al frontmatter de la página actual

There are many examples like this one (but I don't have a PhD in literature so I only correct the most obvious ones)

I refrained from translating words like path to directorio, it is up to you whether it is appropriate to maintain the English context.

There are also extracts that were in Portuguese.

Another comment you add is when Anglicisms are used, in parts of the documentation it is used in italics (APA style maybe), but it is not always applied, what criteria is applied for this?

seen here with service worker

vitepress/docs/es/reference/site-config.md

Line 259 in d200f4e

#### Ejemplo: Registrando un _service worker_ {#example-registering-a-service-worker}

but not with path as a "technical expression" (I think path should be translated as directorio)

vitepress/docs/es/guide/cms.md

Line 22 in d200f4e

2. Obtenga los datos necesarios del CMS y aplique formato en paths de datos apropiados:

When using a title for some variable or class as description, it should have some distinction so that translators don't translate those words... on the other hand I got translations to /guia directories instead of /guide... in that case it should be obvious... but a check could be made to local links

vitepress/docs/es/reference/site-config.md

Line 192 in d200f4e

### description

vitepress/docs/pt/reference/default-theme-nav.md

Line 86 in d200f4e

{ text: 'Guia', link: '/guia' },

vitepress/docs/es/reference/default-theme-nav.md

Line 86 in d200f4e

{ text: 'Guia', link: '/guia' },

With all this, certain criteria must be established for translations (in general)

Note

BTW I apologize in advance for the irony of making a PR for spelling and syntax correction, when I surely have errors when writing this PR in English.

Linked Issues

Additional Context

---

Tip

The author of this PR can publish a preview release by commenting /publish below.

[userquin]

use es, this will force to use Español de Colombia, we don't need the country, maybe we can split this later using es-ES and es-419