Examples of how to translate a heading:

    Source (English):

        «««
        ## Alternative API docs { #alternative-api-docs }
        »»»

    Result (Spanish):

          - translate-lang
          - update-outdated
          - add-missing
          - update-and-add
          - remove-removable
      language:
        description: Language to translate to as a letter code (e.g. "es" for Spanish)
        type: string
        required: false
        default: ""
      en_path:
        description: File path in English to translate (e.g. docs/en/docs/index.md)
        type: string
        required: false

* request body: request body (do not translate to "cuerpo de la petición")
* response body: response body (do not translate to "cuerpo de la respuesta")
* cross domain: cross domain (do not translate to "dominio cruzado")
* cross origin: cross origin (do not translate to "origen cruzado")
* plugin: plugin (do not translate to "complemento" or "extensión")
* plug-in: plug-in (do not translate to "complemento" or "extensión")

</div>

#### Translation specific tips and guidelines

* Translate only the Markdown documents (`.md`). Do not translate the code examples at `./docs_src`.

* In code blocks within the Markdown document, translate comments (`# a comment`), but leave the rest unchanged.

* Do not change anything enclosed in "``" (inline code).

* In lines starting with `///` translate only the text part after `|`. Leave the rest unchanged.

* Check if things are okay in the translation.
* If necessary, improve your language specific prompt, the general prompt, or the English document.
* Then manually fix the remaining issues in the translation, so that it is a good translation.

* bug: bug
* context manager: gerenciador de contexto
* cross domain: cross domain (do not translate to "domínio cruzado")
* cross origin: cross origin (do not translate to "origem cruzada")
* Cross-Origin Resource Sharing: Cross-Origin Resource Sharing (do not translate to "Compartilhamento de Recursos de Origem Cruzada")
* Deep Learning: Deep Learning (do not translate to "Aprendizado Profundo")
* dependable: dependable
* dependencies: dependências

### Headings

1) Translate headings using the infinite form.

Examples:

    Source (English):

        «««
        ## Create a Project { #create-a-project }
        »»»

    Translate with (German):

        «««
        ## Ein Projekt erstellen { #create-a-project }
        »»»

    Do NOT translate with (German):

        «««

/**
 * Postprocesses filesystem paths. For instance, a path translator might want to resolve relative paths given in the
 * bean configuration against some base directory.
 *
 */
public interface BeanConfigurationPathTranslator {

    /**
     * Translates the specified path.
     *
     * @param path The path to translate, may be {@code null}.
     * @return The translated path or {@code null} if none.
     */

1) Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
2) If a title is present, prefer these canonical titles:

- `/// note | 참고`
- `/// tip | 팁`
- `/// warning | 경고`
- `/// info | 정보`
- `/// danger | 위험`
- `/// note Technical Details | 기술 세부사항`
- `/// check | 확인`
Notes:

- `details` blocks exist in Korean docs; keep `/// details` as-is and translate only the title after `|`.

### `///` admonitions

1) Keep the admonition keyword in English (do not translate `note`, `tip`, etc.).
2) Many Traditional Chinese docs currently omit titles in `///` blocks; that is OK.
3) If a generic title is present, prefer these canonical titles:

- `/// note | 注意`

Notes:

- `details` blocks exist; keep `/// details` as-is and translate only the title after `|`.
- Example canonical titles used in existing docs: