Documentation updates

- removed white characters at the end of the lines
- changed links to the documentation to docs.zendframework.com

Author: michalbundyra

docs/book/controllers.md

@@ -81,7 +81,7 @@ public function getServiceLocator();
 
 > #### ServiceLocatorInterface is deprecated
 >
-> `ServiceLocatorAwareInterface` [was removed from zend-servicemanager v3.0](http://zendframework.github.io/zend-servicemanager/migration/#miscellaneous-interfaces-traits-and-classes),
+> `ServiceLocatorAwareInterface` [was removed from zend-servicemanager v3.0](http://docs.zendframework.com/zend-servicemanager/migration/#miscellaneous-interfaces-traits-and-classes),
 > and, as such, starting in zend-mvc 2.7.0, the `AbstractController`
 > implementation no longer implements the interface, though it implements the
 > methods the interface defines; this allows forwards compatibility with
@@ -92,7 +92,7 @@ public function getServiceLocator();
 > pulling them from a composed `ServiceManager` instance.
 >
 > In cases where an object will not be used in all code paths, we recommend
-> splitting into discrete controllers, or using [lazy services](http://zendframework.github.io/zend-servicemanager/lazy-services/).
+> splitting into discrete controllers, or using [lazy services](http://docs.zendframework.com/zend-servicemanager/lazy-services/).
 
 ### EventManagerAware
 

docs/book/index.html

@@ -1,7 +1,7 @@
 <div class="container">
   <div class="jumbotron">
     <h1>zend-mvc</h1>
-    
+
     <p>Zend Framework's event-driven MVC layer, including MVC Applications, Controllers, and Plugins.</p>
 
     <pre><code class="language-bash">$ composer require zendframework/zend-mvc</code></pre>

docs/book/intro.md

@@ -257,8 +257,8 @@ If you do not want these actions, or want to provide alternatives, you can do so
 The second action you can take with the configured `Application` is to `run()`
 it. Calling this method performs the following:
 
-- it triggers the "route" event, 
-- followed by the "dispatch" event, and, depending on execution, 
+- it triggers the "route" event,
+- followed by the "dispatch" event, and, depending on execution,
 - the "render" event
 
 When done, it triggers the "finish" event, and then returns the response

docs/book/middleware.md

@@ -2,7 +2,7 @@
 
 [PSR-7](http://www.php-fig.org/psr/psr-7/) defines interfaces for HTTP messages,
 and is now being adopted by many frameworks; Zend Framework itself offers a
-parallel microframework targeting PSR-7 with [Expressive](https://zendframework.github.io/zend-expressive).
+parallel microframework targeting PSR-7 with [Expressive](https://docs.zendframework.com/zend-expressive).
 What if you want to dispatch PSR-7 middleware from zend-mvc?
 
 zend-mvc currently uses [zend-http](https://github.com/zendframework/zend-http)
@@ -61,7 +61,7 @@ http-middleware instance. These will then be piped into a
 present in the array.
 
 > ### No action required
-> 
+>
 > Unlike action controllers, middleware typically is single purpose, and, as
 > such, does not require a default `action` parameter.
 
@@ -99,7 +99,7 @@ Starting in 3.1.0, the `MiddlewareListener` always adds middleware to a
 `Zend\Stratigility\MiddlewarePipe` instance, and invokes it as
 [http-interop/http-middleware](https://github.com/http-interop/http-middleware),
 passing it a PSR-7 `ServerRequestInterface` and an http-interop
-`DelegateInterface`. 
+`DelegateInterface`.
 
 As such, ideally your middleware should implement the `MiddlewareInterface` from
 [http-interop/http-middleware](https://github.com/http-interop/http-middleware):

docs/book/migration/to-v2-7.md

@@ -48,7 +48,7 @@ zend-mvc provides two mechanisms for injecting event managers into
 registered in `Zend\Mvc\Service\ServiceManagerConfig`, and the other is the
 `Zend\Mvc\Controller\ControllerManager::injectEventManager()` initializer. In
 both cases, the logic was updated to be forwards compatible with
-zend-eventmanager v3. 
+zend-eventmanager v3.
 
 Previously each would check if the instance's `getEventManager()` method
 returned an event manager instance, and, if so, inject the shared event manager:
@@ -194,7 +194,7 @@ two approaches you can use:
   specific controllers. This way you don't need to inject dependencies that are
   only used in some actions. (We recommend doing this regardless, as it helps
   keep your code more maintainable.)
-- Use [lazy services](http://zendframework.github.io/zend-servicemanager/lazy-services/).
+- Use [lazy services](http://docs.zendframework.com/zend-servicemanager/lazy-services/).
   When you configure these, zend-servicemanager gives you a proxy instance that,
   on first access, loads the full service. This allows you to delay the most
   expensive operations until absolutely needed.

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

@@ -1,4 +1,4 @@
-# Upgrading to 3.0 
+# Upgrading to 3.0
 
 With the release of Zend Framework 2, all components current at that time,
 regardless of history, were tagged as v2 releases; in reality, it was the first
@@ -21,7 +21,7 @@ however, raised another problem: you now have to register components as modules
 in your application.
 
 To solve this new problem, we created a new component,
-[zend-component-installer](http://zendframework.github.io/zend-component-installer/).
+[zend-component-installer](http://docs.zendframework.com/zend-component-installer/).
 Install this in your application now:
 
 ```bash
@@ -82,9 +82,9 @@ service alias.
 
 ## DI-ServiceManager integration
 
-The integration between [zend-servicemanager](https://zendframework.github.io/zend-servicemanager) and
+The integration between [zend-servicemanager](https://docs.zendframework.com/zend-servicemanager) and
 [zend-di](https://github.com/zendframework/zend-di) has been moved to a new
-standalone component, [zend-servicemanager-di](https://zendframework.github.io/zend-servicemanager-di/).
+standalone component, [zend-servicemanager-di](https://docs.zendframework.com/zend-servicemanager-di/).
 In most cases, installing the component will restore the original behavior:
 
 ```bash
@@ -96,10 +96,10 @@ $ composer require zendframework/zend-servicemanager-di
 > The above assumes you're using the new component installer detailed in the
 > [dependency reduction](#dependency-reduction) section, above. If you are not,
 > you will need to inject the zend-servicemanager-di module into your
-> application manually; follow the [instructions in the zend-servicemanager-di documentation](https://zendframework.github.io/zend-servicemanager-di/)
+> application manually; follow the [instructions in the zend-servicemanager-di documentation](https://docs.zendframework.com/zend-servicemanager-di/)
 > to do so.
 
-The new component also contains a [migration document](https://zendframework.github.io/zend-servicemanager-di/migration/v2-to-v3/)
+The new component also contains a [migration document](https://docs.zendframework.com/zend-servicemanager-di/migration/v2-to-v3/)
 detailing potential issues for users migrating to version 3.
 
 ## DispatchListener
@@ -111,14 +111,14 @@ with the v3 release.
 ## Routing
 
 Routing was removed from zend-mvc, and moved to a new component,
-[zend-router](https://zendframework.github.io/zend-router/), which is now a
+[zend-router](https://docs.zendframework.com/zend-router/), which is now a
 dependency of zend-mvc.
 
 The changes that will impact users are:
 
-- [Query route removal](http://zendframework.github.io/zend-router/migration/v2-to-v3/#query-route-removal); 
+- [Query route removal](http://docs.zendframework.com/zend-router/migration/v2-to-v3/#query-route-removal);
   this route had been deprecated since 2.3.0, and removed for the 3.0 release.
-- [Namespace changes](http://zendframework.github.io/zend-router/migration/v2-to-v3/#namespace-change);
+- [Namespace changes](http://docs.zendframework.com/zend-router/migration/v2-to-v3/#namespace-change);
   with the separation to the zend-router component, all routes changed
   namespaces from `Zend\Mvc\Router` to `Zend\Router`.
 
@@ -128,7 +128,7 @@ your code.
 ## Console tooling
 
 Console tooling, including console routes, were split off to a new component,
-[zend-mvc-console](https://zendframework.github.io/zend-mvc-console/). If you
+[zend-mvc-console](https://docs.zendframework.com/zend-mvc-console/). If you
 were using the console tooling, install zend-mvc-console:
 
 ```bash
@@ -140,7 +140,7 @@ ensure the component is registered with your application!)
 
 zend-mvc-console exposes all of the same functionality as was in the v2 series
 of zend-mvc, but most components are in different namespaces. Please read the
-[zend-mvc-console migration guide](http://zendframework.github.io/zend-mvc-console/migration/v2-to-v3/)
+[zend-mvc-console migration guide](http://docs.zendframework.com/zend-mvc-console/migration/v2-to-v3/)
 for full details of what changes you may need to make to your application to
 ensure console tooling continues to work.
 
@@ -159,7 +159,7 @@ provided specifications to zend-modulemanager's `ServiceListener`
 to allow modules to provide filter configuration.
 
 This functionality is now removed from zend-mvc. It is now exposed directly by
-the [zend-filter](https://zendframework.github.io/zend-filter/) component
+the [zend-filter](https://docs.zendframework.com/zend-filter/) component
 itself. To add it, install zend-filter:
 
 ```bash
@@ -201,7 +201,7 @@ provided specifications to zend-modulemanager's `ServiceListener`
 to allow modules to provide hydrator configuration.
 
 This functionality is now removed from zend-mvc. It is now exposed directly by
-the [zend-hydrator](https://zendframework.github.io/zend-hydrator/) component
+the [zend-hydrator](https://docs.zendframework.com/zend-hydrator/) component
 itself. To add it, install zend-hydrator:
 
 ```bash
@@ -218,7 +218,7 @@ provided specifications to zend-modulemanager's `ServiceListener`
 to allow modules to provide validator configuration.
 
 This functionality is now removed from zend-mvc. It is now exposed directly by
-the [zend-inputfilter](https://zendframework.github.io/zend-inputfilter/) component
+the [zend-inputfilter](https://docs.zendframework.com/zend-inputfilter/) component
 itself. To add it, install zend-inputfilter:
 
 ```bash
@@ -240,8 +240,8 @@ Internationalization tooling, including:
 - the `TranslatorAwareTreeRouteStack` implementation
 - factories for the translator and translator loader managers
 
-were removed, and re-assigned to the [zend-i18n](https://zendframework.github.io/zend-i18n/)
-and [zend-mvc-i18n](https://zendframework.github.io/zend-mvc-i18n/) packages.
+were removed, and re-assigned to the [zend-i18n](https://docs.zendframework.com/zend-i18n/)
+and [zend-mvc-i18n](https://docs.zendframework.com/zend-mvc-i18n/) packages.
 In most cases, you can install `zendframework/zend-mvc-i18n` to restore i18n
 functionality to your application:
 
@@ -261,9 +261,9 @@ Second, if you were extending one of the service factories for either the
 factories have changed. In such situations, you have two options:
 
 - Update your extensions to extend the new classes. See the [zend-mvc-i18n
-  migration guide](https://zendframework.github.io/zend-mvc-i18n/migration/v2-to-v3/)
+  migration guide](https://docs.zendframework.com/zend-mvc-i18n/migration/v2-to-v3/)
   to determine what names have changed.
-- Instead of extending, consider using [delegator factories](https://zendframework.github.io/zend-servicemanager/delegators/),
+- Instead of extending, consider using [delegator factories](https://docs.zendframework.com/zend-servicemanager/delegators/),
   as these decorate the service factory, regardless of what factory is used.
 
 ## Log integration
@@ -273,7 +273,7 @@ services by default, and provided specifications to zend-modulemanager's
 `ServiceListener` to allow modules to provide configuration for each.
 
 This functionality is now removed from zend-mvc. It is now exposed directly by
-the [zend-log](https://zendframework.github.io/zend-log/) component
+the [zend-log](https://docs.zendframework.com/zend-log/) component
 itself. To add it, install zend-log:
 
 ```bash
@@ -400,7 +400,7 @@ provided specifications to zend-modulemanager's `ServiceListener`
 to allow modules to provide validator configuration.
 
 This functionality is now removed from zend-mvc. It is now exposed directly by
-the [zend-validator](https://zendframework.github.io/zend-validator/) component
+the [zend-validator](https://docs.zendframework.com/zend-validator/) component
 itself. To add it, install zend-validator:
 
 ```bash

docs/book/plugins.md

@@ -72,11 +72,11 @@ class SomeController extends AbstractActionController
 
 The above would return a standard `Zend\View\Model\ViewModel` instance if no
 criterias are met, and the specified view model types if a specific criteria
-is met. Rules are matched in order, with the first match "winning". 
-Make sure to put your fallback view model *first* as a fallback for unknown 
+is met. Rules are matched in order, with the first match "winning".
+Make sure to put your fallback view model *first* as a fallback for unknown
 content types or `*/*`.
 
-> Browsers are sending `*/*` as last content type of the Accept header so you have to define every 
+> Browsers are sending `*/*` as last content type of the Accept header so you have to define every
 > acceptable view model and their content type.
 
 ## Forward Plugin

docs/book/routing.md

@@ -722,4 +722,4 @@ echo $this->url('packages.zendframework.com/index', [], [], true);
 ## Console Route Types
 
 zend-mvc also allows routing Console based applications; console routes are
-explained in the [zend-console routing documentation](http://zendframework.github.io/zend-console/routes/).
+explained in the [zend-console routing documentation](http://docs.zendframework.com/zend-console/routes/).

docs/book/send-response-event.md

@@ -22,7 +22,7 @@ Class                                                        | Priority | Method
 ------------------------------------------------------------ | -------: | ------------- | -----------
 `Zend\Mvc\SendResponseListener\PhpEnvironmentResponseSender` | -1000    | `__invoke`    | This is used in HTTP contexts (this is the most often used).
 `Zend\Mvc\SendResponseListener\ConsoleResponseSender`        | -2000    | `__invoke`    | This is used in console contexts.
-`Zend\Mvc\SendResponseListener\SimpleStreamResponseSender`   | -3000    | `__invoke`    | 
+`Zend\Mvc\SendResponseListener\SimpleStreamResponseSender`   | -3000    | `__invoke`    |
 
 Because each listener has negative priority, adding your own logic to modify the
 `Response` involves adding a new listener without priority (as priority defaults

docs/book/services.md

@@ -48,7 +48,7 @@ As a quick review, the following service types may be configured:
   service manager as an argument, the resolved service name, and the requested
   service name; it **must** be a class or object implementing
   `Zend\ServiceManager\AbstractFactoryInterface`. See the section on
-  [abstract factories](http://zendframework.github.io/zend-servicemanager/configuring-the-service-manager/#abstract-factories)
+  [abstract factories](http://docs.zendframework.com/zend-servicemanager/configuring-the-service-manager/#abstract-factories)
   for configuration information.
 - **Aliases**, which alias one service name to another. Aliases can also
   reference other aliases.
@@ -107,7 +107,7 @@ services configured out of the box.
 
     - If the controller implements `Zend\EventManager\EventManagerAwareInterface`,
       an instance of the `EventManager` will be injected into it.
-  
+
     - Finally, an initializer will inject it with the `ControllerPluginManager`
       service, as long as the `setPluginManager` method is implemented.
 
@@ -126,7 +126,7 @@ services configured out of the box.
     - If the `adapter` subkey is present, it is used to get the adapter
       instance, otherwise, `Zend\Console\Console::detectBestAdapter()` will be
       called to configure an adapter instance.
-  
+
     - If the `charset` subkey is present, the value is used to set the adapter
       charset.
 
@@ -166,7 +166,7 @@ services configured out of the box.
 
 - `FilterManager`, mapping to `Zend\Mvc\Service\FilterManagerFactory`. This
   instantiates the `Zend\Filter\FilterPluginManager` instance, passing it the
-  service manager instance; this is used to manage filters for [filter chains](http://zendframework.github.io/zend-filter/filter-chains/).
+  service manager instance; this is used to manage filters for [filter chains](http://docs.zendframework.com/zend-filter/filter-chains/).
   It also uses the `DiAbstractServiceFactory` service, effectively allowing
   you to fall back to DI in order to retrieve filters.
 
@@ -380,7 +380,7 @@ return [
 ];
 ```
 
-See the [cache documentation](https://zendframework.github.io/zend-cache/storage/adapter/)
+See the [cache documentation](https://docs.zendframework.com/zend-cache/storage/adapter/)
 for more configuration options.
 
 ### Zend\\Db\\Adapter\\AdapterAbstractServiceFactory
@@ -469,7 +469,7 @@ return [
 ];
 ```
 
-See the [log documentation](https://zendframework.github.io/zend-log/intro/)
+See the [log documentation](https://docs.zendframework.com/zend-log/intro/)
 for more configuration options.
 
 ## Plugin Managers