tweaks as per @aturon's feedback

Author: steveklabnik

_posts/2016-01-21-Rust-1.6.md

@@ -22,19 +22,22 @@ a change to [Crates.io](https://crates.io).
 
 #### libcore stabilization
 
-The largest new feature in 1.6 is that [`libcore`] is now stable! Rust’s standard
-library is two-tiered: `libcore` contains a lot of functionality, but more important
-is what it does _not_ contain: significant dependencies. `libcore` is completely
-platform agnostic, and requires only a handful of external symbols to be defined.
-Rust’s `libstd` builds on top of `libcore`, adding support for memory allocation,
-I/O, and concurrency. Applications using Rust in the embedded space, as well as
-those writing operating systems, often eschew `libstd`, using only `libcore`.
+The largest new feature in 1.6 is that [`libcore`] is now stable! Rust’s
+standard library is two-tiered: there’s a small core library, `libcore`, and
+the full standard library, `libstd`, that builds on top of it. `libcore` is
+completely platform agnostic, and requires only a handful of external symbols
+to be defined. Rust’s `libstd` builds on top of `libcore`, adding support for
+memory allocation, I/O, and concurrency. Applications using Rust in the
+embedded space, as well as those writing operating systems, often eschew
+`libstd`, using only `libcore`.
 
 [`libcore`]: http://doc.rust-lang.org/nightly/core/
 
-`libcore` being stabilized is a major step towards being able to write the lowest
-levels of software using stable Rust. There’s still future work to be done, however,
-so expect to hear more about this in future release notes.
+`libcore` being stabilized is a major step towards being able to write the
+lowest levels of software using stable Rust. There’s still future work to be
+done, however. This will allow for a library ecosystem to develop around
+`libcore`, but _applications_ are not fully supported yet. Expect to hear more
+about this in future release notes.
 
 #### Library stabilizations
 
@@ -52,7 +55,7 @@ Finally, `Vec::extend_from_slice()`, which was previously known as
 `push_all()`. This method has a significantly faster implementation than the
 more general `extend()`.
 
-See the detailed release notes linked above for more.
+See the [detailed release notes][notes] for more.
 
 #### Crates.io disallows wildcards
 
@@ -65,8 +68,11 @@ describing their dependencies. In other words, this is not allowed:
 regex = "*"
 ```
 
-Instead, you must actually specify a specific version or range of versions,
-using one of the `semver` crate’s various options: `^`, `~`, or `=`.
+Instead, you must actually specify [a specific version or range of
+versions][versions], using one of the `semver` crate’s various options: `^`,
+`~`, or `=`.
+
+[versions]: http://doc.crates.io/crates-io.html#using-cratesio-based-crates
 
 A wildcard dependency means that you work with any possible version of your
 dependency. This is highly unlikely to be true, and causes unnecessary breakage