Apply some suggestions from programmerjake

Co-authored-by: Jacob Lifshay <programmerjake@gmail.com>

Author: Urgau

posts/2024-04-29-check-cfg.md

@@ -11,9 +11,9 @@ The Cargo and Compiler team are delighted to announce that starting with Rust 1.
 
 This can help with verifying that the crate is correctly handling conditional compilation for different target platforms or features. It ensures that the cfg settings are consistent between what is intended and what is used, helping to catch potential bugs or errors early in the development process.
 
-Addressing a common pitfall for new and advanced users.
+This addresses a common pitfall for new and advanced users.
 
-This is another step to our commitment to provide user-focused tooling and we are eager and excited to finally see it fixed, more than two years since the original [RFC 3013](https://github.com/rust-lang/rfcs/pull/3013)[^1].
+This is another step to our commitment to provide user-focused tooling and we are eager and excited to finally see it fixed, after more than two years since the original [RFC 3013](https://github.com/rust-lang/rfcs/pull/3013)[^1].
 
 [^1]: The stabilized implementation and RFC 3013 diverge significantly, in particular there is only one form for `--check-cfg`: `cfg()` (instead of `values()` and `names()` being incomplete and subtlety incompatible with each other).
 
@@ -58,7 +58,7 @@ Some crates use custom cfgs that they either expected from the environment (`RUS
 
 [^2]: `cargo::rustc-check-cfg` take action since Rust 1.80, between Rust 1.77 and Rust 1.79 *(included)* it silently did nothing and before that (so Rust 1.76 and below) it warned when used without the unstable Cargo `-Zcheck-cfg`.
 
-The syntax to use is described in the [rustc book](https://doc.rust-lang.org/rustc/index.html) section [checking configuration](TODO), but in a nut shell the basic syntax of `--check-cfg` is:
+The syntax to use is described in the [rustc book](https://doc.rust-lang.org/rustc/index.html) section [checking configuration](TODO), but in a nutshell the basic syntax of `--check-cfg` is:
 
 > `cfg(name, values("value1", "value2", ..., "valueN"))`