docs: 参考文档不用第二人称,四处改回陈述句

Author: speak-agent

docs/05-mcpp-toml.md

@@ -2248,7 +2248,7 @@ visible as *"the device is never reachable"* is the hardest kind to diagnose.
 #### A rule package brings its own environment (2026.9.6.6+)
 
 The table above is what a project writes when it has an opinion. Most projects
-have none, and should write nothing:
+have none, and nothing is what they write:
 
 ```toml
 [build-dependencies.mcpp]
@@ -2287,7 +2287,7 @@ Which one is decided in two steps.
 outranks a package it depends on, so a pin overrides a rule's requirement:
 
 ```toml
-# your project, when you do have an opinion
+# the project, when it does have an opinion
 [target.'cfg(accelerator = "cuda")'.xlings.workspace]
 "xim:cuda-nvcc" = "13.3.33"
 ```
@@ -2296,7 +2296,7 @@ A declaration that names no version abstains: it says the package is wanted and
 nothing about which version, so it cannot outrank a floor merely by being
 nearer. When two declarations disagree and both name a version, mcpp reports
 which was used — an override visible only as *"two versions were declared and
-one directory exists"* is a fact you would have to reconstruct from the
+one directory exists"* is a fact the reader has to reconstruct from the
 filesystem.
 
 **Validation — the winner must satisfy every requirement that lost.** `>=`,
@@ -2318,8 +2318,8 @@ violated.
 **This is a comparison, not a search.** The version is chosen by adjudication
 and then checked, so mcpp never has to ask the index which versions exist and
 carries no constraint solver. The cost is stated rather than hidden: a
-combination a solver could satisfy — your `>=8.0`, a rule's `8.5.0`, and 8.3 as
-the newest in the index — is refused instead, and the refusal says how to
+combination a solver could satisfy — a project's `>=8.0`, a rule's `8.5.0`, and
+8.3 as the newest in the index — is refused instead, and the refusal says how to
 proceed.
 
 Ranges are resolved in both directions. `>=2026.1` installs the highest

docs/20-heterogeneous-builds.md

@@ -178,14 +178,14 @@ accelerator opens neither, which is what keeps the cheapest build cheap -- and
 that is the build CI runs.
 
 Every lane works this way: `rules-cuda`, `rules-hip`, `rules-sycl`,
-`rules-spirv` and `rules-ascendc` each carry their own. There is no lane where
-you are expected to supply the environment yourself, because "sometimes you
-have to" is a rule nothing can state precisely enough to be useful.
-
-**Overriding is one line, in your project.** Which package and how old it may
-be is the rule author's knowledge; *exactly which version* is sometimes yours,
-because a CUDA line is coupled to a driver floor that is a property of your
-machines:
+`rules-spirv` and `rules-ascendc` each carry their own. No lane expects the
+project to supply the environment instead, because "sometimes it has to" is a
+rule nothing can state precisely enough to be useful.
+
+**Overriding is one line, in the project.** Which package and how old it may be
+is the rule author's knowledge; *exactly which version* sometimes belongs to the
+project, because a CUDA line is coupled to a driver floor that is a property of
+the machines it will run on:
 
 ```toml
 [target.'cfg(accelerator = "cuda")'.xlings.workspace]

docs/zh/05-mcpp-toml.md

@@ -1913,7 +1913,7 @@ hardware = {}
 
 #### 规则包自带它的环境(2026.9.6.6+)
 
-上面那张表是工程**有主张**时写的。多数工程没有主张,也就不该写:
+上面那张表是工程**有主张**时写的。多数工程没有主张,写下的也就是空无一物:
 
 ```toml
 [build-dependencies.mcpp]
@@ -1944,10 +1944,10 @@ plugins = { version = "0.2.4", features = ["rules-cuda"], host-module = true }
 
 装哪一个,分两步决定。
 
-**裁决——离产物更近的声明赢。** 你的工程压过它依赖的包,于是一个钉覆盖规则的要求:
+**裁决——离产物更近的声明赢。** 工程压过它依赖的包,于是一个钉覆盖规则的要求:
 
 ```toml
-# 你的工程,当你确实有主张时
+# 工程侧,当它确实有主张时
 [target.'cfg(accelerator = "cuda")'.xlings.workspace]
 "xim:cuda-nvcc" = "13.3.33"
 ```
@@ -1973,7 +1973,7 @@ error: `xim:cuda-nvcc` is pinned to 12.0.0 by this project, and mcpp:plugins
 
 **这是一次比较,不是一次搜索。** 版本由裁决选定、再被检查,所以 mcpp 从不需要问索引
 「有哪些版本」,也就不带约束求解器。代价被写出来而不是藏起来:一个求解器本可满足的
-组合——你写 `>=8.0`、规则写 `8.5.0`、而索引里最新是 8.3——会被拒绝,而拒绝消息里
+组合——工程写 `>=8.0`、规则写 `8.5.0`、而索引里最新是 8.3——会被拒绝,而拒绝消息里
 写着怎么往下走。
 
 范围在两个方向上都被求解。`>=2026.1` 装到满足它的最高已发布版本,`>=2099.1` 作为

docs/zh/20-heterogeneous-builds.md

@@ -145,11 +145,11 @@ plugins = { version = "0.2.4", features = ["rules-cuda"], host-module = true }
 两道门都不过——这正是让最便宜的那次构建保持便宜的原因,而那是 CI 跑的那一次。
 
 每条 lane 都是这样:`rules-cuda`、`rules-hip`、`rules-sycl`、`rules-spirv`、
-`rules-ascendc` 各自带着自己的环境。**不存在需要你自己补环境的 lane**,因为「有时候
+`rules-ascendc` 各自带着自己的环境。**不存在需要工程自己补环境的 lane**,因为「有时候
 需要」是一条没有任何地方能说清楚到可用的规则。
 
 **覆盖是工程里的一行。** 哪个包、最低到哪一版,是规则作者的知识;**具体哪一版**有时
-是你的——一条 CUDA 线耦合着驱动下界,而那是你那批机器的属性:
+属于工程——一条 CUDA 线耦合着驱动下界,而那是产物将要运行的那批机器的属性:
 
 ```toml
 [target.'cfg(accelerator = "cuda")'.xlings.workspace]