Some more wording tweaks

Author: Mark-Simulacrum

posts/2025-01-09-Rust-1.84.0.md

@@ -19,20 +19,23 @@ If you'd like to help us out by testing future releases, you might consider upda
 
 ## What's in 1.84.0 stable
 
-### Cargo can use toolchain version for library version selection
+### Cargo considers Rust versions for dependency version selection 
 
 1.84.0 stabilizes the minimum supported Rust version (MSRV) aware resolver,
 which uses the declared [minimum supported Rust version](https://doc.rust-lang.org/cargo/reference/rust-version.html) from
 dependencies, if available, to improve package version selection. Rust version
 aware selection allows library authors to easily adopt newer Rust versions
-while avoiding breaking consumers needing compatibility with older toolchains.
+while avoiding breaking consumers who want to use older Rust compilers.
 
 You can opt-in to the MSRV-aware resolver via [`.cargo/config.toml`](https://doc.rust-lang.org/cargo/reference/config.html#resolverincompatible-rust-versions):
+
 ```toml
 [resolver]
 incompatible-rust-versions = "fallback"
 ```
+
 Then when adding a dependency:
+
 ```console
 $ cargo add clap
     Updating crates.io index
@@ -44,6 +47,7 @@ warning: ignoring clap@4.5.23 (which requires rustc 1.74) to maintain demo's rus
 ```
 
 When [verifying the latest dependencies in CI](https://doc.rust-lang.org/cargo/guide/continuous-integration.html#verifying-latest-dependencies), you can override this:
+
 ```console
 $ CARGO_RESOLVER_INCOMPATIBLE_RUST_VERSIONS=allow cargo update
     Updating crates.io index
@@ -60,10 +64,10 @@ toolchain (and avoid running `cargo update`). Now, those users will be able to
 automatically use older library versions compatible with their older toolchain.
 In the future, we expect this to provide more flexibility for library authors
 to select their preferred support strategy for Rust versions, with the toolchain
-helping users on older toolchains avoid breakage.
+helping users on older toolchains avoid breakage. See also the [detailed guidance](https://doc.rust-lang.org/beta/cargo/reference/rust-version.html#setting-and-updating-rust-version)
+on what to consider when making a choice of supported version.
 
-The new resolver will be enabled by default with the 2024 edition (expected to
-stabilize in 1.85), but can be enabled as of 1.84 by setting
+The new resolver will be enabled by default when optin into the 2024 edition (will stabilize in 1.85), but can be enabled as of 1.84 by setting
 [`package.resolver = "3"`](https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions) in the Cargo.toml manifest file, or
 [`resolver.incompatible-rust-versions = "fallback"`](https://doc.rust-lang.org/cargo/reference/config.html#resolverincompatible-rust-versions) in the Cargo configuration file.
 
@@ -93,7 +97,7 @@ engine used relatively esoteric code. It also improves our ability to detect
 where impls do *not* overlap, allowing more code to be written in some cases.
 
 For more details, see a [previous blog post](https://blog.rust-lang.org/inside-rust/2024/12/04/trait-system-refactor-initiative.html)
-and the [stabilization report](https://github.com/rust-lang/rust/pull/130654)
+and the [stabilization report](https://github.com/rust-lang/rust/pull/130654).
 
 [Crater]: https://github.com/rust-lang/crater/