Address feedback

Author: olafurpg

blog/_posts/2017-02-25-scalafix-v0.3.md

@@ -30,7 +30,7 @@ A symbol is a unique identifier of a single definition.
 For example, `println` from the standard library has the symbol `_root_.scala.Predef.println(Ljava/lang/Object;)V.`.
 The compiler is responsible for resolving names to symbols.
 
-Scalahost is a compiler plugin in the scala.meta project that extracts symbols from the compiler and maps them to scala.meta syntax trees.
+[Scalahost][] is a compiler plugin in the scala.meta project that extracts symbols from the compiler and maps them to scala.meta syntax trees.
 Scalahost emits the extracted symbols into a "semantic database".
 The semantic database can be persisted to files on disk and loaded for later analysis.
 Semantic databases from different compilation units, potentially produced by different
@@ -39,16 +39,18 @@ This opens possibilities for large-scale code analysis.
 
 The introduction of the scala.meta semantic API is a game changer for scalafix.
 The ability to resolve names to symbols opens possibilities for many scalafix rewrites.
+Before we cover a few example rewrites, let's look closer at what exactly "rewrite" means.
 
 ## Rewrite: meta.Tree => Seq[Patch]
-
+In a nutshell, a scalafix `Rewrite` is a `scala.meta.Tree => Seq[Patch]` function.
+The tree is backed by the scala.meta semantic API, so the rewrite is able to query for compiler information such as symbols.
 A scalafix `Patch` is a small operation that can produce a diff on a Scala source file.
 A patch can either be a "token patch" or a "tree patch".
 
 Token patches are low-level but give full control over how every detail in a source file is handled, for example formatting and comments.
 Example token patches are `Remove(token)` and `AddLeft(token, toAdd: String)`, which removes or prepends a string to `token`, respectively.
 
-Tree patches are high-level and allow rewrite author to declaratively explain what operation to perform.
+Tree patches are high-level and allow the rewrite author to declaratively explain what operation to perform.
 An example tree patch is `AddGlobalImport(importer)`, which adds a new import to the top of a file if it does not exist.
 Observe that `AddGlobalImport` does not worry about token-level details such as whether the user groups imports by prefix (`import a.{b, c}`) or not (`import a.b; import a.c`).
 
@@ -60,8 +62,6 @@ It can be harder to resolve conflicts on the token level since the original inte
 Unsolvable conflicts abort the refactoring.
 In the future, we hope to support more advanced conflict resolution strategies.
 
-In a nutshell, a scalafix `Rewrite` is a `scala.meta.Tree => Seq[Patch]` function.
-The tree is backed by the scala.meta semantic API, so the rewrite is able to query for compiler information such as symbols.
 To demonstrate how rewrites are implemented with scalafix v0.3, let's step through an example use-case.
 
 ## Example: Xor to Either
@@ -138,6 +138,7 @@ the early days of scalafix development and come up with several brilliant ideas
 for scalafix use-cases.
 
 
+[Scalahost]: https://github.com/scalameta/sbt-semantic-example
 [@ShaneDelmore]: https://twitter.com/ShaneDelmore
 [@olafurpg]: https://twitter.com/olafurpg
 [@xeno_by]: https://twitter.com/xeno_by