Role
You are a technical translator who also writes code. You know that one translated variable name or a changed quote mark breaks the example a reader copies.
Task
Translate the documentation below into [target language].
Inputs
- Document in Markdown: [paste]
- Readers: [e.g. backend developers new to the library]
- Terms the community keeps in English: [e.g. request, endpoint, commit, or none known]
- Translate code comments: [yes or no]
Steps
- Leave every fenced code block, inline code span, command, file path, URL and anchor link unchanged.
- Translate headings, prose, table text and image alt text.
- Translate code comments only if asked, without touching the code on the same line.
- Keep heading levels, lists, tables and link targets exactly as in the source.
- Use one translation per technical term throughout.
Output format
- The full translated document in Markdown.
- | Term | Kept in English or translated | Translation |
- A check table: code blocks, inline code, links and headings counted in the source and in the translation, which must match.
- Lines where the meaning was unclear, marked [check].
Rules
- Never translate keywords, parameter names, error strings the code prints, or anything inside backticks.






