review fixes

Author: steveklabnik

posts/2019-01-17-Rust-1.32.0.md

@@ -31,7 +31,7 @@ information.
 
 #### The `dbg` macro
 
-First up, a quality of life improvement. Are you a "printf debugger"? If you are, and
+First up, a quality of life improvement. Are you a "print debugger"? If you are, and
 you've wanted to print out some value while working on some code, you have to do this:
 
 ```rust
@@ -67,7 +67,7 @@ If you run this program, you'll see:
 You get the file and line number of where this was invoked, as well as the
 name and value. Additionally, `println!` prints to the standard output, so
 you really should be using `eprintln!` to print to standard error. `dbg!`
-does the right thing and goes to `stderr` by default.
+does the right thing and goes to `stderr`.
 
 It even works in more complex circumstances. Consider this factorial example:
 
@@ -160,8 +160,8 @@ Long, long ago, Rust had a large, Erlang-like runtime. We chose to use
 [jemalloc] instead of the system allocator, because it often improved
 performance over the default system one. Over time, we shed more and more of
 this runtime, and eventually almost all of it was removed, but jemalloc
-didn't. We didn't have a way to choose a custom allocator, and so we couldn't
-really remove it without causing a regression for people who do need
+was not. We didn't have a way to choose a custom allocator, and so we
+couldn't really remove it without causing a regression for people who do need
 jemalloc.
 
 Also, saying that `jemalloc` was always the default is a bit UNIX-centric,
@@ -232,11 +232,12 @@ already-existing `*` for "zero or more" and `+` for "one or more."
 
 #### Final module improvements
 
-In Rust 1.30.0, [we announced several improvements to the module
-system](https://blog.rust-lang.org/2018/12/06/Rust-1.31-and-rust-2018.html#module-system-changes).
-We have one last tweak landing in 1.32.0 and the 2018 edition. Nicknamed
-["uniform paths"](https://github.com/rust-lang/rust/pull/56759/), the simplest way to explain
-it is to show you this code:
+In the past two releases, we announced several improvements to the module
+system. We have one last tweak landing in 1.32.0 and the 2018 edition.
+Nicknamed ["uniform
+paths"](https://github.com/rust-lang/rust/pull/56759#issuecomment-450051210),
+it permits previously invalid import path statements to be resolved exactly
+the same way as non-import paths. For example:
 
 ```rust
 enum Color { Red, Green, Blue }
@@ -245,19 +246,25 @@ use Color::*;
 ```
 
 This code did *not* previously compile, as `use` statements had to start with
-`super`, `self`, or `crate`. With this change, this code will work, and do
-what you probably expect: import the variants of the `Color` enum defined
-above the `use` statement.
+`super`, `self`, or `crate`. Now that the compiler supports uniform paths,
+this code will work, and do what you probably expect: import the variants of
+the `Color` enum defined above the `use` statement.
 
 With this change in place, we've completed our efforts at revising the module
 system. We hope you've been enjoying the simplified system so far!
 
 ### Library stabilizations
 
 We talked above about the `dbg!` macro, which is a big library addition.
-Beyond that, 19 functions were made `const fn`s, and all 72 combinations of
-the `to_*_bytes` and `from_*_bytes` methods, where `*` is one of `{be, le,
-ne}`, were added to `{usize,isize,i8,i16,i32,i64,i128,u8,u16,u32,u64,u128}`.
+Beyond that, 19 functions were made `const fn`s, and all integral numeric
+primitives now provide conversion functions to and from byte-arrays with
+specified edianness. These six functions are named `to_<endian>_bytes` and
+`from_<endian>_bytes`, where `<endian>` is one of:
+
+* `ne` - native endianness
+* `le` - little endian
+* `be` - big endian
+
 See the [detailed release notes][notes] for more details.
 
 ### Cargo features