Small punctuation and spelling fixes

Author: carols10cents

_posts/2017-07-20-Rust-1.19.md

@@ -23,12 +23,12 @@ appropriate page on our website, and check out the [detailed release notes for
 ### What's in 1.19.0 stable
 
 Rust 1.19.0 has some long-awaited features, but first, a note for our Windows
-users. On Windows, Rust relies on `link.exe` for linking, which you can get
-via the "Microsoft Visual C++ Build Tools." With the recent release of Visual
-Studio 2017, the directory structure for these tools has changed. As such, you
-had to stick with the 2015 tools to use Rust, or use a workaround (such as running
-`vcvars.bat`). In 1.19.0, `rustc` now knows how to find the 2017 tools, and so
-they work without a workaround.
+users. On Windows, Rust relies on `link.exe` for linking, which you can get via
+the "Microsoft Visual C++ Build Tools." With the recent release of Visual
+Studio 2017, the directory structure for these tools has changed. As such, to
+use Rust, you had to stick with the 2015 tools or use a workaround (such as
+running `vcvars.bat`). In 1.19.0, `rustc` now knows how to find the 2017 tools,
+and so they work without a workaround.
 
 On to new features! Rust 1.19.0 is the first release that supports [`union`s]:
 
@@ -52,7 +52,7 @@ unsafe { u.f1 = 5 };
 let value = unsafe { u.f1 };
 ```
 
-Pattern matching works too: 
+Pattern matching works too:
 
 ```rust
 fn f(u: MyUnion) {
@@ -75,7 +75,7 @@ API wrappers for those libraries significantly easier. Additionally, from [its R
 > bits of aligned pointers to distinguish cases.
 
 This feature has been long awaited, and there's still more improvements to come.
-For now, `union`s can only include `Copy` types, and may not implement `Drop`.
+For now, `union`s can only include `Copy` types and may not implement `Drop`.
 We expect to lift these restrictions in the future.
 
 [`union`s]: https://github.com/rust-lang/rust/pull/42068
@@ -101,7 +101,7 @@ loop {
 let x = loop { break 7; };
 ```
 
-Rust has tradititionally positioned itself as an "expression oriented language", that is,
+Rust has traditionally positioned itself as an "expression oriented language", that is,
 most things are expressions that evaluate to a value, rather than statements. `loop` stuck
 out as strange in this way, as it was previously a statement.
 
@@ -116,28 +116,28 @@ to a function pointer](https://github.com/rust-lang/rust/pull/42162):
 let f: fn(i32) -> i32 = |x| x + 1;
 ```
 
-We now produce [xz compressed tarballs](https://github.com/rust-lang/rust-installer/pull/57), and prefer them by default,
-making the data transfer smaller and faster. `gzip`'d tarballs are still produced,
+We now produce [xz compressed tarballs](https://github.com/rust-lang/rust-installer/pull/57) and prefer them by default,
+making the data transfer smaller and faster. `gzip`'d tarballs are still produced
 in case you can't use `xz` for some reason.
 
 The compiler can now [bootstrap on
 Android](https://github.com/rust-lang/rust/pull/41370). We've long supported Android
 in various ways, and this continues to improve our support.
 
 Finally, a compatibility note. Way back when we were running up to Rust 1.0, we did
-a huge push to verify everything that was being marked as stable, and as unstable.
+a huge push to verify everything that was being marked as stable and as unstable.
 We overlooked one thing, however: `-Z` flags. The `-Z` flag to the compiler enables
 unstable flags. Unlike the rest of our stability story, you could still use `-Z` on
 stable Rust. Back in April of 2016, in Rust 1.8, we made the use of `-Z` on stable
-or beta produce a warning, and over a year later, we're fixing this hole in our
+or beta produce a warning. Over a year later, we're fixing this hole in our
 stability story by [disallowing `-Z` on stable and beta](https://github.com/rust-lang/rust/pull/41751).
 
 See the [detailed release notes][notes] for more.
 
 #### Library stabilizations
 
 The largest new library feature is the [`eprint!` and `eprintln!` macros].
-These work exactly the same as `print!` and `printn!`, but instead write
+These work exactly the same as `print!` and `printn!` but instead write
 to standard error, as opposed to standard output.
 
 [`eprint!` and `eprintln!` macros]: https://github.com/rust-lang/rust/pull/41192
@@ -174,10 +174,10 @@ See the [detailed release notes][notes] for more.
 
 #### Cargo features
 
-Cargo mostly recieved small but valuable improvements in this relase. The
+Cargo mostly received small but valuable improvements in this release. The
 largest is possibly that [Cargo no longer checks out a local working
-directory for the crates.io index][cargo/4026] This should provide smaller
-file size for the registry, and improve cloning times, especially on Windows
+directory for the crates.io index][cargo/4026]. This should provide smaller
+file size for the registry and improve cloning times, especially on Windows
 machines.
 
 Other improvements: