1) Use polite, instructional Korean (e.g. 합니다/하세요 style).
2) Keep the tone consistent with the existing Korean FastAPI docs.

### Headings

1) Follow existing Korean heading style (short, action-oriented headings like “확인하기”).
2) Do not add trailing punctuation to headings.

### Quotes

1) Keep quote style consistent with the existing Korean docs.
2) Never change quotes inside inline code, code blocks, URLs, or file paths.

### Grammar and tone

1) Use polite/formal address consistent with existing Ukrainian docs (use “ви/ваш”).
2) Keep the tone concise and technical.

### Headings

1) Follow existing Ukrainian heading style; keep headings short and instructional.
2) Do not add trailing punctuation to headings.

### Quotes

1) Prefer Ukrainian guillemets «…» for quoted terms in prose, matching existing Ukrainian docs.

2) For headings that are instructions written in imperative in English (e.g. “Go check …”), keep them in imperative in French, using the formal grammar (e.g. «Allez voir …»).

3) Keep heading punctuation as in the source. In particular, keep occurrences of literal « - » (space-hyphen-space) as « - » (the existing French docs use a hyphen here).

Translate to Japanese (日本語).

Language code: ja.

### Grammar and tone

1) Use polite, instructional Japanese (です/ます調).
2) Keep the tone concise and technical (match existing Japanese FastAPI docs).

### Headings

1) Follow the existing Japanese style: short, descriptive headings (often noun phrases), e.g. 「チェック」.
2) Do not add a trailing period at the end of headings.

### Quotes

### Target language

Translate to Simplified Chinese (简体中文).

Language code: zh.

### Grammar and tone

1) Use clear, concise technical Chinese consistent with existing docs.
2) Address the reader naturally (commonly using “你/你的”).

### Headings

1) Follow existing Simplified Chinese heading style (short and descriptive).
2) Do not add trailing punctuation to headings.

### Negative Consequences

* **Historical inconsistencies**: Existing code may contain British English spellings that cannot be changed due to backward compatibility

### Migration and Enforcement

* **New code**: All new contributions must use American English

1) Use clear, concise technical Traditional Chinese consistent with existing docs.
2) Address the reader naturally (commonly using “你/你的”).

### Headings

1) Follow existing Traditional Chinese heading style (short and descriptive).
2) Do not add trailing punctuation to headings.

### Quotes and punctuation

        // Gehe in dieses Projektverzeichnis
        $ cd awesome-project
        ```
        »»»

                        .expectResult(MODULE_B),
                scenario("Selected missing project as required and as optional")
                        .activeRequiredProjects("non-existing-module")
                        .activeOptionalProjects("non-existing-module")
                        .expectResult(MavenExecutionException.class, "do not exist"),
                scenario("Resuming from project")
                        .resumeFrom(MODULE_B)

1.  Any significant changes should be accompanied by tests. The project already
    has good test coverage, so look at some existing tests if you're unsure how
    to go about it.
2.  All contributions must be licensed Apache 2.0 and all files must have a copy
    of the boilerplate license comment (can be copied from an existing file).
3.  Files should be formatted according to Google's [Java style guide][].