docs: make technical prose concrete
This commit is contained in:
@@ -64,4 +64,4 @@ When translations need to be written from scratch, the orchestrating agent does
|
||||
|
||||
## How to respond to translation review
|
||||
|
||||
Follow the [code-review reporting guidance](../dsh-code-review/SKILL.md#reporting-findings): evaluate each comment on its merits, and for terminology comments, remember the table is the contract — a reviewer's rendering decision gets applied to [terminology.md](../../../docs/i18n/terminology.md) so it binds every future translation, not just patched into one file.
|
||||
Follow the [code-review reporting guidance](../dsh-code-review/SKILL.md#reporting-findings): evaluate each comment on its merits, and for terminology comments, remember the terminology table is the contract — apply a reviewer's rendering decision to [terminology.md](../../../docs/i18n/terminology.md), not only to one file.
|
||||
|
||||
Reference in New Issue
Block a user