more fixes

Author: steveklabnik

_posts/2016-12-22-Rust-1.14.md

@@ -61,13 +61,6 @@ crate](https://crates.io/crates/webplatform), which exposes the DOM to Rust.
 [Rust Belt Rust]: http://www.rust-belt-rust.com/sessions/
 [todomvc]: http://timryan.org/rust-todomvc/
 
-Also of interest is [xargo], which allows for easy cross-compilation of Rust
-to bare-metal targets. If you're writing an operating system in Rust, or
-doing something interesting on a microcontroller, xargo can make your life a
-lot simpler.
-
-[xargo]: https://github.com/japaric/xargo
-
 Speaking of platforms, a large number of platforms have gained additional
 support:
 
@@ -97,6 +90,16 @@ more details.
 
 [platform support]: https://forge.rust-lang.org/platform-support.html
 
+Just like how the community is doing interesting work on the WebAssembly
+target, there's also neat things going on with increasing Rust's target support
+beyond what's listed above. [xargo] allows for easy cross-compilation of Rust
+to bare-metal targets. If you're writing an operating system in Rust, or doing
+something interesting on a microcontroller, xargo can make your life a lot
+simpler.
+
+[xargo]: https://github.com/japaric/xargo
+
+
 The landing of MIR over the last few releases means that a [number of
 improvements to compile times] have landed, with more coming in the future.
 
@@ -167,17 +170,20 @@ fit into particularly nice categories for this release. Here's the highlights:
 * [`println!()`, with no arguments, prints newline][36825].
   Previously, an empty string was required to achieve the same.
 * [`Wrapping` impls standard binary and unary operators on references, as well
-  as the `Sum` and `Product` iterators][37356]
+  as the `Sum` and `Product` iterators][37356], making references to these
+  types easier to use.
 * [Implement `From<Cow<str>> for String` and `From<Cow<[T]>> for
-  Vec<T>`][37326]
-* [Expand `.zip()` specialization to `.map()` and `.cloned()`][37230]
-* [Implement `RefUnwindSafe` for atomic types][37178]
-* [Specialize `Vec::extend` to `Vec::extend_from_slice`][37094]
+  Vec<T>`][37326]. These implementations make sense, but were not yet added.
+* [Expand `.zip()` specialization to `.map()` and `.cloned()`][37230] for improved performance.
+* [Implement `RefUnwindSafe` for atomic types][37178], as these types are
+  "unwind safe," though that wasn't obvious at first.
+* [Specialize `Vec::extend` to `Vec::extend_from_slice`][37094] for performance gains.
 * [Don't reuse `HashMap` random seeds][37470]. This helps to mitigate one type
   of DDoS attack.
 * [The internal memory layout of `HashMap` is more cache-friendly, for
   significant improvements in some operations][36692]
-* [Impl `Add<{str, Cow<str>}>` for `Cow<str>`][36430]
+* [Impl `Add<{str, Cow<str>}>` for `Cow<str>`][36430]. We already support `Add`
+  for other string types, so not having it on `Cow` is inconsistent.
 
 [36825]: https://github.com/rust-lang/rust/issues/36825
 [37356]: https://github.com/rust-lang/rust/issues/37356
@@ -193,10 +199,10 @@ See the [detailed release notes][notes] for more.
 
 #### Cargo features
 
-As for Cargo, [RFC 1721] has been implemented. The motivation for this feature
-is that Cargo can now compile objects for statically linking against the msvcrt
-on the MSVC platform. But, mechanically speaking, this means that Cargo will
-now pass along the values printed by `rustc --print cfg` to build scripts.
+As for Cargo, [RFC 1721] has been implemented. Cargo will now pass along the
+values printed by `rustc --print cfg` to build scripts. The motivation for this
+feature is that Cargo can now compile objects for statically linking against
+the msvcrt on the MSVC platform.
 
 [RFC 1721]: https://github.com/rust-lang/rfcs/blob/master/text/1721-crt-static.md