Address review feedback

Co-authored-by: lcnr <rust@lcnr.de> Co-authored-by: Ralf Jung <post@ralfj.de> Co-authored-by: waffle <waffle.lapkin@gmail.com>
rust-lang · bors · Jul 29, 2025 · Jan 23, 2025 · Jan 23, 2025 · Jun 19, 2025
commit 857f46eb393896e0240969f6c6b204ac015d60a9
diff --git a/src/doc/rustc-dev-guide/src/implementing_new_features.md b/src/doc/rustc-dev-guide/src/implementing_new_features.md
@@ -209,7 +209,7 @@ tests/ui/feature-gates/ --bless`.
 
 ## Call for testing
 
-Once the implementation is complete, the feature will be available to nightly users, but not yet part of stable Rust. This is a good time to write a blog post on [one of the Rust blogs](https://github.com/rust-lang/blog.rust-lang.org/) and issue a call for testing (here are two example [blog](https://blog.rust-lang.org/inside-rust/2024/08/09/async-closures-call-for-testing.html) [posts](https://blog.rust-lang.org/2024/09/05/impl-trait-capture-rules.html) to give you the idea). The post should highlight how the feature works, what areas you'd like people to play with, and how they can supply feedback.
+Once the implementation is complete, the feature will be available to nightly users, but not yet part of stable Rust. This is a good time to write a blog post on [one of the Rust blogs](https://github.com/rust-lang/blog.rust-lang.org/) and issue a call for testing (here are three [example](https://blog.rust-lang.org/2021/08/03/GATs-stabilization-push.html) [blog](https://blog.rust-lang.org/inside-rust/2024/08/09/async-closures-call-for-testing.html) [posts](https://blog.rust-lang.org/2024/09/05/impl-trait-capture-rules.html) to give you the idea). The post should highlight how the feature works, what areas you'd like people to play with, and how they can supply feedback.
 
 ## Affiliated work
 

diff --git a/src/doc/rustc-dev-guide/src/stabilization_guide.md b/src/doc/rustc-dev-guide/src/stabilization_guide.md
@@ -52,7 +52,7 @@ The [template][srt] includes a series of questions that aim to surface interconn
 The stabilization report is typically posted as the main comment on the stabilization PR (see the next section).
 If you'd like to develop the stabilization report incrementally, we recommend adding it to 
 
-## Stabilization PR
+## Stabilization PR for a language feature
 
 *This is for stabilizing language features.  If you are stabilizing a library
 feature, see [the stabilization chapter of the std dev guide][std-guide-stabilization] instead.*

diff --git a/src/doc/rustc-dev-guide/src/stabilization_report_template.md b/src/doc/rustc-dev-guide/src/stabilization_report_template.md
@@ -28,10 +28,10 @@ An example for async closures: https://rustc-dev-guide.rust-lang.org/coroutine-c
 
 ### What outstanding bugs in the issue tracker involve this feature? Are they stabilization-blocking?
 
-### Summarize contributors to the feature by name for recognition and assuredness that people involved in the feature agree with stabilization 
-
 ### What FIXMEs are still in the code for that feature and why is it ok to leave them there?
 
+### Summarize contributors to the feature by name for recognition and assuredness that people involved in the feature agree with stabilization 
+
 ### Which tools need to be adjusted to support this feature. Has this work been done?
 
 *Consider rustdoc, clippy, rust-analyzer, rustfmt, rustup, docs.rs.*
@@ -42,7 +42,7 @@ An example for async closures: https://rustc-dev-guide.rust-lang.org/coroutine-c
 
 (Be sure to link to tests demonstrating that these tests are being done.)
 
-### Can users use this feature to introduce undefined behavior? (Describe.)
+### Can users use this feature to introduce undefined behavior, or use this feature to break the abstraction of Rust and expose the underlying assembly-level implementation? (Describe.)
 
 ### What updates are needed to the reference/specification? (link to PRs when they exist)