Minor edits for #155

- Minor edits to use an active voice, provide cross-document links, and correct
  formatting.

Author: weierophinney

doc/book/migration/to-v3-0.md

@@ -417,17 +417,16 @@ template using a variety of heuristics, including an explicit map provided
 during configuration, or auto-detection based on the controller class name.
 
 In version 2, the autodetection took into consideration the `__NAMESPACE__`
-route match parameter to derive subnamespaces or would omit them completely if
-`__NAMESPACE__` is not present. This caused issues when multiple modules shared
-a top-level namespace (e.g., `ZF\Apigility` and `ZF\Apigility\Admin`) if each
+route match parameter to derive subnamespaces, or would omit them completely if
+`__NAMESPACE__` was not present. This caused issues when multiple modules shared
+a top-level namespace (e.g., `ZF\Apigility` and `ZF\Apigility\Admin`) and each
 had a controller with the same name.
 
 To avoid naming conflicts, version 3 removes this aspect of autodetection, and
 instead provides exactly one workflow for mapping:
 
-- Strip the `Controller` subnamespace, if present (e.g.,
-  the namespace `Application\Controller\` is normalized to
-  `Application\`).
+- Strip the `Controller` subnamespace, if present (e.g., the namespace
+  `Application\Controller\\` is normalized to `Application\\`).
 - Strip the `Controller` suffix in the class name, if present (e.g.,
   `IndexController` is normalized to `Index`).
 - Inflect CamelCasing to dash-separated (e.g., `ShowUsers` becomes
@@ -439,8 +438,8 @@ As a full example, the controller service name
 `test-something/with/camel-case`, regardless of the `__NAMESPACE__` value
 provided in routing configuration.
 
-Similar behavior in version 2 could be achieved with namespace whitelisting in
-controller to template map
+If needed, you can emulate the version 2 behavior in version 3 via namespace
+whitelisting in the controller <=> template map.
 
 ## Zend\Mvc\View\SendResponseListener
 

doc/book/quick-start.md

@@ -178,23 +178,25 @@ That's it. Save the file.
 
 As per PSR-0, modules should be named following the rule: `<Vendor Name>\<Namespace>\*`.
 
-Since version 3.0 default template name resolver uses fully qualified controller
-class name, stripping only `\Controller\` subnamespace, if present.
-For example, `AwesomeMe\MyModule\Controller\HelloWorldController` is resolved
-to template name `awesome-me/my-module/hello-world`.
-
-For prior versions default was to strip subnamespaces but optional mapping rules
-allowed to whitelist namespaces in module configuration to enable current
-resolver behavior:
+Since version 3.0, the default template name resolver uses fully qualified
+controller class names, stripping only the `\Controller\\` subnamespace, if
+present.  For example, `AwesomeMe\MyModule\Controller\HelloWorldController`
+resolves to the template name `awesome-me/my-module/hello-world` via the
+following configuration:
 
 ```php
 'view_manager' => array(
     'controller_map' => array(
-        '<AwesomeMe\MyModule>' => true,
+        'AwesomeMe\MyModule' => true,
     ),
 ),
 ```
 
+(In v2 releases, the default was to strip subnamespaces, but optional mapping rules
+allowed whitelisting namespaces in module configuration to enable current
+resolver behavior. See the [migration guide](migration/to-v3-0.md#zendmvcviewinjecttemplatelistener)
+for more details.)
+
 ## Create a Route
 
 Now that we have a controller and a view script, we need to create a route to it.