New translation batch for es (#23337)

* Add crowdin translations

* Run script/i18n/homogenize-frontmatter.js

* Run script/i18n/fix-translation-errors.js

* Run script/i18n/lint-translation-files.js --check rendering

* run script/i18n/reset-known-broken-translation-files.js

* Check in es CSV report

Co-authored-by: Francis <15894826+francisfuzz@users.noreply.github.com>

Author: docubot

translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md

@@ -133,11 +133,15 @@ runs:
 
 For more information on how to use context syntax, see "[Contexts](/actions/learn-github-actions/contexts)."
 
+## `runs`
+
+**Required** Specifies whether this is a JavaScript action, a composite action or a Docker action and how the action is executed.
+
 ## `runs` for JavaScript actions
 
-**Required** Configures the path to the action's code and the application used to execute the code.
+**Required** Configures the path to the action's code and the runtime used to execute the code.
 
-### Example using Node.js
+### Example using Node.js v12
 
 ```yaml
 runs:
@@ -147,15 +151,18 @@ runs:
 
 ### `runs.using`
 
-**Required** The application used to execute the code specified in [`main`](#runsmain).
+**Required** The runtime used to execute the code specified in [`main`](#runsmain).  
+
+- Use `node12` for Node.js v12.
+- Use `node16` for Node.js v16.
 
 ### `runs.main`
 
-**Required** The file that contains your action code. The application specified in [`using`](#runsusing) executes this file.
+**Required** The file that contains your action code. The runtime specified in [`using`](#runsusing) executes this file.
 
 ### `pre`
 
-**Optional** Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The application specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`pre-if`](#pre-if).
+**Optional** Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The runtime specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`pre-if`](#pre-if).
 
 In this example, the `pre:` action runs a script called `setup.js`:
 
@@ -181,7 +188,7 @@ In this example, `cleanup.js` only runs on Linux-based runners:
 
 ### `post`
 
-**Optional** Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The application specified with the [`using`](#runsusing) syntax will execute this file.
+**Optional** Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The runtime specified with the [`using`](#runsusing) syntax will execute this file.
 
 In this example, the `post:` action runs a script called `cleanup.js`:
 
@@ -207,11 +214,11 @@ For example, this `cleanup.js` will only run on Linux-based runners:
 
 ## `runs` for composite actions
 
-**Required** Configures the path to the composite action, and the application used to execute the code.
+**Required** Configures the path to the composite action.
 
 ### `runs.using`
 
-**Required** To use a composite action, set this to `"composite"`.
+**Required** You must set this value to `'composite'`.
 
 ### `runs.steps`
 
@@ -354,7 +361,7 @@ runs:
 
 **Optional** Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. {% data variables.product.prodname_actions %} uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using [`pre-if`](#pre-if).
 
-The application specified with the [`using`](#runsusing) syntax will execute this file.
+The runtime specified with the [`using`](#runsusing) syntax will execute this file.
 
 In this example, the `pre-entrypoint:` action runs a script called `setup.sh`:
 

translations/es-ES/content/actions/learn-github-actions/contexts.md

@@ -139,7 +139,8 @@ The `runner` context contains information about the runner that is executing the
 | Property name | Type | Description |
 |---------------|------|-------------|
 | `runner.name` | `string` | {% data reusables.actions.runner-name-description %} |
-| `runner.os` | `string` | {% data reusables.actions.runner-os-description %} |
+| `runner.os` | `string` | {% data reusables.actions.runner-os-description %} |{% if actions-runner-arch-envvars %}
+| `runner.arch` | `string` | {% data reusables.actions.runner-arch-description %} |{% endif %}
 | `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} |
 | `runner.tool_cache` | `string` | {% ifversion ghae %}For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}|
 

translations/es-ES/content/actions/learn-github-actions/environment-variables.md

@@ -79,7 +79,8 @@ We strongly recommend that actions use environment variables to access the files
 | `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`.
 | `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`.
 | `RUNNER_NAME` | {% data reusables.actions.runner-name-description %}
-| `RUNNER_OS` | {% data reusables.actions.runner-os-description %}
+| `RUNNER_OS` | {% data reusables.actions.runner-os-description %}{% if actions-runner-arch-envvars %}
+| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}{% endif %}
 | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %}
 {% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %}
 

translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md

@@ -54,6 +54,36 @@ It's not possible to add CPU or memory resources to an existing AWS/EC2 instance
 3. Start the instance.
 {% data reusables.enterprise_installation.configuration-recognized %}
 
+## Adding CPU or memory resources on Microsoft Azure
+
+{% note %}
+
+**Note:** To add CPU or memory resources in Microsoft Azure, you must be familiar with using either the Azure Portal, Azure CLI or Azure Powershell to manage VM instances. For background and details on using the Azure tools of your choice to perform the resize, please refer to the Azure documentation on [changing the size of a virtual machine](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm).
+
+{% endnote %}
+
+### Resizing considerations
+
+Before increasing CPU or memory resources for {% data variables.product.product_location %}, review the following recommendations.
+
+- **Scale your memory with CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %}
+- **Assign a static IP address to the instance**. If you haven't assigned a static IP to your instance, you might have to adjust the DNS A records for your {% data variables.product.prodname_ghe_server %} host after the restart to account for the change in IP address.
+
+### Supported Microsoft Azure instance sizes
+
+You need to determine the instance size you would like to upgrade to based on CPU/memory specifications.
+
+{% data reusables.enterprise_installation.warning-on-scaling %}
+
+{% data reusables.enterprise_installation.azure-instance-recommendation %}
+
+### Resizing for Microsoft Azure
+
+You can scale the VM up by changing the VM size. Changing its size will cause it to be restarted. In some cases, you must deallocate the VM first. This can happen if the new size is not available on the hardware cluster that is currently hosting the VM. 
+
+1. Refer to the Azure documentation on [changing the size of a virtual machine](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm) for the required steps.
+{% data reusables.enterprise_installation.configuration-recognized %}
+
 ## Adding CPU or memory resources for OpenStack KVM
 
 It's not possible to add CPU or memory resources to an existing OpenStack KVM instance. Instead, you must: