Update goals to reference lang-docs

In the context of a project goal reserving the bandwidth of a team,
the work of reviewing and revising proposed Reference text at this
time falls more on the T-lang-docs side rather than on the T-spec
side.  So let's update the relevant project goals and the template
accordingly.

Author: traviscross

src/2025h2/Rust-for-Linux-language.md

@@ -73,15 +73,15 @@ Which features get finished and stabilized depends on bandwidth and other constr
 
 ### Finish and stabilize `arbitrary_self_types` and `derive_coerce_pointee`
 
-| Task                           | Owner(s) or team(s) | Notes |
-|--------------------------------|---------------------|-------|
-| Discussion and moral support   | ![Team][] [lang]    |       |
-| Finalize remaining work        | @dingxiangfei2009   |       |
-| Author specification 1st draft | @dingxiangfei2009   |       |
-| Finalize specification text    | ![Team][] [spec]    |       |
-| Lang-team champion             | ![Team][] [lang]    |       |
-| Author stabilization report    | @dingxiangfei2009   |       |
-| Author stabilization PR        | @dingxiangfei2009   |       |
-| Stabilization decision         | ![Team][] [lang]    |       |
+| Task                         | Owner(s) or team(s)   | Notes |
+|------------------------------|-----------------------|-------|
+| Discussion and moral support | ![Team][] [lang]      |       |
+| Finalize remaining work      | @dingxiangfei2009     |       |
+| Author Reference PR          | @dingxiangfei2009     |       |
+| Review/revise Reference PR   | ![Team][] [lang-docs] |       |
+| Lang-team champion           | ![Team][] [lang]      |       |
+| Author stabilization report  | @dingxiangfei2009     |       |
+| Author stabilization PR      | @dingxiangfei2009     |       |
+| Stabilization decision       | ![Team][] [lang]      |       |
 
 ## Frequently asked questions

src/2025h2/cargo-script.md

@@ -76,14 +76,14 @@ Tracking issue [#136889](https://github.com/rust-lang/rust/issues/136889):
 
 ### Stabilize language feature `frontmatter`
 
-| Task                           | Owner(s) or team(s)                | Notes |
-|--------------------------------|------------------------------------|-------|
-| Author specification 1st draft | @epage |       |
-| Finalize specification text    | ![Team][] [spec]                   |  @ehuss |
-| Lang-team champion             | ![Team][] [lang]                   | @joshtriplett       |
-| Author stabilization report    | @epage |       |
-| Author stabilization PR        | @epage |       |
-| Stabilization decision         | ![Team][] [lang]                   |       |
+| Task                        | Owner(s) or team(s)   | Notes         |
+|-----------------------------|-----------------------|---------------|
+| Author Reference PR         | @epage                |               |
+| Review/revise Reference PR  | ![Team][] [lang-docs] | @ehuss        |
+| Lang-team champion          | ![Team][] [lang]      | @joshtriplett |
+| Author stabilization report | @epage                |               |
+| Author stabilization PR     | @epage                |               |
+| Stabilization decision      | ![Team][] [lang]      |               |
 
 ### Definitions
 

src/TEMPLATE.md

@@ -98,18 +98,18 @@
 
 > *If the feature has been RFC'd and implemented and experiences are positive, [stabilization](https://rustc-dev-guide.rust-lang.org/stabilization_guide.html) may be the right next step. In this case, you will need to author a first draft of text for the Rust reference and make a Team Ask to request someone from the the spec team to adapt that text for final inclusion. You will also need to author a stabilization report.
 
-| Task                           | Owner(s) or team(s)                | Notes |
-|--------------------------------|------------------------------------|-------|
-| Author specification 1st draft | *Goal point of contact, typically* |       |
-| Finalize specification text    | ![Team][] [spec]                   |       |
-| Lang-team champion             | ![Team][] [lang]                   |       |
-| Author stabilization report    | *Goal point of contact, typically* |       |
-| Author stabilization PR        | *Goal point of contact, typically* |       |
-| Stabilization decision         | ![Team][] [lang]                   |       |
+| Task                        | Owner(s) or team(s)                | Notes |
+|-----------------------------|------------------------------------|-------|
+| Author Reference PR         | *Goal point of contact, typically* |       |
+| Review/revise Reference PR  | ![Team][] [lang-docs]              |       |
+| Lang-team champion          | ![Team][] [lang]                   |       |
+| Author stabilization report | *Goal point of contact, typically* |       |
+| Author stabilization PR     | *Goal point of contact, typically* |       |
+| Stabilization decision      | ![Team][] [lang]                   |       |
 
 ### Stabilize library feature
 
-> *Standard library features follow the [libs-api stabilization process](https://rustc-dev-guide.rust-lang.org/stability.html#stabilizing-a-library-feature). 
+> *Standard library features follow the [libs-api stabilization process](https://rustc-dev-guide.rust-lang.org/stability.html#stabilizing-a-library-feature).
 
 | Task                           | Owner(s) or team(s)                | Notes |
 |--------------------------------|------------------------------------|-------|