Address nits by @ScottAbbey

thanks! ❤️

Author: steveklabnik

_posts/2017-04-27-Rust-1.17.md

@@ -78,10 +78,11 @@ let p = Point {
 That is, the `x, y` form will assume that its values are set to a varaible
 with the same name in its scope.
 
-In a similar way, it's common for new Rustaceans to try to use `+` to add two
-`&str`s together. This doesn't work, you can only add `String + &str`. As
-such, [a new error message](https://github.com/rust-lang/rust/pull/39116)
-was added to help users who make this mistake:
+For another small quality of life improvement, it's common for new Rustaceans to
+try to use `+` to add two `&str`s together. This doesn't work, you can only add
+`String + &str`. As such, [a new error
+message](https://github.com/rust-lang/rust/pull/39116) was added to help users
+who make this mistake:
 
 ```rust
 // code
@@ -123,9 +124,9 @@ into Cargo](https://github.com/rust-lang/cargo/pull/3664), and will be assumed i
 and you can use `build = false` to opt out.
 
 This release marks [the removal](https://github.com/rust-lang/rust/pull/39431)
-of the old `Makefile` based build system. We announced this new system in 1.15,
-which is written in Rust and primarily uses Cargo to drive the build, and now
-it is mature enough to always use.
+of the old `Makefile` based build system. The new system, announced in Rust
+1.15, is written in Rust and primarily uses Cargo to drive the build. It is now
+mature enough to be the only build system.
 
 As part of that change, packages from crates.io can now be used within Rust's
 build system. The first one to be added was [mdBook](https://crates.io/crates/mdbook),
@@ -140,7 +141,7 @@ In addition, see those links to their respective repositories; they've been
 moved out of tree. Also, we've added a fourth book, still in-tree: [The
 Unstable Book](https://doc.rust-lang.org/stable/unstable-book/). This
 provides an overview of unstable features by name, contains links to their
-tracking issues, and may contain initial documentation of the feature.
+tracking issues, and may contain initial documentation.
 If there's a feature you want to see stabilized, please get involved on
 its tracking issue!