Apply suggestions from code review

Co-authored-by: Camelid <camelidcamel@gmail.com>

Author: jyn514

src/stability.md

@@ -74,13 +74,13 @@ To stabilize a feature, follow these steps:
 
 0. Ask a **@T-libs** member to start an FCP on the tracking issue and wait for
    the FCP to complete (with `disposition-merge`).
-1. Change `#[unstable]` to `#[stable(since = "version")]`.
+1. Change `#[unstable(...)]` to `#[stable(since = "version")]`.
    `version` should be the *current nightly*, i.e. stable+2. You can see which version is
-   currently nightly [on Forge](https://forge.rust-lang.org/#current-release-versions).
-2. Remove `#![feature]` from any test or doc-test for this API. If the feature is used in the
+   the current nightly [on Forge](https://forge.rust-lang.org/#current-release-versions).
+2. Remove `#![feature(...)]` from any test or doc-test for this API. If the feature is used in the
    compiler or tools, remove it from there as well.
-3. If applicable, change `#[rustc_const_unstable]` to `#[rustc_const_stable(since = "version")]`.
-4. Open a PR against `rust-lang/rust`
+3. If applicable, change `#[rustc_const_unstable(...)]` to `#[rustc_const_stable(since = "version")]`.
+4. Open a PR against `rust-lang/rust`.
    - Add the appropriate labels: `@rustbot modify labels: +T-libs`.
    - Link to the tracking issue and say "Closes #XXXXX".
 

src/stabilization_guide.md

@@ -1,7 +1,7 @@
 # Request for stabilization
 
 **NOTE**: this page is about stabilizing language features.
-For stabilizing library features, see [Stabilizing a library feature].
+For stabilizing *library* features, see [Stabilizing a library feature].
 
 [Stabilizing a library feature]: ./stability.md#stabilizing-a-library-feature