A quick review of the RoutingBundle docs

Author: wouterj

bundles/_partials/sonata_admin_enabled.rst.inc

@@ -1,14 +1,15 @@
 ``enabled``
 ***********
 
-... true false only
+**type**: ``bool`` **default**: ``false``
 
-**type**: ``bool`` **valid values**: ``true|false`` **default**: ``false``
+If ``true``, the admin classes and extensions of this package are loaded and
+available for Sonata Admin.
 
-If ``true``, the admin classes for the routing are loaded and available for
-Sonata.
+.. tip::
 
-.. note::
+    If you do not see this admin on the Sonata dashboard, you need to configure
+    the dashboard to show the admin service in question. Read more about this
+    in `the Sonata Admin documentation`_.
 
-    To see an admin on the sonata dashboard, you still need to configure the
-    dashboard to show the admin service in question.
+.. _the Sonata Admin documentation: https://sonata-project.org/bundles/admin/3-x/doc/reference/dashboard.html

bundles/routing/configuration.rst

@@ -306,7 +306,7 @@ setting is set as controller.
 
 **type**: ``scalar``, **default**: ``0``
 
-If this value is set to a number bigger than 0, the ``getRouteCollection``
+If this value is set to a number bigger than 0, the ``getRouteCollection()``
 method returns a collection of routes read from the database. The limit serves
 to prevent huge route lists if you have a large database. Setting the limit to
 ``false`` disables the limit entirely and attempts to return all routes.

bundles/sonata_phpcr_admin_integration/routing.rst

@@ -1,20 +1,19 @@
 RoutingBundle
 =============
 
-Both content routes and redirect routes can be administrated. The content admin
-shows a tree of the content documents to select which content to use for this
-route. Set the root of the content with the ``content_basepath`` setting.
+Both content routes and redirect routes can be administrated. When creating
+content routes, a tree of content documents is shown. The administrator can
+select a content document to bind to the route. This tree is configured with
+the ``content_basepath`` setting.
 
-The root path to add Routes defaults to the first entry in ``route_basepaths``,
-but you can overwrite this with the ``basepath`` if you need a different
-base path.
+The root path to add routes defaults to the first entry in ``route_basepaths``
+configuration of the RoutingBundle. You can overwrite this with the
+``basepath`` option if you need a different base path.
 
-Routing can also be handled on a content that has a back link to its routes.
-The admin integration provides an admin extension to add route editing to any
-route aware content.
-
-Another extension provides a frontend link on all admin pages that are about
-content that has a URL.
+Routes can also be handled in the content admin page. The admin integration
+provides an admin extension that allows adding routes to any route aware
+objects. Another extension provides a frontend link on all admin pages that
+objects that refer to routes.
 
 Configuration
 -------------
@@ -28,8 +27,8 @@ Configuration
             bundles:
                 routing:
                     enabled: false
-                    basepath: null
-                    content_basepath: null
+                    basepath: ~
+                    content_basepath: ~
 
     .. code-block:: xml
 
@@ -196,7 +195,9 @@ See the `Sonata Admin extension documentation`_ for more information.
 Styling the Frontend Link
 *************************
 
-The frontend link button can be customized using the following CSS selectors:
+The frontend link button can be customized using the
+``.sonata-admin-frontend-link`` selector. For instance, to show a link icon and
+make the label bold, use the following CSS:
 
 .. code-block:: css