Import some suggestions

Author: Mark-Simulacrum

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

@@ -22,10 +22,11 @@ If you'd like to help us out by testing future releases, you might consider upda
 ### 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. MSRV-aware
-aware selection allows library authors to easily adopt newer Rust versions
-while avoiding breaking consumers who want to use older Rust compilers.
+which prefers dependency versions compatible with the project's declared
+[MSRV](https://doc.rust-lang.org/cargo/reference/rust-version.html).
+With MSRV-aware version selection, the toil is reduced for maintainers to
+support older toolchains by not needing to manually select older versions for
+each dependency.
 
 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):
 
@@ -55,24 +56,21 @@ $ CARGO_RESOLVER_INCOMPATIBLE_RUST_VERSIONS=allow cargo update
     Updating clap v4.0.32 -> v4.5.23
 ```
 
-Library authors should take the MSRV-aware resolver into account when deciding
+This gives library authors more flexibility when deciding
 their policy on adopting new Rust toolchain features. Previously, a library
 adopting features from a new Rust toolchain would force downstream users of
 that library who have an older Rust version to either upgrade their toolchain
 or manually select an old version of the library compatible with their
 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. 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 when optin into the 2024 edition (will stabilize in 1.85), but can be enabled as of 1.84 by setting
+See the [documentation](https://doc.rust-lang.org/cargo/reference/rust-version.html#setting-and-updating-rust-version) for more considerations when deciding on an MSRV policy.
+
+The new resolver will be enabled by default for projects using the 2024 edition
+(which will stabilize in 1.85), but can be enabled in this release via
 [`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.
 
-Read [the documentation](https://doc.rust-lang.org/cargo/reference/resolver.html#rust-version) for more details.
-
 ### Migration to a new trait solver begins
 
 The Rust compiler is in the process of moving to a new implementation for the