Edits from comments

Author: carols10cents

_posts/2017-06-08-Rust-1.18.md

@@ -22,7 +22,7 @@ appropriate page on our website, and check out the [detailed release notes for
 
 ### What's in 1.18.0 stable
 
-Rust 1.18.0 is similar to many of our releases: no big bombshells, just a number
+Rust 1.18.0 is similar to many of our releases: no big surprises, just a number
 of improvements, cleanups, and new features.
 
 One of the largest changes is a long time coming: core team members Carol
@@ -31,16 +31,15 @@ Programming Language", the official book about Rust. It's being [written openly
 on GitHub](https://github.com/rust-lang/book), and has over a hundred
 contributors in total. This release [includes the first draft of the second
 edition in our online documentation](https://doc.rust-lang.org/stable/book/).
-19 out of 20 chapters have a draft; the draft of chapter 20 will land in the
-Rust 1.19. When the book is done, a print version will be made available through
-[No Starch Press](https://www.nostarch.com/Rust), if you'd like a paper copy.
-While first drafts of the chapters are available, we're still working with the
-editors at No Starch to improve the text, so there's more to do, but we wanted
+19 out of 20 chapters have a draft; the draft of chapter 20 will land in Rust
+1.19. When the book is done, a print version will be made available through [No
+Starch Press](https://www.nostarch.com/Rust), if you'd like a paper copy. We're
+still working with the editors at No Starch to improve the text, but we wanted
 to start getting a wider audience now. The new edition is a complete re-write
 from the ground up, using the last two years of knowledge we've gained from
 teaching people Rust. You'll find brand-new explanations for a lot of Rust's
 core concepts, new projects to build, and all kinds of other good stuff. Please
-check it out and let us know what you think!
+check it out and [let us know what you think](https://github.com/rust-lang/book/issues/new)!
 
 As for the language itself, an old feature has learned some new tricks: the
 `pub` keyword has been expanded a bit. Experienced Rustaceans will know that
@@ -61,12 +60,14 @@ users. This was *possible* with the current module system, but often very awkwar
 You can also specify a path, like this:
 
 ```rust
-pub(a::b::c) foo;
+pub(in a::b::c) foo;
 ```
 
 This means "usable within the hierarchy of `a::b::c`, but not elsewhere." This
 feature was defined in [RFC
 1422](https://github.com/rust-lang/rfcs/blob/master/text/1422-pub-restricted.md)
+and [is documented in the
+reference](https://doc.rust-lang.org/stable/reference/visibility-and-privacy.html#pubin-path-pubcrate-pubsuper-and-pubself).
 
 For our Windows users, Rust 1.18.0 has [a new attribute,
 `#![windows_subsystem]`](https://github.com/rust-lang/rust/pull/40870). It
@@ -147,16 +148,18 @@ to use a `#[repr]` attribute to guarantee a particular layout if you rely on it.
 
 We've been planning on moving `rustdoc` to use a CommonMark compliant markdown
 parser for a long time now. However, just switching over can introduce
-regressions where the CommonMark spec differs from our existing parser, Hoedown.
-As part of the transition plan, [a new flag has been added to
-`rustdoc`](https://github.com/rust-lang/rust/pull/40338), `--enable-commonmark`.
-This will use the new parser instead of the old one. Please give it a try! There's
-no scenario we know of where tweaking your markdown gets identical results on both
-parsers.
-
-Finally, compiling `rustc` itself is now [15%-20% faster](https://github.com/rust-lang/rust/pull/41469). Each commit message in this PR
-goes over the details, but the short of it is that there were some inefficient
-things, and now they've been cleaned up.
+regressions where the CommonMark spec differs from our existing parser,
+Hoedown. As part of the transition plan, [a new flag has been added to
+`rustdoc`](https://github.com/rust-lang/rust/pull/40338),
+`--enable-commonmark`. This will use the new parser instead of the old one.
+Please give it a try! As far as we know, both parsers will produce identical
+results, but we'd be interested in knowing if you find a scenario where the
+rendered results differ!
+
+Finally, compiling `rustc` itself is now [15%-20%
+faster](https://github.com/rust-lang/rust/pull/41469). Each commit message in
+this PR goes over the details, but the short of it is that there were some
+inefficient things, and now they've been cleaned up.
 
 See the [detailed release notes][notes] for more.
 
@@ -166,7 +169,7 @@ Seven new APIs were stabilized this release:
 
 - [`Child::try_wait`] is a non-blocking form of `Child::wait`.
 - [`HashMap::retain`] and  [`HashSet::retain`] bring the `retain` API `Vec<T>` has to these two hash data structures.
-- [`PeekMut::pop`] lets you pop stuff off of a `BinaryHeap<T>`
+- [`PeekMut::pop`] lets you pop the top element from a `BinaryHeap<T>` after you've already peeked at it without needing to reorder the heap a second time.
 - [`TcpStream::peek`], [`UdpSocket::peek`], [`UdpSocket::peek_from`] let you peek at a stream or socket.
 
 [`Child::try_wait`]: https://doc.rust-lang.org/std/process/struct.Child.html#method.try_wait
@@ -184,7 +187,7 @@ See the [detailed release notes][notes] for more.
 Cargo has [added support](https://github.com/rust-lang/cargo/pull/3842) for the Pijul VCS,
 which is written in Rust. `cargo new my-awesome-project --vcs=pijul` will get you going!
 
-To suppliment the `--all` flag, Cargo now has [several new
+To supplement the `--all` flag, Cargo now has [several new
 flags](https://github.com/rust-lang/cargo/pull/3901) such as `--bins`,
 `--examples`, `--tests`, and `--benches`, which will let you build all programs of
 that type.