fixes requested by @denesh

Author: derekwyatt

overviews/quasiquotes/definition-details.md

@@ -78,7 +78,7 @@ The template consists of:
         scala> val q"new { ..$earlydefns } with RequiresX" = withx
         earlydefns: List[universe.Tree] = List(val x = 1)
 
-2. List of parents. A list of type identifiers with optional arguments to the first one in the list:
+2. List of parents. A list of type identifiers where only the first one in the list may have optional type and value arguments.  This is because the first parent must be a class and subsequent parents are just traits that don't yet accept arguments:
 
         scala> val q"new ..$parents"  = q"new Foo(1) with Bar[T]"
         parents: List[universe.Tree] = List(Foo(1), Bar[T])

overviews/quasiquotes/expression-details.md

@@ -557,7 +557,7 @@ While and do-while loops are low-level control structures that can be used when
 
 ## For and For-Yield Loops
 
-For and For-Yield expressions allow us to write a monadic style comprehension that desugar into calls to `map`, `flatMap`, `foreach` and `withFilter` methods:
+`for` and `for-yield` expressions allow us to write a monadic style comprehension that desugar into calls to `map`, `flatMap`, `foreach` and `withFilter` methods:
 
     scala> val `for-yield` = q"for (x <- xs; if x > 0; y = x * 2) yield x"
     for-yield: universe.Tree =
@@ -582,7 +582,7 @@ Similarly one can deconstruct the `for-yield` back into a list of enumerators an
     enums: List[universe.Tree] = List(`<-`((x @ _), xs), `if`(x.$greater(0)), (y @ _) = x.$times(2))
     body: universe.Tree = x
 
-It's important to mention that For and For-Yield do not cross-match each other:
+It's important to mention that `for` and `for-yield` do not cross-match each other:
 
     scala> val q"for (..$enums) $body" = `for-yield`
     scala.MatchError: ...

overviews/quasiquotes/hygiene.md

@@ -12,7 +12,7 @@ outof: 13
 
 The notion of hygiene has been widely popularized by macro research in Scheme. A code generator is called hygienic if it ensures the absence of name clashes between regular and generated code, preventing accidental capture of identifiers. As numerous experience reports show, hygiene is of great importance to code generation, because name binding problems are often non-obvious and lack of hygiene might manifest itself in subtle ways.
 
-Sophisticated macro systems such as Racket's have mechanisms that make macros hygienic without any effort from macro writers. In Scala we don't have automatic hygiene yet - both of our codegen facilities (compile-time codegen with macros and runtime codegen with toolboxes) require programmers to handle hygiene manually. Fixing this is our number one priority for 2.12 (see [future prospects](/overviews/quasiquotes/future.html)) but, in the meantime, you must know how to work around the absence of hygiene, which is what this section is about.
+Sophisticated macro systems such as Racket's have mechanisms that make macros hygienic without any effort from macro writers. In Scala we don't have automatic hygiene - both of our codegen facilities (compile-time codegen with macros and runtime codegen with toolboxes) require programmers to handle hygiene manually. You must know how to work around the absence of hygiene, which is what this section is about.
 
 Preventing name clashes between regular and generated code means two things. First, we must ensure that, regardless of the context in which we put generated code, its meaning will not change (*referential transparency*). Second, we must make certain that regardless of the context in which we splice regular code, its meaning will not change (often called *hygiene in the narrow sense*). Let's see what can be done to this end on a series of examples.