Rewrote actions

Author: wouterj

bundles/routing_auto/exists_actions.rst

@@ -5,7 +5,7 @@ Path Exists Actions
 -------------------
 
 These are the default actions available to take if the path provided by a
-`path_provider` already exists and so creating a new path would create a
+``path_provider`` already exists and so creating a new path would create a
 conflict.
 
 auto_increment
@@ -18,9 +18,7 @@ it finds a path which *doesn't* exist.
 
 This action should typically be used in the ``content_name`` builder unit to
 resolve conflicts. Using it in the ``content_path`` builder chain would not
-make much sense (I can't imagine any use cases at the moment).
-
-Example:
+make much sense.
 
 .. configuration-block::
 
@@ -43,17 +41,14 @@ use
 ~~~
 
 The ``use`` action will simply take the existing path and use it. For example,
-in our post example the first builder unit must first determine the blogs
-path, ``/my/blog``, if this path exists (and it should) then we will *use* it
-in the stack.
+in a forum the builder unit must first determine the category path, ``/my-category``,
+if this path exists (and it should) then it will be *used* in the stack.
 
 This action should typically be used in one of the content path builder units
-to specify that we should use the existing route, on the other hand, using
+to specify that it should use the existing route. On the other hand, using
 this as the content name builder action should cause the old route to be
 overwritten.
 
-Example:
-
 .. configuration-block::
 
     .. code-block:: yaml

bundles/routing_auto/not_exists_actions.rst

@@ -10,9 +10,7 @@ These are the default actions available to take if the path provided by a
 create
 ~~~~~~
 
-The ``create`` action will create the path. **currently** all routes provided
-by the content path build units will be created as ``Generic`` documents,
-whilst the content name route will be created as an ``AutoRoute`` document.
+The ``create`` action will create the path.
 
 .. configuration-block::
 
@@ -31,6 +29,12 @@ whilst the content name route will be created as an ``AutoRoute`` document.
             'not_exists_action' => 'create',
         );
 
+.. note::
+
+    **Currently** all routes provided by the content path build units will be
+    created as ``Generic`` documents, whilst the content name route will be
+    created as an ``AutoRoute`` document.
+
 throw_exception
 ~~~~~~~~~~~~~~~
 

bundles/routing_auto/providers.rst

@@ -22,9 +22,6 @@ Options
 
 * ``path`` - **required** The path to provide.
 
-Example
-.......
-
 .. configuration-block::
 
     .. code-block:: yaml
@@ -67,9 +64,6 @@ Options
 
  - ``method``: **required** Method used to return the document whose route path you wish to use.
 
-Example
-.......
-
 .. configuration-block::
 
     .. code-block:: yaml
@@ -109,9 +103,6 @@ Options
 * ``method``: **required** Method used to return the route name/path/path elements.
 * ``slugify``: If the return value should be slugified, default is ``true``.
 
-Example
-.......
-
 .. configuration-block::
 
     .. code-block:: yaml
@@ -167,9 +158,6 @@ content_datetime
 The ``content_datettime`` provider will provide a path from a ``DateTime``
 object provided by a designated method on the content document.
 
-Example
-.......
-
 .. configuration-block::
 
     .. code-block:: yaml