diff --git a/docs/cookbook/recipe_custom_action.rst b/docs/cookbook/recipe_custom_action.rst
index 1cfd1239a7..1b31c0cc0e 100644
--- a/docs/cookbook/recipe_custom_action.rst
+++ b/docs/cookbook/recipe_custom_action.rst
@@ -2,9 +2,14 @@ Creating a Custom Admin Action
 ==============================
 
 This is a full working example of creating a custom list action for SonataAdmin.
-The example is based on an existing ``CarAdmin`` class in an ``AppBundle``.
+The example is based on an existing ``CarAdmin`` class in a ``App`` namespace.
 It is assumed you already have an admin service up and running.
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 The recipe
 ----------
 
@@ -25,9 +30,9 @@ First you need to create your own Controller extending the one from SonataAdmin
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Controller/CRUDController.php
+    // src/Controller/CRUDController.php
 
-    namespace AppBundle\Controller;
+    namespace App\Controller;
 
     use Sonata\AdminBundle\Controller\CRUDController as Controller;
 
@@ -46,30 +51,30 @@ Either by using XML:
 
 .. code-block:: xml
 
-        <!-- src/AppBundle/Resources/config/admin.xml -->
+        <!-- src/Resources/config/admin.xml -->
 
-        <service id="app.admin.car" class="AppBundle\Admin\CarAdmin">
+        <service id="app.admin.car" class="App\Admin\CarAdmin">
             <tag name="sonata.admin" manager_type="orm" group="Demo" label="Car" />
             <argument />
-            <argument>AppBundle\Entity\Car</argument>
-            <argument>AppBundle:CRUD</argument>
+            <argument>App\Entity\Car</argument>
+            <argument>App\Controller\CRUDController</argument>
         </service>
 
 or by adding it to your ``admin.yml``:
 
 .. code-block:: yaml
 
-    # src/AppBundle/Resources/config/admin.yml
+    # src/Resources/config/admin.yml
 
     services:
         app.admin.car:
-            class: AppBundle\Admin\CarAdmin
+            class: App\Admin\CarAdmin
             tags:
                 - { name: sonata.admin, manager_type: orm, group: Demo, label: Car }
             arguments:
                 - null
-                - AppBundle\Entity\Car
-                - AppBundle:CRUD
+                - App\Entity\Car
+                - App\Controller\CRUDController
             public: true
 
 For more information about service configuration please refer to Step 3 of :doc:`../getting_started/creating_an_admin`
@@ -83,9 +88,9 @@ to implement a ``clone`` action.
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Controller/CRUDController.php
+    // src/Controller/CRUDController.php
 
-    namespace AppBundle\Controller;
+    namespace App\Controller;
 
     use Symfony\Component\HttpKernel\Exception\NotFoundHttpException;
     use Sonata\AdminBundle\Controller\CRUDController as Controller;
@@ -151,7 +156,7 @@ Admin Controller.
 
 .. code-block:: html+jinja
 
-    {# src/AppBundle/Resources/views/CRUD/list__action_clone.html.twig #}
+    {# templates/CRUD/list__action_clone.html.twig #}
 
     <a class="btn btn-sm" href="{{ admin.generateObjectUrl('clone', object) }}">clone</a>
 
@@ -207,9 +212,9 @@ The full ``CarAdmin.php`` example looks like this:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/CarAdmin.php
+    // src/Admin/CarAdmin.php
 
-    namespace AppBundle\Admin;
+    namespace App\Admin;
 
     use Sonata\AdminBundle\Admin\AbstractAdmin;
     use Sonata\AdminBundle\Datagrid\DatagridMapper;
@@ -264,12 +269,12 @@ The full ``CarAdmin.php`` example looks like this:
 
     If you want to render a custom controller action in a template by using the
     render function in twig you need to add ``_sonata_admin`` as an attribute. For
-    example; ``{{ render(controller('AppBundle:XxxxCRUD:comment', {'_sonata_admin':
+    example; ``{{ render(controller('App:XxxxCRUD:comment', {'_sonata_admin':
     'sonata.admin.xxxx' })) }}``. This has to be done because the moment the
     rendering should happen the routing, which usually sets the value of this
     parameter, is not involved at all, and then you will get an error "There is no
     _sonata_admin defined for the controller
-    AppBundle\Controller\XxxxCRUDController and the current route ' '."
+    App\Controller\XxxxCRUDController and the current route ' '."
 
 Custom Action without Entity
 ----------------------------
diff --git a/docs/cookbook/recipe_customizing_a_mosaic_list.rst b/docs/cookbook/recipe_customizing_a_mosaic_list.rst
index 8a07056f8d..8cae7befc1 100644
--- a/docs/cookbook/recipe_customizing_a_mosaic_list.rst
+++ b/docs/cookbook/recipe_customizing_a_mosaic_list.rst
@@ -79,9 +79,8 @@ Block types:
  - ``sonata_mosaic_description``: this block will be always on screen and should represent the entity's name.
 
 
-The ``ObjectMetadata`` object is returned by the related admin class, for instance the MediaBundle defines the method as:
-
-.. code-block:: jinja
+The ``ObjectMetadata`` object is returned by the related admin class,
+for instance the MediaBundle defines the method as::
 
     <?php
 
diff --git a/docs/cookbook/recipe_data_mapper.rst b/docs/cookbook/recipe_data_mapper.rst
index 8491bcc476..68c692b259 100644
--- a/docs/cookbook/recipe_data_mapper.rst
+++ b/docs/cookbook/recipe_data_mapper.rst
@@ -3,6 +3,11 @@ Using DataMapper to work with domain entities without per field setters
 
 This is an example of using DataMapper with entities that avoid setters/getters for each field.
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 Pre-requisites
 --------------
 
@@ -25,9 +30,9 @@ Example Entity
 
     <?php
 
-    // src/AppBundle/Entity/Example.php
+    // src/Entity/Example.php
 
-    namespace AppBundle\Entity;
+    namespace App\Entity;
 
     class Example
     {
@@ -58,12 +63,12 @@ To be able to set entity data without the possibility to use setters a ``DataMap
 
     <?php
 
-    // src/AppBundle/Form/DataMapper/ExampleDataMapper.php
+    // src/Form/DataMapper/ExampleDataMapper.php
 
-    namespace AppBundle\Form\DataMapper;
+    namespace App\Form\DataMapper;
 
     use Symfony\Component\Form\DataMapperInterface;
-    use AppBundle\Entity\Example;
+    use App\Entity\Example;
 
     class ExampleDataMapper implements DataMapperInterface
     {
@@ -114,13 +119,13 @@ Now we need to configure the form to use our ``ExampleDataMapper``.
 
     <?php
 
-    // src/AppBundle/Admin/ExampleAdmin.php
+    // src/Admin/ExampleAdmin.php
 
-    namespace AppBundle\Admin;
+    namespace App\Admin;
 
     use Sonata\AdminBundle\Admin\AbstractAdmin;
     use Sonata\AdminBundle\Form\FormMapper;
-    use AppBundle\Form\DataMapper\ExampleDataMapper;
+    use App\Form\DataMapper\ExampleDataMapper;
 
     class ExampleAdmin extends AbstractAdmin
     {
diff --git a/docs/cookbook/recipe_delete_field_group.rst b/docs/cookbook/recipe_delete_field_group.rst
index f9038c23fd..070bcac02c 100644
--- a/docs/cookbook/recipe_delete_field_group.rst
+++ b/docs/cookbook/recipe_delete_field_group.rst
@@ -1,13 +1,16 @@
 Deleting a Group of Fields from an Admin
 ========================================
 
-In some cases, when you extend existing Admins, you might want to delete fields from the admin, or make them not show.
-You could delete every field by hand, using the ``FormMapper``s ``remove`` method.
+In some cases, when you extend existing Admins, you might want to delete
+fields from the admin, or make them not show. You could delete every
+field by hand, using the ``FormMapper``s ``remove`` method.
 
     .. code-block:: php
 
-        class UserAdmin extends \Sonata\UserBundle\Admin\Model\UserAdmin {
+        use Sonata\UserBundle\Admin\Model\UserAdmin as SonataUserAdmin;
 
+        class UserAdmin extends SonataUserAdmin
+        {
             protected function configureFormFields(FormMapper $formMapper)
             {
                 parent::configureFormFields($formMapper);
@@ -22,24 +25,35 @@ You could delete every field by hand, using the ``FormMapper``s ``remove`` metho
         }
 
 
-This works, as long as the extended Admin does not use Groups to organize it's field. In the above example, we try to remove all fields from the User Admin, that comes with the SonataUserBundle.
-However, since the fields we deleted, are all part of the 'Social' Group of the form, the fields will be deleted and the empty group will stay.
-For this case, the FormMapper comes with a method, which allows you to get rid of a whole form group: ``removeGroup``
+This works, as long as the extended Admin does not use Groups to organize its field.
+In the above example, we try to remove all fields from the User Admin, that comes
+with the SonataUserBundle. However, since the fields we deleted, are all part
+of the 'Social' Group of the form, the fields will be deleted and the empty group will stay.
+For this case, the FormMapper comes with a method, which allows you to get rid
+of a whole form group: ``removeGroup``.
 
     .. code-block:: php
 
-        class UserAdmin extends \Sonata\UserBundle\Admin\Model\UserAdmin {
+        use Sonata\UserBundle\Admin\Model\UserAdmin as SonataUserAdmin;
+
+        class UserAdmin extends SonataUserAdmin
+        {
 
             protected function configureFormFields(FormMapper $formMapper)
             {
                 parent::configureFormFields($formMapper);
 
                 $formMapper->removeGroup('Social', 'User');
-
             }
         }
 
-This will remove the whole 'Social' group from the form, which happens to contain all the fields, we deleted manually in the first example. The second argument is the name of the tab, the group belongs to.
-This is optional. However, when not provided, it will be assumed that you mean the 'default' tab. If the group is on another tab, it won't be removed, when this is not provided.
-There is a third optional argument for the method, which let's you choose, whether or not, tabs are also removed, if you happen to remove all groups of a tab. This behaviour is disabled by default, but
-can be enabled, by setting the third argument of ``removeGroup`` to ``true``
+This will remove the whole 'Social' group from the form, which happens
+to contain all the fields, we deleted manually in the first example.
+The second argument is the name of the tab, the group belongs to.
+This is optional. However, when not provided, it will be assumed that
+you mean the 'default' tab. If the group is on another tab, it won't be
+removed, when this is not provided. There is a third optional argument
+for the method, which let's you choose, whether or not, tabs are also
+removed, if you happen to remove all groups of a tab. This behaviour
+is disabled by default, but can be enabled, by setting the third
+argument of ``removeGroup`` to ``true``.
diff --git a/docs/cookbook/recipe_dynamic_form_modification.rst b/docs/cookbook/recipe_dynamic_form_modification.rst
index a4fa8b6a59..094a59acf0 100644
--- a/docs/cookbook/recipe_dynamic_form_modification.rst
+++ b/docs/cookbook/recipe_dynamic_form_modification.rst
@@ -1,6 +1,11 @@
 Modifying form fields dynamically depending on edited object
 ============================================================
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 It is a quite common situation when you need to modify your form's fields because
 of edited object's properties or structure. Let us assume you only want to display
 an admin form field for new objects and you do not want it to be shown for those
@@ -11,17 +16,18 @@ This is a way for you to accomplish this.
 In your ``Admin`` class' ``configureFormFields`` method you are able to get the
 current object by calling ``$this->getSubject()``. The value returned will be your
 linked model. And another method ``isCurrentRoute`` for check the current request's route.
-Then, you should be able to dynamically add needed fields to the form:
-
-.. code-block:: php
+Then, you should be able to dynamically add needed fields to the form::
 
     <?php
-    // src/AppBundle/Admin/PostAdmin
+    // src/Admin/PostAdmin
 
-    namespace AppBundle\Admin;
+    namespace App\Admin;
 
     use Sonata\AdminBundle\Admin\AbstractAdmin;
     use Sonata\AdminBundle\Form\FormMapper;
+    use Symfony\Component\Form\Extension\Core\Type\TextType;
+    use Symfony\Component\Form\Extension\Core\Type\TextareaType;
+    use Symfony\Component\Form\Extension\Core\Type\FileType;
 
     class PostAdmin extends AbstractAdmin
     {
@@ -31,19 +37,19 @@ Then, you should be able to dynamically add needed fields to the form:
         {
             // Description field will always be added to the form:
             $formMapper
-                ->add('description', 'textarea')
+                ->add('description', TextareaType::class)
             ;
 
             $subject = $this->getSubject();
 
             if ($subject->isNew()) {
                 // The thumbnail field will only be added when the edited item is created
-                $formMapper->add('thumbnail', 'file');
+                $formMapper->add('thumbnail', FileType::class);
             }
 
             // Name field will be added only when create an item
             if ($this->isCurrentRoute('create')) {
-                $formMapper->add('name', 'text');
+                $formMapper->add('name', TextType::class);
             }
         }
     }
diff --git a/docs/cookbook/recipe_file_uploads.rst b/docs/cookbook/recipe_file_uploads.rst
index 235158a698..d89325f851 100644
--- a/docs/cookbook/recipe_file_uploads.rst
+++ b/docs/cookbook/recipe_file_uploads.rst
@@ -4,6 +4,11 @@ Uploading and saving documents (including images) using DoctrineORM and SonataAd
 This is a full working example of a file upload management method using
 SonataAdmin with the DoctrineORM persistence layer.
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 Pre-requisites
 --------------
 
@@ -42,11 +47,11 @@ upload timestamp.
 
     .. code-block:: yaml
 
-        # src/AppBundle/Resources/config/Doctrine/Image.orm.yml
+        # src/Resources/config/Doctrine/Image.orm.yml
 
         AppBundleBundle\Entity\Image:
             type: entity
-            repositoryClass: AppBundle\Entity\Repositories\ImageRepository
+            repositoryClass: App\Entity\Repositories\ImageRepository
             table: images
             id:
                 id:
@@ -67,12 +72,10 @@ upload timestamp.
                 prePersist:   [ lifecycleFileUpload ]
                 preUpdate:    [ lifecycleFileUpload ]
 
-We then have the following methods in our ``Image`` class to manage file uploads:
-
-.. code-block:: php
+We then have the following methods in our ``Image`` class to manage file uploads::
 
     <?php
-    // src/AppBundle/Bundle/Entity/Image.php
+    // src/Entity/Image.php
 
     const SERVER_PATH_TO_IMAGE_FOLDER = '/server/path/to/images';
 
@@ -163,19 +166,19 @@ We need to do two things in Sonata to enable file uploads:
 1. Add a file upload widget
 2. Ensure that the Image class' lifecycle events fire when we upload a file
 
-Both of these are straightforward when you know what to do:
-
-.. code-block:: php
+Both of these are straightforward when you know what to do::
 
     <?php
-    // src/AppBundle/Admin/ImageAdmin.php
+    // src/Admin/ImageAdmin.php
+
+    use Symfony\Component\Form\Extension\Core\Type\FileType;
 
     class ImageAdmin extends AbstractAdmin
     {
         protected function configureFormFields(FormMapper $formMapper)
         {
             $formMapper
-                ->add('file', 'file', [
+                ->add('file', FileType::class, [
                     'required' => false
                 ])
 
@@ -225,12 +228,10 @@ Admin's lifecycle events to trigger the file management when needed.
 
 In this example we have a Page class which has three one-to-one Image relationships
 defined, linkedImage1 to linkedImage3. The PostAdmin class' form field configuration
-looks like this:
-
-.. code-block:: php
+looks like this::
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     use Sonata\AdminBundle\Form\Type\AdminType;
 
@@ -259,12 +260,10 @@ looks like this:
 This is easy enough - we have embedded three fields, which will then use our ``ImageAdmin``
 class to determine which fields to show.
 
-In our PostAdmin we then have the following code to manage the relationships' lifecycles:
-
-.. code-block:: php
+In our PostAdmin we then have the following code to manage the relationships' lifecycles::
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     class PostAdmin extends AbstractAdmin
     {
@@ -287,7 +286,7 @@ In our PostAdmin we then have the following code to manage the relationships' li
                 // detect embedded Admins that manage Images
                 if ($fieldDescription->getType() === 'sonata_type_admin' &&
                     ($associationMapping = $fieldDescription->getAssociationMapping()) &&
-                    $associationMapping['targetEntity'] === 'AppBundle\Entity\Image'
+                    $associationMapping['targetEntity'] === 'App\Entity\Image'
                 ) {
                     $getter = 'get'.$fieldName;
                     $setter = 'set'.$fieldName;
diff --git a/docs/cookbook/recipe_improve_performance_large_datasets.rst b/docs/cookbook/recipe_improve_performance_large_datasets.rst
index 0ce827b8b5..4b03a532f0 100644
--- a/docs/cookbook/recipe_improve_performance_large_datasets.rst
+++ b/docs/cookbook/recipe_improve_performance_large_datasets.rst
@@ -19,27 +19,27 @@ To use `SimplePager` in your admin just define ``pager_type`` inside the service
 
     .. code-block:: xml
 
-        <!-- src/AppBundle/Resources/config/admin.xml -->
+        <!-- src/Resources/config/admin.xml -->
 
-        <service id="app.admin.post" class="AppBundle\Admin\PostAdmin">
+        <service id="app.admin.post" class="App\Admin\PostAdmin">
             <tag name="sonata.admin" manager_type="orm" group="Content" label="Post" pager_type="simple" />
             <argument />
-            <argument>AppBundle\Entity\Post</argument>
+            <argument>App\Entity\Post</argument>
             <argument />
         </service>
 
     .. code-block:: yaml
 
-        # src/AppBundle/Resources/config/admin.yml
+        # config/services.yaml
 
         services:
             app.admin.post:
-                class: AppBundle\Admin\PostAdmin
+                class: App\Admin\PostAdmin
                 tags:
                     - { name: sonata.admin, manager_type: orm, group: "Content", label: "Post", pager_type: "simple" }
                 arguments:
                     - ~
-                    - AppBundle\Entity\Post
+                    - App\Entity\Post
                     - ~
                 public: true
 
diff --git a/docs/cookbook/recipe_knp_menu.rst b/docs/cookbook/recipe_knp_menu.rst
index f6fc5abcb2..92ee255df1 100644
--- a/docs/cookbook/recipe_knp_menu.rst
+++ b/docs/cookbook/recipe_knp_menu.rst
@@ -2,16 +2,20 @@ KnpMenu
 =======
 
 The admin comes with `KnpMenu`_ integration.
-It integrates a menu with the KnpMenu library. This menu can be a SonataAdmin service, a menu created with a Knp menu provider or a route of a custom controller.
+It integrates a menu with the KnpMenu library. This menu can be a SonataAdmin
+service, a menu created with a Knp menu provider or a route of a custom controller.
+
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
 
 Add a custom controller entry in the menu
 -----------------------------------------
 
 To add a custom controller entry in the admin menu:
 
-Create your controller:
-
-.. code-block:: php
+Create your controller::
 
     class BlogController
     {
@@ -39,7 +43,7 @@ Add the controller route as an item of the menu:
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             dashboard:
@@ -62,7 +66,7 @@ group roles will be checked.
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             dashboard:
@@ -80,13 +84,14 @@ group roles will be checked.
                               label:        Article
                         roles: [ ROLE_ADMIN, ROLE_SONATA_ADMIN]
 
-You can also override the template of knp_menu used by sonata. The default one is `@SonataAdmin/Menu/sonata_menu.html.twig`:
+You can also override the template of knp_menu used by sonata. The default
+one is `@SonataAdmin/Menu/sonata_menu.html.twig`:
 
 .. configuration-block::
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             templates:
@@ -97,7 +102,11 @@ And voilà, now you have a menu group which contains a link to a sonata admin vi
 Using a menu provider
 ---------------------
 
-As seen above, the main way to declare your menu is by declaring items in your sonata admin config file. In some case you may have to create a more complex menu depending on your business logic. This is possible by using a menu provider to populate a whole menu group. This is done with the ``provider`` config value.
+As seen above, the main way to declare your menu is by declaring items
+in your sonata admin config file. In some cases you may have to create a
+more complex menu depending on your business logic. This is possible by
+using a menu provider to populate a whole menu group. This is done with
+the ``provider`` config value.
 
 The following configuration uses a menu provider to populate the menu group ``my_group``:
 
@@ -105,7 +114,7 @@ The following configuration uses a menu provider to populate the menu group ``my
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             dashboard:
@@ -114,9 +123,12 @@ The following configuration uses a menu provider to populate the menu group ``my
                         provider:        'MyBundle:MyMenuProvider:getMyMenu'
                         icon:            '<i class="fa fa-edit"></i>'
 
-With KnpMenuBundle you can create a custom menu by using a builder class or by declaring it as a service. Please see the `Knp documentation`_ for further information.
+With KnpMenuBundle you can create a custom menu by using a builder class
+or by declaring it as a service. Please see the `Knp documentation`_ for
+further information.
 
-In sonata, whatever the implementation you choose, you only have to provide the menu alias to the provider config key:
+In sonata, whatever the implementation you choose, you only have to provide
+the menu alias to the provider config key:
 
 * If you are using a builder class, your menu alias should be something like ``MyBundle:MyMenuProvider:getMyMenu``.
 * If you are using a service, your menu alias is the alias set in the ``knp_menu.menu`` tag. In the following example this is ``my_menu_alias``:
@@ -129,19 +141,19 @@ In sonata, whatever the implementation you choose, you only have to provide the
             <tag name="knp_menu.menu" alias="my_menu_alias" />
         </service>
 
-Please note that when using the provider option, you can't set the menu label via the configuration. It is done in your custom menu.
+Please note that when using the provider option, you can't set the menu
+label via the configuration. It is done in your custom menu.
 
 Extending the menu
 ------------------
 
-You can modify the menu via events easily. You can register as many listeners as you want for the event with name ``sonata.admin.event.configure.menu.sidebar``:
-
-.. code-block:: php
+You can modify the menu via events easily. You can register as many
+listeners as you want for the event with name ``sonata.admin.event.configure.menu.sidebar``::
 
     <?php
-    // src/AppBundle/EventListener/MenuBuilderListener.php
+    // src/EventListener/MenuBuilderListener.php
 
-    namespace AppBundle\EventListener;
+    namespace App\EventListener;
 
     use Sonata\AdminBundle\Event\ConfigureMenuEvent;
 
@@ -164,11 +176,11 @@ You can modify the menu via events easily. You can register as many listeners as
 
     .. code-block:: yaml
 
-        # src/AppBundle/Resources/config/services.yml
+        # config/services.yaml
 
         services:
             app.menu_listener:
-                class: AppBundle\EventListener\MenuBuilderListener
+                class: App\EventListener\MenuBuilderListener
                 tags:
                     - { name: kernel.event_listener, event: sonata.admin.event.configure.menu.sidebar, method: addMenuItems }
 
@@ -191,7 +203,7 @@ your admin services or simply remove menu items from the ``sonata_admin`` dashbo
 
 .. code-block:: yaml
 
-    # app/config/config.yml
+    # config/packages/sonata_admin.yaml
 
     sonata_admin:
         dashboard:
@@ -214,7 +226,7 @@ open and ignore open/close effects:
 
 .. code-block:: yaml
 
-    # app/config/config.yml
+    # config/packages/sonata_admin.yaml
 
     sonata_admin:
         dashboard:
@@ -249,7 +261,7 @@ or in sonata_admin dashboard group configuration:
 
 .. code-block:: yaml
 
-    # app/config/config.yml
+    # config/packages/sonata_admin.yaml
 
     sonata_admin:
         dashboard:
@@ -272,7 +284,7 @@ Your can't use this option for two or more items in the same time, for example:
 
 .. code-block:: yaml
 
-    # app/config/config.yml
+    # config/packages/sonata_admin.yaml
 
     sonata_admin:
         dashboard:
diff --git a/docs/cookbook/recipe_lock_protection.rst b/docs/cookbook/recipe_lock_protection.rst
index 25deaedb44..f147fe3ed9 100644
--- a/docs/cookbook/recipe_lock_protection.rst
+++ b/docs/cookbook/recipe_lock_protection.rst
@@ -3,6 +3,11 @@ Lock Protection
 
 Lock protection will prevent data corruption when multiple users edit an object at the same time.
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 Example
 -------
 
@@ -18,27 +23,26 @@ Enable Lock Protection
 ----------------------
 
 By default, lock protection is disabled.
-You can enable it in your ``sonata_admin`` configuration :
+You can enable it in your ``sonata_admin`` configuration:
 
 .. configuration-block::
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             options:
                 lock_protection: true
                 
-You must also configure each entity that you want to support by adding a field called ``$version`` on which the Doctrine ``Version`` feature is activated.
-
-Using Annotations:
+You must also configure each entity that you want to support by adding a
+field called ``$version`` on which the Doctrine ``Version`` feature is activated.
 
-.. code-block:: php
+Using Annotations::
 
     <?php
-    // src/AppBundle/Entity/Car.php
-    namespace AppBundle\Entity\Car;
+    // src/Entity/Car.php
+    namespace App\Entity\Car;
     
     use Doctrine\ORM\Mapping as ORM;
 
@@ -60,9 +64,9 @@ Using XML:
 .. code-block:: xml
 
     <?xml version="1.0" encoding="utf-8"?>
-    <!-- src/AppBundle/Resources/orm/Car.orm.xml -->
+    <!-- src/Resources/orm/Car.orm.xml -->
     <doctrine-mapping>
-        <entity name="AppBundle\Entity\Car">
+        <entity name="App\Entity\Car">
             <!-- ... -->
     
             <field name="version" type="integer" version="true" />
diff --git a/docs/cookbook/recipe_overwrite_admin_configuration.rst b/docs/cookbook/recipe_overwrite_admin_configuration.rst
index 4ed8813046..5ffa1d7f70 100644
--- a/docs/cookbook/recipe_overwrite_admin_configuration.rst
+++ b/docs/cookbook/recipe_overwrite_admin_configuration.rst
@@ -1,9 +1,12 @@
 Overwrite Admin Configuration
 =============================
 
-Sometime you might want to overwrite some Admin settings from vendors. This recipe will explain how to achieve this operation. However, keep in mind this operation is quite dangerous and might break code.
+Sometimes you might want to overwrite some Admin settings from vendors.
+This recipe will explain how to achieve this operation. However, keep
+in mind this operation is quite dangerous and might break code.
 
-From the configuration file, you can add a new section named ``admin_services`` with the following templates:
+From the configuration file, you can add a new section named ``admin_services``
+with the following templates:
 
 .. code-block:: yaml
 
diff --git a/docs/cookbook/recipe_select2.rst b/docs/cookbook/recipe_select2.rst
index 27e465667d..47dda865a5 100644
--- a/docs/cookbook/recipe_select2.rst
+++ b/docs/cookbook/recipe_select2.rst
@@ -10,13 +10,13 @@ The select2 is enabled on all ``select`` form elements by default.
 Disable select2
 ---------------
 
-If you don't want to use select2 in your admin, you can disable it in ``config.yml``.
+If you don't want to use select2 in your admin, you can disable it in configuration.
 
 .. configuration-block::
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             options:
diff --git a/docs/cookbook/recipe_sortable_listing.rst b/docs/cookbook/recipe_sortable_listing.rst
index dbc051b1eb..02d67743ca 100644
--- a/docs/cookbook/recipe_sortable_listing.rst
+++ b/docs/cookbook/recipe_sortable_listing.rst
@@ -3,6 +3,11 @@ Sortable behavior in admin listing
 
 This is a full working example of how to implement a sortable feature in your Sonata admin listing
 
+.. note::
+   This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 Background
 ----------
 
@@ -84,14 +89,12 @@ and use the default twig template provided in the ``pixSortableBehaviorBundle``
         ]);
 
 
-In order to add new routes for these actions we are also adding the following method
-
-.. code-block:: php
+In order to add new routes for these actions we are also adding the following method::
 
     <?php
-    // src/AppBundle/Admin/ClientAdmin.php
+    // src/Admin/ClientAdmin.php
 
-    namespace AppBundle/Admin;
+    namespace App/Admin;
 
     use Sonata\AdminBundle\Route\RouteCollection;
     // ...
@@ -108,12 +111,12 @@ Now you can update your ``services.yml`` to use the handler provider by the ``pi
 
     services:
         app.admin.client:
-            class: AppBundle\Admin\ClientAdmin
+            class: App\Admin\ClientAdmin
             tags:
               - { name: sonata.admin, manager_type: orm, label: "Clients" }
             arguments:
               - ~
-              - AppBundle\Entity\Client
+              - App\Entity\Client
               - 'PixSortableBehaviorBundle:SortableAdmin' # define the new controller via the third argument
             public: true
 
@@ -122,9 +125,9 @@ Now we need to define the sort by field to be ``$position``:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/ClientAdmin.php
+    // src/Admin/ClientAdmin.php
 
-    namespace AppBundle\Admin;
+    namespace App\Admin;
 
     use Sonata\AdminBundle\AbstractAdmin;
     use Sonata\AdminBundle\Datagrid\ListMapper;
diff --git a/docs/cookbook/recipe_sortable_sonata_type_model.rst b/docs/cookbook/recipe_sortable_sonata_type_model.rst
index 4ac924f2bd..addc6f8f13 100644
--- a/docs/cookbook/recipe_sortable_sonata_type_model.rst
+++ b/docs/cookbook/recipe_sortable_sonata_type_model.rst
@@ -1,13 +1,16 @@
 Sortable Sonata Type Model in Admin
 ===================================
 
-This is a full working example on how to implement a sortable feature in your Sonata admin form between two entities.
+This is a full working example on how to implement a sortable
+feature in your Sonata admin form between two entities.
 
 Background
 ----------
 
-The sortable function is already available inside Sonata for the ``ChoiceType``. But the ``ModelType`` (or sonata_type_model) extends from choice, so this function is already available in our form type.
-We just need some configuration to make it work.
+The sortable function is already available inside Sonata for the ``ChoiceType``.
+But the ``ModelType`` (or sonata_type_model) extends from choice, so this
+function is already available in our form type. We just need some configuration
+to make it work.
 
 The goal here is to fully configure a working example to handle the following need :
 User got some expectations, but some are more relevant than the others.
@@ -29,8 +32,9 @@ The recipe
 Part 1 : Update the data model configuration
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The first thing to do is to update the Doctrine ORM configuration and create the join entity between ``User`` and ``Expectation``.
-We are going to call this join entity ``UserHasExpectations``.
+The first thing to do is to update the Doctrine ORM configuration and
+create the join entity between ``User`` and ``Expectation``. We are
+going to call this join entity ``UserHasExpectations``.
 
 .. note::
 
@@ -91,9 +95,7 @@ We now need to create the join entity configuration, create the following file i
 Part 2 : Update the data model entities
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Update the ``UserBundle\Entity\User.php`` entity with the following :
-
-.. code-block:: php
+Update the ``UserBundle\Entity\User.php`` entity with the following::
 
     // ...
 
@@ -154,9 +156,7 @@ Update the ``UserBundle\Entity\User.php`` entity with the following :
 
     // ...
 
-Update the ``UserBundle\Entity\Expectation.php`` entity with the following :
-
-.. code-block:: php
+Update the ``UserBundle\Entity\Expectation.php`` entity with the following::
 
     // ...
 
@@ -191,9 +191,7 @@ Update the ``UserBundle\Entity\Expectation.php`` entity with the following :
 
     // ...
 
-Create the ``UserBundle\Entity\UserHasExpectations.php`` entity with the following :
-
-.. code-block:: php
+Create the ``UserBundle\Entity\UserHasExpectations.php`` entity with the following::
 
     <?php
     namespace UserBundle\Entity;
@@ -383,7 +381,8 @@ There is two important things that we need to show here :
 Part 4 : Data Transformer
 ^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The last (but not least) step is create the ``UserBundle\Form\DataTransformer\ExpectationDataTransformer.php`` to handle the conversion of ``Expectation`` to ``UserHasExpectations``.
+The last (but not least) step is create the ``UserBundle\Form\DataTransformer\ExpectationDataTransformer.php``
+to handle the conversion of ``Expectation`` to ``UserHasExpectations``.
 
 .. code-block:: php
 
diff --git a/docs/getting_started/creating_an_admin.rst b/docs/getting_started/creating_an_admin.rst
index d6ea7c9820..252e4d4860 100644
--- a/docs/getting_started/creating_an_admin.rst
+++ b/docs/getting_started/creating_an_admin.rst
@@ -19,8 +19,8 @@ using these commands:
 
 .. code-block:: bash
 
-    $ php bin/console doctrine:generate:entity --entity="App:Category" --fields="name:string(255)" --no-interaction
-    $ php bin/console doctrine:generate:entity --entity="App:BlogPost" --fields="title:string(255) body:text draft:boolean" --no-interaction
+    $ bin/console doctrine:generate:entity --entity="App:Category" --fields="name:string(255)" --no-interaction
+    $ bin/console doctrine:generate:entity --entity="App:BlogPost" --fields="title:string(255) body:text draft:boolean" --no-interaction
 
 After this, you'll need to tweak the entities a bit:
 
@@ -106,7 +106,7 @@ After this, create the schema for these entities:
 
 .. code-block:: bash
 
-    $ php bin/console doctrine:schema:create
+    $ bin/console doctrine:schema:create
 
 .. note::
     This article assumes you have basic knowledge of the Doctrine2 ORM and
diff --git a/docs/getting_started/installation.rst b/docs/getting_started/installation.rst
index 220ead4ac2..3847f4ce0c 100644
--- a/docs/getting_started/installation.rst
+++ b/docs/getting_started/installation.rst
@@ -188,8 +188,8 @@ install the assets:
 
 .. code-block:: bash
 
-    $ php bin/console cache:clear
-    $ php bin/console assets:install
+    $ bin/console cache:clear
+    $ bin/console assets:install
 
 The Admin Interface
 -------------------
@@ -199,7 +199,7 @@ server, you can now visit the admin page on http://localhost:8000/admin
 
 .. note::
     This tutorial assumes you are using the build-in server using the
-    ``php bin/console server:start`` (or ``server:run``) command.
+    ``bin/console server:start`` (or ``server:run``) command.
 
 .. figure:: ../images/getting_started_empty_dashboard.png
    :align: center
diff --git a/docs/getting_started/the_form_view.rst b/docs/getting_started/the_form_view.rst
index f586b4ea05..598b31a7b8 100644
--- a/docs/getting_started/the_form_view.rst
+++ b/docs/getting_started/the_form_view.rst
@@ -254,7 +254,7 @@ You've now finished your nice form view for the ``BlogPost`` model. Now it's
 time to test it out by creating a post.
 
 After pressing the "Create" button, you probably see a green message like:
-*Item "AppBundle\Entity\BlogPost:00000000192ba93c000000001b786396" has been
+*Item "App\Entity\BlogPost:00000000192ba93c000000001b786396" has been
 successfully created.*
 
 While it's very friendly of the SonataAdminBundle to notify the admin of a
diff --git a/docs/reference/action_create_edit.rst b/docs/reference/action_create_edit.rst
index 952e2c5719..20c0b4f6c8 100644
--- a/docs/reference/action_create_edit.rst
+++ b/docs/reference/action_create_edit.rst
@@ -2,7 +2,6 @@ Creating and Editing objects
 ============================
 
 .. note::
-
     This document is a stub representing a new work in progress. If you're reading
     this you can help contribute, **no matter what your experience level with Sonata
     is**. Check out the `issues on Github`_ for more information about how to get involved.
@@ -10,6 +9,10 @@ Creating and Editing objects
 This document will cover the Create and Edit actions. It will cover configuration
 of the fields and forms available in these views and any other relevant settings.
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
 
 Basic configuration
 -------------------
@@ -54,7 +57,7 @@ For more detailed information about routes, see :doc:`routing`.
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PersonAdmin.php
+    // src/Admin/PersonAdmin.php
 
     class PersonAdmin extends AbstractAdmin
     {
@@ -108,7 +111,7 @@ has 4 parameters:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PersonAdmin.php
+    // src/Admin/PersonAdmin.php
 
     class PersonAdmin extends AbstractAdmin
     {
@@ -149,12 +152,10 @@ options for the group itself.
 - ``translation_domain``: The translation domain for the form group title
   (the Admin translation domain is used by default).
 
-To specify options, do as follows:
-
-.. code-block:: php
+To specify options, do as follows::
 
     <?php
-    // src/AppBundle/Admin/PersonAdmin.php
+    // src/Admin/PersonAdmin.php
 
     class PersonAdmin extends AbstractAdmin
     {
diff --git a/docs/reference/action_export.rst b/docs/reference/action_export.rst
index 21f8d97667..ab9474d771 100644
--- a/docs/reference/action_export.rst
+++ b/docs/reference/action_export.rst
@@ -3,11 +3,16 @@ The Export action
 
 This document will cover the Export action and related configuration options.
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 Basic configuration
 -------------------
 
-If you have registered the ``SonataExporterBundle`` bundle in the kernel of your application,
-you can benefit from a lot of flexibility:
+If you have registered the ``SonataExporterBundle`` bundle, you can benefit
+from a lot of flexibility:
 
 * You can configure default exporters globally.
 * You can add custom exporters, also globally.
@@ -19,8 +24,9 @@ Translation
 ~~~~~~~~~~~
 
 All field names are translated by default.
-An internal mechanism checks if a field matching the translator strategy label exists in the current translation file
-and will use the field name as a fallback.
+An internal mechanism checks if a field matching the translator strategy
+label exists in the current translation file and will use the field name
+as a fallback.
 
 Picking which fields to export
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -28,20 +34,18 @@ Picking which fields to export
 By default, all fields are exported. More accurately, it depends on the
 persistence backend you are using, but for instance, the doctrine ORM backend
 exports all fields (associations are not exported). If you want to change this
-behavior for a specific admin, you can override the ``getExportFields()`` method:
-
-.. code-block:: php
+behavior for a specific admin, you can override the ``getExportFields()`` method::
 
     <?php
 
     public function getExportFields()
     {
-        return ['givenName', 'familyName', 'contact.phone'];
+        return ['givenName', 'familyName', 'contact.phone', 'getAddress'];
     }
 
 .. note::
-
-    Note that you can use `contact.phone` to access the `phone` property of `Contact` entity
+    Note that you can use `contact.phone` to access the `phone` property
+    of `Contact` entity. Or use a getter if you have some virtual field.
 
 You can also tweak the list by creating an admin extension that implements the
 ``configureExportFields()`` method.
@@ -74,12 +78,10 @@ method in your admin class.
 Customizing the query used to fetch the results
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 If you want to customize the query used to fetch the results for a specific admin,
-you can override the ``getDataSourceIterator()`` method:
-
-.. code-block:: php
+you can override the ``getDataSourceIterator()`` method::
 
     <?php
-    // src/AppBundle/Admin/PersonAdmin.php
+    // src/Admin/PersonAdmin.php
 
     class PersonAdmin extends AbstractAdmin
     {
diff --git a/docs/reference/action_list.rst b/docs/reference/action_list.rst
index f5b1a93765..be60b69677 100644
--- a/docs/reference/action_list.rst
+++ b/docs/reference/action_list.rst
@@ -47,7 +47,6 @@ Here is an example:
 .. code-block:: php
 
     <?php
-
     // ...
 
     public function configureListFields(ListMapper $listMapper)
@@ -112,15 +111,19 @@ Options
     * ``(m)`` stands for mandatory
     * ``(o)`` stands for optional
 
-- ``type`` (m): defines the field type - mandatory for the field description itself but will try to detect the type automatically if not specified
+- ``type`` (m): defines the field type - mandatory for the field description
+  itself but will try to detect the type automatically if not specified
 - ``template`` (o): the template used to render the field
 - ``label`` (o): the name used for the column's title
-- ``link_parameters`` (o): add link parameter to the related Admin class when the ``Admin::generateUrl`` is called
+- ``link_parameters`` (o): add link parameter to the related Admin class
+  when the ``Admin::generateUrl`` is called
 - ``code`` (o): the method name to retrieve the related value (for example,
   if you have an `array` type field, you would like to show info prettier
   than `[0] => 'Value'`; useful when simple getter is not enough).
   Notice: works with string-like types (string, text, html)
-- ``associated_property`` (o): property path to retrieve the "string" representation of the collection element, or a closure with the element as argument and return a string.
+- ``associated_property`` (o): property path to retrieve the "string"
+  representation of the collection element, or a closure with the element
+  as argument and return a string.
 - ``identifier`` (o): if set to true a link appears on the value to edit the element
 
 Available types and associated options
@@ -192,10 +195,10 @@ Available types and associated options
 |           | hide_protocol  | Hide http:// or https:// (default: false)                             |
 +-----------+----------------+-----------------------------------------------------------------------+
 
-If you have the SonataDoctrineORMAdminBundle installed, you have access to more field types, see `SonataDoctrineORMAdminBundle Documentation <https://sonata-project.org/bundles/doctrine-orm-admin/master/doc/reference/list_field_definition.html>`_.
+If you have the SonataDoctrineORMAdminBundle installed, you have access
+to more field types, see `SonataDoctrineORMAdminBundle Documentation`_.
 
 .. note::
-
     It is better to prefer non negative notions when possible for boolean
     values so use the ``inverse`` option if you really cannot find a good enough
     antonym for the name you have.
@@ -233,7 +236,7 @@ the ``datagridValues`` array property. All three keys ``_page``, ``_sort_order``
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     use Sonata\AdminBundle\Admin\AbstractAdmin;
 
@@ -272,7 +275,7 @@ You can add filters to let user control which data will be displayed.
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     use Sonata\AdminBundle\Datagrid\DatagridMapper;
 
@@ -290,7 +293,8 @@ You can add filters to let user control which data will be displayed.
         // ...
     }
 
-All filters are hidden by default for space-saving. User has to check which filter he wants to use.
+All filters are hidden by default for space-saving. User has to check which
+filter he wants to use.
 
 To make the filter always visible (even when it is inactive), set the parameter
 ``show_filter`` to ``true``.
@@ -330,8 +334,9 @@ Though this ``operator_type`` is automatically detected it can be changed or eve
         ;
     }
 
-If you don't need the advanced filters, or all your ``operator_type`` are hidden, you can disable them by setting
-``advanced_filter`` to ``false``. You need to disable all advanced filters to make the button disappear.
+If you don't need the advanced filters, or all your ``operator_type``
+are hidden, you can disable them by setting ``advanced_filter`` to ``false``.
+You need to disable all advanced filters to make the button disappear.
 
 .. code-block:: php
 
@@ -351,7 +356,8 @@ Default filters
 ^^^^^^^^^^^^^^^
 
 Default filters can be added to the datagrid values by using the ``configureDefaultFilterValues`` method.
-A filter has a ``value`` and an optional ``type``. If no ``type`` is given the default type ``is equal`` is used.
+A filter has a ``value`` and an optional ``type``. If no ``type`` is
+given the default type ``is equal`` is used.
 
 .. code-block:: php
 
@@ -363,12 +369,10 @@ A filter has a ``value`` and an optional ``type``. If no ``type`` is given the d
         ];
     }
 
-Available types are represented through classes which can be found here:
-https://github.com/sonata-project/SonataCoreBundle/tree/master/Form/Type
+Available types are represented through classes which can be found `here`_.
 
-Types like ``equal`` and ``boolean`` use constants to assign a choice of ``type`` to an ``integer`` for its ``value``:
-
-.. code-block:: php
+Types like ``equal`` and ``boolean`` use constants to assign a choice of
+``type`` to an ``integer`` for its ``value``::
 
     <?php
     // SonataCoreBundle/Form/Type/EqualType.php
@@ -384,9 +388,7 @@ Types like ``equal`` and ``boolean`` use constants to assign a choice of ``type`
 The integers are then passed in the URL of the list action e.g.:
 **/admin/user/user/list?filter[enabled][type]=1&filter[enabled][value]=1**
 
-This is an example using these constants for an ``boolean`` type:
-
-.. code-block:: php
+This is an example using these constants for an ``boolean`` type::
 
     use Sonata\UserBundle\Admin\Model\UserAdmin as SonataUserAdmin;
     use Sonata\CoreBundle\Form\Type\EqualType;
@@ -402,9 +404,9 @@ This is an example using these constants for an ``boolean`` type:
         ];
     }
 
-Please note that setting a ``false`` value on a the ``boolean`` type will not work since the type expects an integer of  ``2`` as ``value`` as defined in the class constants:
-
-.. code-block:: php
+Please note that setting a ``false`` value on a the ``boolean`` type
+will not work since the type expects an integer of  ``2`` as ``value``
+as defined in the class constants::
 
     <?php
     // SonataCoreBundle/Form/Type/BooleanType.php
@@ -417,7 +419,8 @@ Please note that setting a ``false`` value on a the ``boolean`` type will not wo
         const TYPE_NO = 2;
     }
 
-Default filters can also be added to the datagrid values by overriding the ``getFilterParameters`` method.
+Default filters can also be added to the datagrid values by overriding
+the ``getFilterParameters`` method.
 
 .. code-block:: php
 
@@ -463,14 +466,14 @@ This approach is useful when you need to create dynamic filters.
         }
     }
 
-Please note that this is not a secure approach to hide posts from others. It's just an example for setting filters on demand.
+Please note that this is not a secure approach to hide posts from others.
+It's just an example for setting filters on demand.
 
 Callback filter
 ^^^^^^^^^^^^^^^
 
-If you have the **SonataDoctrineORMAdminBundle** installed you can use the ``doctrine_orm_callback`` filter type e.g. for creating a full text filter:
-
-.. code-block:: php
+If you have the **SonataDoctrineORMAdminBundle** installed you can use the
+``doctrine_orm_callback`` filter type e.g. for creating a full text filter::
 
     use Sonata\UserBundle\Admin\Model\UserAdmin as SonataUserAdmin;
     use Sonata\AdminBundle\Datagrid\DatagridMapper;
@@ -506,9 +509,8 @@ If you have the **SonataDoctrineORMAdminBundle** installed you can use the ``doc
         }
     }
 
-You can also get the filter type which can be helpful to change the operator type of your condition(s):
-
-.. code-block:: php
+You can also get the filter type which can be helpful to change the operator
+type of your condition(s)::
 
     use Sonata\CoreBundle\Form\Type\EqualType;
 
@@ -541,8 +543,10 @@ You can also get the filter type which can be helpful to change the operator typ
 Visual configuration
 --------------------
 
-You have the possibility to configure your List View to customize the render without overriding to whole template.
-You can :
+You have the possibility to configure your List View to customize the
+render without overriding to whole template.
+
+You can:
 
 - `header_style`: Customize the style of header (width, color, background, align...)
 - `header_class`: Customize the class of the header
@@ -580,12 +584,13 @@ You can :
         ;
     }
 
-If you want to customise the `collapse` option, you can also give an array to override the default parameters.
+If you want to customise the `collapse` option, you can also give an array
+to override the default parameters.
 
 .. code-block:: php
 
             // ...
-            ->add('description', 'text', [
+            ->add('description', TextType::class, [
                 'header_style' => 'width: 35%',
                 'collapse' => [
                     'height' => 40, // height in px
@@ -595,9 +600,7 @@ If you want to customise the `collapse` option, you can also give an array to ov
             ])
             // ...
 
-If you want to show only the `label_icon`:
-
-.. code-block:: php
+If you want to show only the `label_icon`::
 
             // ...
             ->add('upvotes', null, [
@@ -606,7 +609,7 @@ If you want to show only the `label_icon`:
             ])
             // ...
 
-.. _`issues on GitHub`: https://github.com/sonata-project/SonataAdminBundle/issues/1519
+`issues on GitHub`_
 
 Mosaic view button
 ------------------
@@ -619,8 +622,8 @@ You have the possibility to show/hide mosaic view button.
         # for hide mosaic view button on all screen using `false`
         show_mosaic_button:   true
 
-You can show/hide mosaic view button using admin service configuration. You need to add option ``show_mosaic_button``
-in your admin services:
+You can show/hide mosaic view button using admin service configuration.
+You need to add option ``show_mosaic_button`` in your admin services:
 
 .. code-block:: yaml
 
@@ -640,6 +643,9 @@ Checkbox range selection
 ------------------------
 
 .. tip::
-
     You can check / uncheck a range of checkboxes by clicking a first one,
     then a second one with shift + click.
+
+.. _`issues on GitHub`: https://github.com/sonata-project/SonataAdminBundle/issues/1519
+.. _`SonataDoctrineORMAdminBundle Documentation`: https://sonata-project.org/bundles/doctrine-orm-admin/master/doc/reference/list_field_definition.html
+.. _`here`: https://github.com/sonata-project/SonataCoreBundle/tree/master/Form/Type
\ No newline at end of file
diff --git a/docs/reference/action_show.rst b/docs/reference/action_show.rst
index 6ffd999d28..c609ed28cb 100644
--- a/docs/reference/action_show.rst
+++ b/docs/reference/action_show.rst
@@ -2,13 +2,17 @@ The Show action
 ===============
 
 .. note::
-
     This document is a stub representing a new work in progress. If you're reading
     this you can help contribute, **no matter what your experience level with Sonata
     is**. Check out the `issues on GitHub`_ for more information about how to get involved.
 
 This document will cover the Show action and related configuration options.
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 Basic configuration
 -------------------
 
@@ -27,9 +31,12 @@ Group options
 When adding a group to your show page, you may specify some options for the group itself.
 
 - ``collapsed``: unused at the moment
-- ``class``: the class for your group in the admin; by default, the value is set to ``col-md-12``.
-- ``fields``: the fields in your group (you should NOT override this unless you know what you're doing).
-- ``box_class``: the class for your group box in the admin; by default, the value is set to ``box box-primary``.
+- ``class``: the class for your group in the admin; by default, the value
+  is set to ``col-md-12``.
+- ``fields``: the fields in your group (you should NOT override this unless
+  you know what you're doing).
+- ``box_class``: the class for your group box in the admin; by default,
+  the value is set to ``box box-primary``.
 - ``description``: to complete
 - ``translation_domain``: to complete
 
@@ -38,7 +45,7 @@ To specify options, do as follow:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PersonAdmin.php
+    // src/Admin/PersonAdmin.php
 
     use Sonata\AdminBundle\Admin\AbstractAdmin;
     use Sonata\AdminBundle\Show\ShowMapper;
@@ -68,7 +75,7 @@ Here is an example of how to achieve this :
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PersonAdmin.php
+    // src/Admin/PersonAdmin.php
 
     use Sonata\AdminBundle\Show\ShowMapper;
 
@@ -95,18 +102,13 @@ Here is an example of how to achieve this :
 Customising the query used to show the object from within your Admin class
 --------------------------------------------------------------------------
 
-Setting up a showAction is pretty much the same as a form, which we did in the initial setup.
-
-It is actually a bit easier, because we are only concerned with displaying information.
-
-Smile, the hard part is already done.
-
-The following is a working example of a ShowAction
-
-.. code-block:: php
+Setting up a showAction is pretty much the same as a form, which we did
+in the initial setup. It is actually a bit easier, because we are only
+concerned with displaying information. Smile, the hard part is already done.
+The following is a working example of a ShowAction::
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     use Sonata\AdminBundle\Show\ShowMapper;
 
@@ -136,9 +138,7 @@ The following is a working example of a ShowAction
     }
 
 .. tip::
-    To customize the displayed label of a show field you can use the ``label`` option:
-
-    .. code-block:: php
+    To customize the displayed label of a show field you can use the ``label`` option::
 
         $showMapper->add('name', null, ['label' => 'UserName']);
 
@@ -161,7 +161,7 @@ The first thing you need to do is define it in app/config/config/yml:
 
 Once you have defined this, Sonata Admin looks for it in the following location:
 
-``src/AppBundle/Resources/views/Admin/Display_Client.html.twig``
+``templates/Admin/Display_Client.html.twig``
 
 Now that you have told Sonata Admin where to find the template, it is time to put one in there.
 
diff --git a/docs/reference/advanced_configuration.rst b/docs/reference/advanced_configuration.rst
index d856752b57..e9248bd476 100644
--- a/docs/reference/advanced_configuration.rst
+++ b/docs/reference/advanced_configuration.rst
@@ -1,10 +1,16 @@
 Advanced configuration
 ======================
 
+.. note::
+   This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 Service Configuration
 ---------------------
 
-When you create a new Admin service you can configure its dependencies, the services which are injected by default are:
+When you create a new Admin service you can configure its dependencies,
+the services which are injected by default are:
 
 =========================     =============================================
 Dependencies                  Service Id
@@ -37,7 +43,7 @@ You have 2 ways of defining the dependencies inside ``services.xml``:
 
     .. code-block:: xml
 
-        <service id="app.admin.project" class="AppBundle\Admin\ProjectAdmin">
+        <service id="app.admin.project" class="App\Admin\ProjectAdmin">
             <tag
                 name="sonata.admin"
                 manager_type="orm"
@@ -47,7 +53,7 @@ You have 2 ways of defining the dependencies inside ``services.xml``:
                 route_builder="sonata.admin.route.path_info"
                 />
             <argument />
-            <argument>AppBundle\Entity\Project</argument>
+            <argument>App\Entity\Project</argument>
             <argument />
         </service>
 
@@ -56,12 +62,12 @@ You have 2 ways of defining the dependencies inside ``services.xml``:
     .. code-block:: yaml
 
         app.admin.project:
-            class: AppBundle\Admin\ProjectAdmin
+            class: App\Admin\ProjectAdmin
             tags:
                 - { name: sonata.admin, manager_type: orm, group: "Project", label: "Project", label_translator_strategy: "sonata.admin.label.strategy.native",  route_builder: "sonata.admin.route.path_info" }
             arguments:
                 - ~
-                - AppBundle\Entity\Project
+                - App\Entity\Project
                 - ~
             public: true
 
@@ -71,7 +77,7 @@ You have 2 ways of defining the dependencies inside ``services.xml``:
 
     .. code-block:: xml
 
-        <service id="app.admin.project" class="AppBundle\Admin\ProjectAdmin">
+        <service id="app.admin.project" class="App\Admin\ProjectAdmin">
             <tag
                 name="sonata.admin"
                 manager_type="orm"
@@ -79,7 +85,7 @@ You have 2 ways of defining the dependencies inside ``services.xml``:
                 label="Project"
                 />
             <argument />
-            <argument>AppBundle\Entity\Project</argument>
+            <argument>App\Entity\Project</argument>
             <argument />
 
             <call method="setLabelTranslatorStrategy">
@@ -96,12 +102,12 @@ You have 2 ways of defining the dependencies inside ``services.xml``:
     .. code-block:: yaml
 
         app.admin.project:
-            class: AppBundle\Admin\ProjectAdmin
+            class: App\Admin\ProjectAdmin
             tags:
                 - { name: sonata.admin, manager_type: orm, group: "Project", label: "Project" }
             arguments:
                 - ~
-                - AppBundle\Entity\Project
+                - App\Entity\Project
                 - ~
             calls:
                 - [ setLabelTranslatorStrategy, [ "@sonata.admin.label.strategy.native" ]]
@@ -115,7 +121,7 @@ application's config file:
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
         admins:
             sonata_admin:
                 sonata.order.admin.order:   # id of the admin service this setting is for
@@ -133,7 +139,7 @@ To create your own RouteBuilder create the PHP class and register it as a servic
 .. code-block:: php
 
     <?php
-    namespace AppBundle\Route;
+    namespace App\Route;
 
     use Sonata\AdminBundle\Builder\RouteBuilderInterface;
     use Sonata\AdminBundle\Admin\AdminInterface;
@@ -165,7 +171,7 @@ To create your own RouteBuilder create the PHP class and register it as a servic
 
     .. code-block:: xml
 
-        <service id="app.admin.entity_route_builder" class="AppBundle\Route\EntityRouterBuilder">
+        <service id="app.admin.entity_route_builder" class="App\Route\EntityRouterBuilder">
             <argument type="service" id="sonata.admin.audit.manager" />
         </service>
 
@@ -177,7 +183,7 @@ To create your own RouteBuilder create the PHP class and register it as a servic
 
         services:
             app.admin.entity_route_builder:
-                class: AppBundle\Route\EntityRouterBuilder
+                class: App\Route\EntityRouterBuilder
                 arguments:
                     - "@sonata.admin.audit.manager"
 
@@ -192,25 +198,24 @@ Lets consider a base class named `Person` and its subclasses `Student` and `Teac
 
     .. code-block:: xml
 
-        <service id="app.admin.person" class="AppBundle\Admin\PersonAdmin">
+        <service id="app.admin.person" class="App\Admin\PersonAdmin">
             <tag name="sonata.admin" manager_type="orm" group="admin" label="Person" />
             <argument/>
-            <argument>AppBundle\Entity\Person</argument>
+            <argument>App\Entity\Person</argument>
             <argument></argument>
             <call method="setSubClasses">
                 <argument type="collection">
-                    <argument key="student">AppBundle\Entity\Student</argument>
-                    <argument key="teacher">AppBundle\Entity\Teacher</argument>
+                    <argument key="student">App\Entity\Student</argument>
+                    <argument key="teacher">App\Entity\Teacher</argument>
                 </argument>
             </call>
         </service>
 
-You will just need to change the way forms are configured in order to take into account these new subclasses:
-
-.. code-block:: php
+You will just need to change the way forms are configured in order to
+take into account these new subclasses::
 
     <?php
-    // src/AppBundle/Admin/PersonAdmin.php
+    // src/Admin/PersonAdmin.php
 
     protected function configureFormFields(FormMapper $formMapper)
     {
@@ -235,9 +240,7 @@ ACL
 ^^^
 
 Though the route linked by a menu may be protected the Tab Menu will not automatically check the ACl for you.
-The link will still appear unless you manually check it using the `hasAccess` method:
-
-.. code-block:: php
+The link will still appear unless you manually check it using the `hasAccess` method::
 
     <?php
 
@@ -260,12 +263,10 @@ Dropdowns
 ^^^^^^^^^
 
 You can use dropdowns inside the Tab Menu by default. This can be achieved by using
-the `'dropdown' => true` attribute:
-
-.. code-block:: php
+the `'dropdown' => true` attribute::
 
     <?php
-    // src/AppBundle/Admin/PersonAdmin.php
+    // src/Admin/PersonAdmin.php
 
     protected function configureTabMenu(MenuItemInterface $menu, $action, AdminInterface $childAdmin = null)
     {
@@ -287,7 +288,7 @@ If you want to use the Tab Menu in a different way, you can replace the Menu Tem
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             templates:
@@ -309,19 +310,16 @@ of data associated with the item, respectively.
     ]);
 
 You can also set the translation domain on the menu root, and children will
-inherit it :
-
-.. code-block:: php
+inherit it::
 
     <?php
+
     $menu->setExtra('translation_domain', 'My domain');
 
 Filter parameters
 ^^^^^^^^^^^^^^^^^
 
-You can add or override filter parameters to the Tab Menu:
-
-.. code-block:: php
+You can add or override filter parameters to the Tab Menu::
 
     <?php
 
@@ -358,16 +356,14 @@ You can add or override filter parameters to the Tab Menu:
         }
     }
 
-The `Delivery` class is based on the `sonata_type_translatable_choice` example inside the Core's documentation:
-http://sonata-project.org/bundles/core/master/doc/reference/form_types.html#sonata-type-translatable-choice
+The `Delivery` class is based on the `sonata_type_translatable_choice` example inside the `Core's documentation`_.
 
 
 Actions Menu
 ------------
 
-You can add custom items to the actions menu for a specific action by overriding the following method:
-
-.. code-block:: php
+You can add custom items to the actions menu for a specific action by
+overriding the following method::
 
     public function configureActionButtons(AdminInterface $admin, $list, $action, $object)
     {
@@ -391,27 +387,29 @@ You can add custom items to the actions menu for a specific action by overriding
 Disable content stretching
 --------------------------
 
-You can disable ``html``, ``body`` and ``sidebar`` elements stretching. These containers are forced
-to be full height by default. If you use custom layout or just don't need such behavior,
-add ``no-stretch`` class to the ``<html>`` tag.
+You can disable ``html``, ``body`` and ``sidebar`` elements stretching.
+These containers are forced to be full height by default. If you use
+custom layout or just don't need such behavior, add ``no-stretch`` class
+to the ``<html>`` tag.
 
 For example:
 
 .. code-block:: html+jinja
 
-    {# src/AppBundle/Resources/views/standard_layout.html.twig #}
+    {# templates/standard_layout.html.twig #}
 
     {% block html_attributes %}class="no-js no-stretch"{% endblock %}
 
 Custom Action Access Management
 -------------------------------
 
-You can customize the access system inside the CRUDController by adding some entries inside the  `$accessMapping` array in the linked Admin.
+You can customize the access system inside the CRUDController by adding
+some entries inside the  `$accessMapping` array in the linked Admin.
 
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     class CustomAdmin extends AbstractAdmin
     {
@@ -422,7 +420,7 @@ You can customize the access system inside the CRUDController by adding some ent
     }
 
     <?php
-    // src/AppBundle/Controller/CustomCRUDController.php
+    // src/Controller/CustomCRUDController.php
 
     class CustomCRUDController extends CRUDController
     {
@@ -445,12 +443,11 @@ You can customize the access system inside the CRUDController by adding some ent
         // ...
     }
 
-You can also fully customize how you want to handle your access management by simply overriding ``checkAccess`` function
-
-.. code-block:: php
+You can also fully customize how you want to handle your access management
+by simply overriding ``checkAccess`` function::
 
     <?php
-    // src/AppBundle/Admin/CustomAdmin.php
+    // src/Admin/CustomAdmin.php
 
     class CustomAdmin extends AbstractAdmin
     {
@@ -461,3 +458,5 @@ You can also fully customize how you want to handle your access management by si
 
         // ...
     }
+
+.. _`Core's documentation`: http://sonata-project.org/bundles/core/master/doc/reference/form_types.html#sonata-type-translatable-choice
diff --git a/docs/reference/architecture.rst b/docs/reference/architecture.rst
index 26d7340cb8..ef4bd6f1ea 100644
--- a/docs/reference/architecture.rst
+++ b/docs/reference/architecture.rst
@@ -1,17 +1,22 @@
 Architecture
 ============
 
-The architecture of the ``SonataAdminBundle`` is primarily inspired by the Django Admin
-Project, which is truly a great project. More information can be found at the
-`Django Project Website`_.
+The architecture of the ``SonataAdminBundle`` is primarily inspired by
+the Django Admin Project, which is truly a great project. More information
+can be found at the `Django Project Website`_.
 
-If you followed the instructions on the :doc:`../getting_started/creating_an_admin` page, you should by
-now have an ``Admin`` class and an ``Admin`` service. In this chapter, we'll discuss more in
-depth how it works.
+If you followed the instructions on the :doc:`../getting_started/creating_an_admin`
+page, you should by now have an ``Admin`` class and an ``Admin`` service.
+In this chapter, we'll discuss more in depth how it works.
 
 The Admin Class
 ---------------
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 The ``Admin`` class maps a specific model to the rich CRUD interface provided by
 ``SonataAdminBundle``. In other words, using your ``Admin`` classes, you can configure
 what is shown by ``SonataAdminBundle`` in each CRUD action for the associated model.
@@ -63,16 +68,16 @@ MenuFactory                     generates the side menu, depending on the curren
 
 
 All of these dependencies have default values that you can override when declaring any of
-your ``Admin`` services. This is done using a ``call`` to the matching ``setter`` :
+your ``Admin`` services. This is done using a ``call`` to the matching ``setter``:
 
 .. configuration-block::
 
     .. code-block:: xml
 
-        <service id="app.admin.post" class="AppBundle\Admin\PostAdmin">
+        <service id="app.admin.post" class="App\Admin\PostAdmin">
               <tag name="sonata.admin" manager_type="orm" group="Content" label="Post" />
               <argument />
-              <argument>AppBundle\Entity\Post</argument>
+              <argument>App\Entity\Post</argument>
               <argument />
               <call method="setLabelTranslatorStrategy">
                   <argument type="service" id="sonata.admin.label.strategy.underscore" />
@@ -83,19 +88,19 @@ your ``Admin`` services. This is done using a ``call`` to the matching ``setter`
 
         services:
             app.admin.post:
-                class: AppBundle\Admin\PostAdmin
+                class: App\Admin\PostAdmin
                 tags:
                     - { name: sonata.admin, manager_type: orm, group: "Content", label: "Post" }
                 arguments:
                     - ~
-                    - AppBundle\Entity\Post
+                    - App\Entity\Post
                     - ~
                 calls:
                     - [ setLabelTranslatorStrategy, ["@sonata.admin.label.strategy.underscore"]]
                 public: true
 
-Here, we declare the same ``Admin`` service as in the :doc:`../getting_started/creating_an_admin` chapter, but using a
-different label translator strategy, replacing the default one. Notice that
+Here, we declare the same ``Admin`` service as in the :doc:`../getting_started/creating_an_admin`
+chapter, but using a different label translator strategy, replacing the default one. Notice that
 ``sonata.admin.label.strategy.underscore`` is a service provided by ``SonataAdminBundle``,
 but you could just as easily use a service of your own.
 
@@ -119,19 +124,19 @@ the Dependency Injection Container (DIC).
 This is particularly useful if you decide to extend the ``CRUDController`` to
 add new actions or change the behavior of existing ones. You can specify which controller
 to use when declaring the ``Admin`` service by passing it as the 3rd argument. For example
-to set the controller to ``AppBundle:PostAdmin``:
+to set the controller to ``App:PostAdmin``:
 
 .. configuration-block::
 
     .. code-block:: xml
 
-        <service id="app.admin.post" class="AppBundle\Admin\PostAdmin">
+        <service id="app.admin.post" class="App\Admin\PostAdmin">
             <tag name="sonata.admin" manager_type="orm" group="Content" label="Post" />
             <argument />
-            <argument>AppBundle\Entity\Post</argument>
-            <argument>AppBundle:PostAdmin</argument>
+            <argument>App\Entity\Post</argument>
+            <argument>App:PostAdmin</argument>
             <call method="setTranslationDomain">
-                <argument>AppBundle</argument>
+                <argument>App</argument>
             </call>
         </service>
 
@@ -139,15 +144,15 @@ to set the controller to ``AppBundle:PostAdmin``:
 
         services:
             app.admin.post:
-                class: AppBundle\Admin\PostAdmin
+                class: App\Admin\PostAdmin
                 tags:
                     - { name: sonata.admin, manager_type: orm, group: "Content", label: "Post" }
                 arguments:
                     - ~
-                    - AppBundle\Entity\Post
-                    - AppBundle:PostAdmin
+                    - App\Entity\Post
+                    - App\Controller\PostAdminController
                 calls:
-                    - [ setTranslationDomain, [AppBundle]]
+                    - [ setTranslationDomain, [App]]
                 public: true
 
 When extending ``CRUDController``, remember that the ``Admin`` class already has
@@ -173,20 +178,21 @@ Your ``Admin`` class defines which of your model's fields will be available in e
 action defined in your ``CRUDController``. So, for each action, a list of field mappings
 is generated. These lists are implemented using the ``FieldDescriptionCollection`` class
 which stores instances of ``FieldDescriptionInterface``. Picking up on our previous
-``PostAdmin`` class example:
-
-.. code-block:: php
+``PostAdmin`` class example::
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
-    namespace AppBundle\Admin;
+    namespace App\Admin;
 
     use Sonata\AdminBundle\Admin\AbstractAdmin;
     use Sonata\AdminBundle\Datagrid\ListMapper;
     use Sonata\AdminBundle\Datagrid\DatagridMapper;
     use Sonata\AdminBundle\Form\FormMapper;
     use Sonata\AdminBundle\Show\ShowMapper;
+    use Symfony\Bridge\Doctrine\Form\Type\EntityType;
+    use Symfony\Component\Form\Extension\Core\Type\TextType;
+    use App\Entity\User;
 
     class PostAdmin extends AbstractAdmin
     {
@@ -194,11 +200,11 @@ which stores instances of ``FieldDescriptionInterface``. Picking up on our previ
         protected function configureFormFields(FormMapper $formMapper)
         {
             $formMapper
-                ->add('title', 'text', [
+                ->add('title', TextType:class, [
                     'label' => 'Post Title'
                 ])
-                ->add('author', 'entity', [
-                    'class' => 'AppBundle\Entity\User'
+                ->add('author', EntityType::class, [
+                    'class' => User::class
                 ])
 
                 // if no type is specified, SonataAdminBundle tries to guess it
diff --git a/docs/reference/batch_actions.rst b/docs/reference/batch_actions.rst
index 210467fa8d..19c50150b1 100644
--- a/docs/reference/batch_actions.rst
+++ b/docs/reference/batch_actions.rst
@@ -2,15 +2,22 @@ Batch actions
 =============
 
 Batch actions are actions triggered on a set of selected objects. By default,
-Admins have a ``delete`` action which allows you to remove several entries at once.
+Admins have a ``delete`` action which allows you to remove several entries
+at once.
+
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
 
 Defining new actions
 --------------------
 
 To create a new custom batch action which appears in the list view follow these steps:
 
-Override ``configureBatchActions()`` in your ``Admin`` class to define the new batch actions
-by adding them to the ``$actions`` array. Each key represent a batch action and could contain these settings:
+Override ``configureBatchActions()`` in your ``Admin`` class to define
+the new batch actions by adding them to the ``$actions`` array.
+Each key represent a batch action and could contain these settings:
 
 - **label**: The name to use when offering this option to users, should be passed through the translator
   (default: the label is generated via the labelTranslatorStrategy)
@@ -61,9 +68,9 @@ granularity), the passed query is ``null``.
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Controller/CRUDController.php
+    // src/Controller/CRUDController.php
 
-    namespace AppBundle\Controller;
+    namespace App\Controller;
 
     use Sonata\AdminBundle\Controller\CRUDController as BaseController;
     use Sonata\AdminBundle\Datagrid\ProxyQueryInterface;
@@ -134,14 +141,15 @@ granularity), the passed query is ``null``.
 (Optional) Overriding the batch selection template
 --------------------------------------------------
 
-A merge action requires two kinds of selection: a set of source objects to merge from
-and a target object to merge into. By default, batch_actions only let you select one set
-of objects to manipulate. We can override this behavior by changing our list template
-(``list__batch.html.twig``) and adding a radio button to choose the target object.
+A merge action requires two kinds of selection: a set of source objects
+to merge from and a target object to merge into. By default, batch_actions
+only let you select one set of objects to manipulate. We can override this
+behavior by changing our list template (``list__batch.html.twig``) and adding
+a radio button to choose the target object.
 
 .. code-block:: html+jinja
 
-    {# src/AppBundle/Resources/views/CRUD/list__batch.html.twig #}
+    {# templates/bundles/SonataAdminBundle/CRUD/list__batch.html.twig #}
     {# see @SonataAdmin/CRUD/list__batch.html.twig for the current default template #}
 
     {% extends get_admin_template('base_list_field', admin.code) %}
@@ -153,31 +161,15 @@ of objects to manipulate. We can override this behavior by changing our list tem
         <input type="radio" name="targetId" value="{{ admin.id(object) }}" />
     {% endblock %}
 
-
-And add this:
-
-.. code-block:: php
-
-    <?php
-    // src/AppBundle/AppBundle.php
-
-    public function getParent()
-    {
-        return 'SonataAdminBundle';
-    }
-
-See the `Symfony bundle overriding mechanism`_
-for further explanation of overriding bundle templates.
-
-
 (Optional) Overriding the default relevancy check function
 ----------------------------------------------------------
 
-By default, batch actions are not executed if no object was selected, and the user is notified of
-this lack of selection. If your custom batch action needs more complex logic to determine if
-an action can be performed or not, just define a ``batchAction<MyAction>IsRelevant`` method
-(e.g. ``batchActionMergeIsRelevant``) in your ``CRUDController`` class. This check is performed
-before the user is asked for confirmation, to make sure there is actually something to confirm.
+By default, batch actions are not executed if no object was selected, and
+the user is notified of this lack of selection. If your custom batch action
+needs more complex logic to determine if an action can be performed or not,
+just define a ``batchAction<MyAction>IsRelevant`` method (e.g. ``batchActionMergeIsRelevant``)
+in your ``CRUDController`` class. This check is performed before the user is asked for confirmation,
+to make sure there is actually something to confirm.
 
 This method may return three different values:
 
@@ -190,9 +182,9 @@ This method may return three different values:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Controller/CRUDController.php
+    // src/Controller/CRUDController.php
 
-    namespace AppBundle\Controller;
+    namespace App\Controller;
 
     use Sonata\AdminBundle\Controller\CRUDController as BaseController;
     use Symfony\Component\HttpFoundation\Request;
@@ -234,8 +226,9 @@ This method may return three different values:
 (Optional) Executing a pre batch hook
 -------------------------------------
 
-In your admin class you can create a ``preBatchAction`` method to execute something before doing the batch action.
-The main purpose of this method is to alter the query or the list of selected ids.
+In your admin class you can create a ``preBatchAction`` method to execute
+something before doing the batch action. The main purpose of this method
+is to alter the query or the list of selected ids.
 
 .. code-block:: php
 
@@ -252,5 +245,3 @@ The main purpose of this method is to alter the query or the list of selected id
 
         $query->setParameter('foo', $bar);
     }
-
-.. _Symfony bundle overriding mechanism: http://symfony.com/doc/current/cookbook/bundles/inheritance.html
diff --git a/docs/reference/breadcrumbs.rst b/docs/reference/breadcrumbs.rst
index 66954e9983..9c09bb0d6b 100644
--- a/docs/reference/breadcrumbs.rst
+++ b/docs/reference/breadcrumbs.rst
@@ -1,15 +1,18 @@
 The breadcrumbs builder
 =======================
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 The ``sonata.admin.breadcrumbs_builder`` service is used in the layout of every
 page to compute the underlying data for two breadcrumbs:
 
 * one as text, appearing in the ``title`` tag of the document's ``head`` tag;
 * the other as html, visible as an horizontal bar at the top of the page.
 
-Getting the breadcrumbs for a given action of a given admin is done like this:
-
-.. code-block:: php
+Getting the breadcrumbs for a given action of a given admin is done like this::
 
    <?php
    $this->get('sonata.admin.breadcrumbs_builder')->getBreadcrumbs($admin, $action);
@@ -20,7 +23,7 @@ Configuration
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             breadcrumbs:
diff --git a/docs/reference/child_admin.rst b/docs/reference/child_admin.rst
index c34080e08d..16450609c8 100644
--- a/docs/reference/child_admin.rst
+++ b/docs/reference/child_admin.rst
@@ -1,18 +1,25 @@
 Create child admins
 -------------------
 
-Let us say you have a ``PlaylistAdmin`` and a ``VideoAdmin``. You can optionally declare the ``VideoAdmin``
-to be a child of the ``PlaylistAdmin``. This will create new routes like, for example, ``/playlist/{id}/video/list``,
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
+Let us say you have a ``PlaylistAdmin`` and a ``VideoAdmin``. You can
+optionally declare the ``VideoAdmin`` to be a child of the ``PlaylistAdmin``.
+This will create new routes like, for example, ``/playlist/{id}/video/list``,
 where the videos will automatically be filtered by post.
 
-To do this, you first need to call the ``addChild`` method in your ``PlaylistAdmin`` service configuration:
+To do this, you first need to call the ``addChild`` method in your ``PlaylistAdmin``
+service configuration:
 
 .. configuration-block::
 
     .. code-block:: xml
 
         <!-- app/config/config.xml -->
-        <service id="sonata.admin.playlist" class="AppBundle\Admin\PlaylistAdmin">
+        <service id="sonata.admin.playlist" class="App\Admin\PlaylistAdmin">
             <!-- ... -->
 
             <call method="addChild">
@@ -26,7 +33,7 @@ Then, you have to set the VideoAdmin ``parentAssociationMapping`` attribute to `
 
     <?php
 
-    namespace AppBundle\Admin;
+    namespace App\Admin;
 
     // ...
 
@@ -42,13 +49,12 @@ Then, you have to set the VideoAdmin ``parentAssociationMapping`` attribute to `
         }
     }
 
-To display the ``VideoAdmin`` extend the menu in your ``PlaylistAdmin`` class:
-
-.. code-block:: php
+To display the ``VideoAdmin`` extend the menu in your ``PlaylistAdmin``
+class::
 
     <?php
 
-    namespace AppBundle\Admin;
+    namespace App\Admin;
 
     use Knp\Menu\ItemInterface as MenuItemInterface;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -85,15 +91,16 @@ To display the ``VideoAdmin`` extend the menu in your ``PlaylistAdmin`` class:
         }
     }
 
-It also possible to set a dot-separated value, like ``post.author``, if your parent and child admins are not directly related.
+It also possible to set a dot-separated value, like ``post.author``,
+if your parent and child admins are not directly related.
 
-Be wary that being a child admin is optional, which means that regular routes
-will be created regardless of whether you actually need them or not. To get rid
-of them, you may override the ``configureRoutes`` method::
+Be wary that being a child admin is optional, which means that regular
+routes will be created regardless of whether you actually need them
+or not. To get rid of them, you may override the ``configureRoutes`` method::
 
     <?php
 
-    namespace AppBundle\Admin;
+    namespace App\Admin;
 
     use Sonata\AdminBundle\Admin\AbstractAdmin;
     use Sonata\AdminBundle\Route\RouteCollection;
diff --git a/docs/reference/conditional_validation.rst b/docs/reference/conditional_validation.rst
index 623257aae7..41dd99a3eb 100644
--- a/docs/reference/conditional_validation.rst
+++ b/docs/reference/conditional_validation.rst
@@ -1,12 +1,13 @@
 Inline Validation
 =================
 
-The inline validation code is now part of the SonataCoreBundle. You can refer to the related documentation for more information.
+The inline validation code is now part of the SonataCoreBundle.
+You can refer to the related documentation for more information.
 
-The above examples show how the integration has been done with the SonataAdminBundle. For completeness, it's worth remembering that
-the ``Admin`` class itself contains an empty ``validate`` method. This is automatically called, so you can override it in your own admin class:
-
-.. code-block:: php
+The above examples show how the integration has been done with the SonataAdminBundle.
+For completeness, it's worth remembering that the ``Admin`` class itself contains an
+empty ``validate`` method. This is automatically called, so you can override
+it in your own admin class::
 
     // add this to your existing use statements
     use Sonata\CoreBundle\Validator\ErrorElement;
@@ -26,20 +27,17 @@ the ``Admin`` class itself contains an empty ``validate`` method. This is automa
 Troubleshooting
 ---------------
 
-Make sure your validator method is being called. If in doubt, try throwing an exception:
-
-.. code-block:: php
+Make sure your validator method is being called. If in doubt, try throwing
+an exception::
 
     public function validate(ErrorElement $errorElement, $object)
     {
         throw new \Exception(__METHOD__);
     }
 
-There should not be any validation_groups defined for the form. If you have code like the example below in
-your ``Admin`` class, remove the 'validation_groups' entry, the whole $formOptions property or set validation_groups
-to an empty array:
-
-.. code-block:: php
+There should not be any validation_groups defined for the form. If you have
+code like the example below in your ``Admin`` class, remove the 'validation_groups'
+entry, the whole $formOptions property or set validation_groups to an empty array::
 
     protected $formOptions = [
         'validation_groups' => []
diff --git a/docs/reference/configuration.rst b/docs/reference/configuration.rst
index db5a90b163..d9b6d6249b 100644
--- a/docs/reference/configuration.rst
+++ b/docs/reference/configuration.rst
@@ -16,7 +16,7 @@ Configuration options
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             security:
diff --git a/docs/reference/console.rst b/docs/reference/console.rst
index 466bcf15ed..2500f83651 100644
--- a/docs/reference/console.rst
+++ b/docs/reference/console.rst
@@ -20,7 +20,7 @@ Usage example:
 
 .. code-block:: bash
 
-    $ php app/console cache:create-cache-class
+    $ bin/console cache:create-cache-class
 
 sonata:admin:generate
 ---------------------
@@ -40,7 +40,7 @@ The command require the SensioGeneratorBundle_ to work. If you don't already hav
 ===============   ===============================================================================================================================
 Options           Description
 ===============   ===============================================================================================================================
- **bundle**       the bundle name (the default value is determined by the given model class, e.g. "AppBundle" or "YourNSFooBundle")
+ **bundle**       the bundle name (the default value is determined by the given model class, e.g. "App" or "YourNSFooBundle")
  **admin**        the admin class basename (by default this adds "Admin" to the model class name, e.g. "BarAdmin")
  **controller**   the controller class basename (by default this adds "AdminController" to the model class name, e.g. "BarAdminController")
  **manager**      the model manager type (by default this is the first registered model manager type, e.g. "orm")
@@ -52,7 +52,7 @@ Usage example:
 
 .. code-block:: bash
 
-    $ php app/console sonata:admin:generate AppBundle/Entity/Foo
+    $ bin/console sonata:admin:generate App/Entity/Foo
 
 sonata:admin:list
 -----------------
@@ -66,7 +66,7 @@ Usage example:
 
 .. code-block:: bash
 
-    $ php app/console sonata:admin:list
+    $ bin/console sonata:admin:list
 
 
 .. figure:: ../images/console_admin_list.png
@@ -86,7 +86,7 @@ Usage example:
 
 .. code-block:: bash
 
-    $ php app/console sonata:admin:explain sonata.news.admin.post
+    $ bin/console sonata:admin:explain sonata.news.admin.post
 
 .. figure:: ../images/console_admin_explain.png
    :align: center
@@ -108,7 +108,7 @@ Usage example:
 
 .. code-block:: bash
 
-    $ php app/console sonata:admin:setup-acl
+    $ bin/console sonata:admin:setup-acl
 
 sonata:admin:generate-object-acl
 --------------------------------
diff --git a/docs/reference/dashboard.rst b/docs/reference/dashboard.rst
index d17c7feda6..9122a0869d 100644
--- a/docs/reference/dashboard.rst
+++ b/docs/reference/dashboard.rst
@@ -1,6 +1,11 @@
 Dashboard
 =========
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 The Dashboard is the main landing page. By default it lists your mapped models,
 as defined by your ``Admin`` services. This is useful to help you start using
 ``SonataAdminBundle`` right away, but there is much more that you can do to take
@@ -9,13 +14,13 @@ advantage of the Dashboard.
 The Dashboard is, by default, available at ``/admin/dashboard``, which is handled by
 the ``SonataAdminBundle:Core:dashboard`` controller action. The default view file for
 this action is ``@SonataAdmin/Core/dashboard.html.twig``, but you can change
-this in your ``config.yml``:
+this in your admin configuration:
 
 .. configuration-block::
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             templates:
@@ -65,12 +70,12 @@ services:
 
     .. code-block:: xml
 
-        <service id="app.admin.post" class="AppBundle\Admin\PostAdmin">
+        <service id="app.admin.post" class="App\Admin\PostAdmin">
               <tag name="sonata.admin" manager_type="orm"
                   group="Content"
                   label="Post" />
               <argument />
-              <argument>AppBundle\Entity\Post</argument>
+              <argument>App\Entity\Post</argument>
               <argument />
           </service>
 
@@ -78,7 +83,7 @@ services:
 
         services:
             app.admin.post:
-                class: AppBundle\Admin\PostAdmin
+                class: App\Admin\PostAdmin
                 tags:
                     - name: sonata.admin
                       manager_type: orm
@@ -86,7 +91,7 @@ services:
                       label: "Post"
                 arguments:
                     - ~
-                    - AppBundle\Entity\Post
+                    - App\Entity\Post
                     - ~
                 public: true
 
@@ -97,12 +102,12 @@ service belongs to the ``Content`` group.
 
     .. code-block:: xml
 
-        <service id="app.admin.post" class="AppBundle\Admin\PostAdmin">
+        <service id="app.admin.post" class="App\Admin\PostAdmin">
               <tag name="sonata.admin" manager_type="orm"
                   group="app.admin.group.content"
-                  label="app.admin.model.post" label_catalogue="AppBundle" />
+                  label="app.admin.model.post" label_catalogue="App" />
               <argument />
-              <argument>AppBundle\Entity\Post</argument>
+              <argument>App\Entity\Post</argument>
               <argument />
           </service>
 
@@ -110,19 +115,19 @@ service belongs to the ``Content`` group.
 
         services:
             app.admin.post:
-                class: AppBundle\Admin\PostAdmin
+                class: App\Admin\PostAdmin
                 tags:
                     - name: sonata.admin
                       manager_type: orm
                       group: "app.admin.group.content"
                       label: "app.admin.model.post"
-                      label_catalogue: "AppBundle"
+                      label_catalogue: "App"
                 arguments:
                     - ~
-                    - AppBundle\Entity\Post
+                    - App\Entity\Post
                     - ~
 
-In this example, the labels are translated by ``AppBundle``, using the given
+In this example, the labels are translated by ``App``, using the given
 ``label_catalogue``. So, you can use the above examples to support multiple languages
 in your project.
 
@@ -142,14 +147,14 @@ declarations.
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             dashboard:
                 groups:
                     app.admin.group.content:
                         label: app.admin.group.content
-                        label_catalogue: AppBundle
+                        label_catalogue: App
                         items:
                             - app.admin.post
 
@@ -168,7 +173,7 @@ declarations.
     either leave out that key or use the ``~`` value for that option.
 
 This configuration specifies that the ``app.admin.group.content`` group uses the
-``app.admin.group.content`` label, which is translated using the ``AppBundle``
+``app.admin.group.content`` label, which is translated using the ``App``
 translation catalogue (the same label and translation configuration that we declared
 previously, in the service definition example).
 
@@ -208,7 +213,7 @@ a text block and RSS feed block on the right. The configuration for this scenari
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             dashboard:
@@ -255,7 +260,7 @@ suit this scenario.
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             dashboard:
@@ -347,7 +352,7 @@ On ``top`` and ``bottom`` positions, you can also specify an optional ``class``
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             dashboard:
@@ -365,12 +370,10 @@ Configuring what actions are available for each item on the dashboard
 By default. A "list" and a "create" option are available for each item on the
 dashboard. If you created a custom action and want to display it along the
 other two on the dashboard, you can do so by overriding the
-``getDashboardActions()`` method of your admin class:
-
-.. code-block:: php
+``getDashboardActions()`` method of your admin class::
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     class PostAdmin extends AbstractAdmin
     {
@@ -393,12 +396,10 @@ other two on the dashboard, you can do so by overriding the
 
     }
 
-You can also hide an action from the dashboard by unsetting it:
-
-.. code-block:: php
+You can also hide an action from the dashboard by unsetting it::
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     class PostAdmin extends AbstractAdmin
     {
diff --git a/docs/reference/extensions.rst b/docs/reference/extensions.rst
index 1c33569f5d..1eb30b848f 100644
--- a/docs/reference/extensions.rst
+++ b/docs/reference/extensions.rst
@@ -1,10 +1,17 @@
 Extensions
 ==========
 
-Admin extensions allow you to add or change features of one or more Admin instances. To create an extension your class
-must implement the interface ``Sonata\AdminBundle\Admin\AdminExtensionInterface`` and be registered as a service. The
-interface defines a number of functions which you can use to customize the edit form, list view, form validation,
-alter newly created objects and other admin features.
+Admin extensions allow you to add or change features of one or more Admin
+instances. To create an extension your class
+must implement the interface ``Sonata\AdminBundle\Admin\AdminExtensionInterface``
+and be registered as a service. The interface defines a number of functions which
+you can use to customize the edit form, list view, form validation, alter newly
+created objects and other admin features.
+
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
 
 .. code-block:: php
 
@@ -45,18 +52,18 @@ The higher the priority, the earlier it's executed.
 
         services:
             app.publish.extension:
-                class: AppBundle\Admin\Extension\PublishStatusAdminExtension
+                class: App\Admin\Extension\PublishStatusAdminExtension
                 tags:
                     - { name: sonata.admin.extension, target: app.admin.article }
                     - { name: sonata.admin.extension, target: app.admin.blog }
 
             app.order.extension:
-                class: AppBundle\Admin\Extension\OrderAdminExtension
+                class: App\Admin\Extension\OrderAdminExtension
                 tags:
                     - { name: sonata.admin.extension, global: true }
 
             app.important.extension:
-                class: AppBundle\Admin\Extension\ImportantAdminExtension
+                class: App\Admin\Extension\ImportantAdminExtension
                 tags:
                     - { name: sonata.admin.extension, priority: 5 }
 
@@ -66,7 +73,7 @@ The second option is to add it to your config.yml file.
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             extensions:
@@ -109,7 +116,7 @@ priority:
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             extensions:
@@ -117,13 +124,13 @@ priority:
                     admins:
                         - app.admin.article
                     implements:
-                        - AppBundle\Publish\PublishStatusInterface
+                        - App\Publish\PublishStatusInterface
                     excludes:
                         - app.admin.blog
                         - app.admin.news
                     extends:
-                        - AppBundle\Document\Blog
+                        - App\Document\Blog
                     instanceof:
-                        -  AppBundle\Document\Page
+                        -  App\Document\Page
                     uses:
-                        -  AppBundle\Trait\Timestampable
+                        -  App\Trait\Timestampable
diff --git a/docs/reference/field_types.rst b/docs/reference/field_types.rst
index 04c5affb45..10aa85fd96 100644
--- a/docs/reference/field_types.rst
+++ b/docs/reference/field_types.rst
@@ -69,7 +69,7 @@ Choice
 
     public function configureListFields(ListMapper $listMapper)
     {
-        // For the value `prog`, the displayed text is `In progress`. The `AppBundle` catalogue will be used to translate `In progress` message.
+        // For the value `prog`, the displayed text is `In progress`. The `App` catalogue will be used to translate `In progress` message.
         $listMapper
             ->add('status', 'choice', [
                 'choices' => [
@@ -77,7 +77,7 @@ Choice
                     'prog' => 'In progress',
                     'done' => 'Done'
                 ],
-                'catalogue' => 'AppBundle'
+                'catalogue' => 'App'
             ])
         ;
     }
diff --git a/docs/reference/form_help_message.rst b/docs/reference/form_help_message.rst
index 4cef680a32..f213497fcc 100644
--- a/docs/reference/form_help_message.rst
+++ b/docs/reference/form_help_message.rst
@@ -1,10 +1,18 @@
 Form Help Messages and Descriptions
 ===================================
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 Help Messages
 -------------
 
-Help messages are short notes that are rendered together with form fields. They are generally used to show additional information so the user can complete the form element faster and more accurately. The text is not escaped, so HTML can be used.
+Help messages are short notes that are rendered together with form fields.
+They are generally used to show additional information so the user can complete
+the form element faster and more accurately. The text is not escaped,
+so HTML can be used.
 
 Example
 ^^^^^^^
@@ -12,7 +20,7 @@ Example
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     class PostAdmin extends AbstractAdmin
     {
@@ -34,12 +42,10 @@ Example
 Alternative Ways To Define Help Messages
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-All at once
-
-.. code-block:: php
+All at once::
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     class PostAdmin extends AbstractAdmin
     {
@@ -58,12 +64,10 @@ All at once
         }
     }
 
-or step by step.
-
-.. code-block:: php
+or step by step::
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     class PostAdmin extends AbstractAdmin
     {
@@ -87,7 +91,7 @@ This Extension for example adds a note field to some entities which use a custom
 
     <?php
 
-    namespace AppBundle\Admin\Extension;
+    namespace App\Admin\Extension;
 
     use Sonata\AdminBundle\Admin\AbstractAdminExtension;
     use Sonata\AdminBundle\Datagrid\DatagridMapper;
@@ -142,7 +146,7 @@ Help messages in a sub-field
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     use Sonata\CoreBundle\Form\Type\ImmutableArrayType;
     use Symfony\Component\Form\Extension\Core\Type\TextareaType;
@@ -176,7 +180,9 @@ use help messages to display an image tag.
 Form Group Descriptions
 -----------------------
 
-A form group description is a block of text rendered below the group title. These can be used to describe a section of a form. The text is not escaped, so HTML can be used.
+A form group description is a block of text rendered below the group title.
+These can be used to describe a section of a form. The text is not escaped,
+so HTML can be used.
 
 Example
 ^^^^^^^
@@ -184,7 +190,7 @@ Example
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     class PostAdmin extends AbstractAdmin
     {
diff --git a/docs/reference/form_types.rst b/docs/reference/form_types.rst
index 17b3f77539..07b1edc221 100644
--- a/docs/reference/form_types.rst
+++ b/docs/reference/form_types.rst
@@ -1,6 +1,11 @@
 Form Types
 ==========
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 Admin related form types
 ------------------------
 
@@ -25,7 +30,7 @@ All we need to do now is add a reference for this field in our ``PageAdmin`` cla
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PageAdmin.php
+    // src/Admin/PageAdmin.php
 
     use Sonata\AdminBundle\Form\FormMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -132,7 +137,7 @@ All we need to do now is add a reference for this field in our ``PageAdmin`` cla
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PageAdmin.php
+    // src/Admin/PageAdmin.php
 
     use Sonata\AdminBundle\Form\Type\ModelListType;
     use Sonata\AdminBundle\Form\FormMapper;
@@ -175,7 +180,7 @@ The value of hidden field is identifier of related entity.
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PageAdmin.php
+    // src/Admin/PageAdmin.php
 
     use Sonata\AdminBundle\Form\FormMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -223,7 +228,7 @@ datagrid filter for the property ``title``.
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/ArticleAdmin.php
+    // src/Admin/ArticleAdmin.php
 
     use Sonata\AdminBundle\Form\FormMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -246,7 +251,7 @@ datagrid filter for the property ``title``.
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/CategoryAdmin.php
+    // src/Admin/CategoryAdmin.php
 
     use Sonata\AdminBundle\Datagrid\DatagridMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -383,7 +388,7 @@ The available options are:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/ArticleAdmin.php
+    // src/Admin/ArticleAdmin.php
 
     use Sonata\AdminBundle\Form\FormMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -404,7 +409,7 @@ The available options are:
 
 .. code-block:: jinja
 
-    {# src/AppBundle/Resources/views/Form/Type/sonata_type_model_autocomplete.html.twig #}
+    {# templates/Form/Type/sonata_type_model_autocomplete.html.twig #}
 
     {% extends '@SonataAdmin/Form/Type/sonata_type_model_autocomplete.html.twig' %}
 
@@ -425,7 +430,7 @@ The available options are:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/ArticleAdmin.php
+    // src/Admin/ArticleAdmin.php
 
     use Sonata\AdminBundle\Form\FormMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -449,7 +454,7 @@ The available options are:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/CategoryAdmin.php
+    // src/Admin/CategoryAdmin.php
 
     use Sonata\AdminBundle\Datagrid\DatagridMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -478,7 +483,7 @@ According the choice made only associated fields are displayed. The others field
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/AppMenuAdmin.php
+    // src/Admin/AppMenuAdmin.php
 
     use Sonata\AdminBundle\Form\FormMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -538,19 +543,19 @@ that looks like this:
 
     .. code-block:: yaml
 
-        # src/AppBundle/Resources/config/admin.yml
+        # src/Resources/config/admin.yml
 
         services:
             app.admin.image:
-                class: AppBundle\Admin\ImageAdmin
+                class: App\Admin\ImageAdmin
                 tags:
                     - { name: sonata.admin, manager_type: orm, label: "Image" }
                 arguments:
                     - ~
-                    - AppBundle\Entity\Image
+                    - App\Entity\Image
                     - 'SonataAdminBundle:CRUD'
                 calls:
-                    - [ setTranslationDomain, [AppBundle]]
+                    - [ setTranslationDomain, [App]]
                 public: true
 
 .. note::
@@ -563,7 +568,7 @@ for the ``image1`` field to ``sonata_type_admin`` in our ``PageAdmin`` class:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PageAdmin.php
+    // src/Admin/PageAdmin.php
 
     use Sonata\AdminBundle\Form\FormMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -607,7 +612,7 @@ to the underlying forms.
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/ProductAdmin.php
+    // src/Admin/ProductAdmin.php
 
     use Sonata\AdminBundle\Form\FormMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -705,7 +710,7 @@ example above:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PageAdmin.php
+    // src/Admin/PageAdmin.php
 
     use Sonata\AdminBundle\Form\FormMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -740,7 +745,7 @@ Given you have a ``PostType`` like this:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Form/PostType.php
+    // src/Form/PostType.php
 
     use Symfony\Component\Form\FormBuilderInterface;
     use Symfony\Bridge\Doctrine\Form\Type\EntityType;
@@ -767,11 +772,11 @@ you can reuse it like this:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/Post.php
+    // src/Admin/Post.php
 
     use Sonata\AdminBundle\Form\FormMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
-    use AppBundle\Form\PostType;
+    use App\Form\PostType;
 
     class Post extend AbstractAdmin
     {
@@ -803,7 +808,7 @@ General
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PageAdmin.php
+    // src/Admin/PageAdmin.php
 
     use Sonata\AdminBundle\Form\FormMapper;
     use Sonata\AdminBundle\Admin\AbstractAdmin;
@@ -832,7 +837,7 @@ General
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PageAdmin.php
+    // src/Admin/PageAdmin.php
 
     use Sonata\AdminBundle\Form\FormMapper;
     use Symfony\Component\Form\Extension\Core\Type\ChoiceType;
diff --git a/docs/reference/preview_mode.rst b/docs/reference/preview_mode.rst
index c666a288e1..e1adcb7a4c 100644
--- a/docs/reference/preview_mode.rst
+++ b/docs/reference/preview_mode.rst
@@ -6,10 +6,15 @@ Preview Mode is an optional view of an object before it is persisted or updated.
 The preview step can be enabled for an admin entity by overriding the public property
 ``$supportsPreviewMode`` and setting it to true.
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 .. code-block:: php
 
     <?php
-    // src/AppBundle/AdminPostAdmin.php
+    // src/AdminPostAdmin.php
 
     class PostAdmin extends AbstractAdmin
     {
@@ -49,19 +54,17 @@ globally through the template configuration for the key 'preview':
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             templates:
                 preview:  "@App/CRUD/preview.html.twig"
 
-Or per admin entity by overriding the ``getTemplate($name)`` and returning the appropriate template when the key
-matches 'preview':
-
-.. code-block:: php
+Or per admin entity by overriding the ``getTemplate($name)`` and returning
+the appropriate template when the key matches 'preview'::
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     // ...
 
diff --git a/docs/reference/routing.rst b/docs/reference/routing.rst
index 360b7b07e3..24e627916f 100644
--- a/docs/reference/routing.rst
+++ b/docs/reference/routing.rst
@@ -1,6 +1,11 @@
 Routing
 =======
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 The default routes used in the CRUD controller are accessible through the
 ``Admin`` class.
 
@@ -26,7 +31,7 @@ be added to generate the actual route names.
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     class PostAdmin extends AbstractAdmin
     {
@@ -46,9 +51,8 @@ route names for your actions like 'admin_vendor_bundlename_entityname_list'.
 If the Admin fails to find a baseRouteName for your Admin class a ``RuntimeException``
 will be thrown with a related message.
 
-If the admin class is a child of another admin class the route name will be prefixed by the parent route name, example :
-
-.. code-block:: php
+If the admin class is a child of another admin class the route name will
+be prefixed by the parent route name, example::
 
     <?php
     // The parent admin class
@@ -77,12 +81,10 @@ You can use ``baseRoutePattern`` to set a custom URL for a given ``Admin`` class
 
 For example, to use ``http://yourdomain.com/admin/foo`` as the base URL for
 the ``FooAdmin`` class (instead of the default of ``http://yourdomain.com/admin/vendor/bundle/foo``)
-use the following code:
-
-.. code-block:: php
+use the following code::
 
     <?php
-    // src/AppBundle/Admin/FooAdmin.php
+    // src/Admin/FooAdmin.php
 
     class FooAdmin extends AbstractAdmin
     {
@@ -92,9 +94,8 @@ use the following code:
 You will then have route URLs like ``http://yourdomain.com/admin/foo/list`` and
 ``http://yourdomain.com/admin/foo/1/edit``
 
-If the admin class is a child of another admin class the route pattern will be prefixed by the parent route pattern, example :
-
-.. code-block:: php
+If the admin class is a child of another admin class the route pattern will
+be prefixed by the parent route pattern, example::
 
     <?php
     // The parent admin class
@@ -151,7 +152,7 @@ explicitly this defaults to the action name.
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/MediaAdmin.php
+    // src/Admin/MediaAdmin.php
 
     use Sonata\AdminBundle\Route\RouteCollection;
 
@@ -173,7 +174,7 @@ in the ``add`` method to set additional settings like this:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/MediaAdmin.php
+    // src/Admin/MediaAdmin.php
 
     use Sonata\AdminBundle\Route\RouteCollection;
 
@@ -193,32 +194,31 @@ handler for it in your Controller. By default Admin classes use ``SonataAdminBun
 as their controller, but this can be changed by altering the third argument when defining
 your Admin service (in your admin.yml file).
 
-For example, lets change the Controller for our MediaAdmin class to AppBundle:MediaCRUD:
+For example, lets change the Controller for our MediaAdmin class to App:MediaCRUD:
 
 .. configuration-block::
 
     .. code-block:: yaml
 
-        # src/AppBundle/Resources/config/admin.yml
+        # src/Resources/config/admin.yml
 
         app.admin.media:
-            class: AppBundle\Admin\MediaAdmin
+            class: App\Admin\MediaAdmin
             tags:
                 - { name: sonata.admin, manager_type: orm, label: "Media" }
             arguments:
                 - ~
-                - AppBundle\Entity\Page
-                - 'AppBundle:MediaCRUD' # define the new controller via the third argument
+                - App\Entity\Page
+                - App\Controller\MediaCRUDController # define the new controller via the third argument
             public: true
 
-We now need to create our Controller, the easiest way is to extend the basic Sonata CRUD controller:
-
-.. code-block:: php
+We now need to create our Controller, the easiest way is to extend the
+basic Sonata CRUD controller::
 
     <?php
-    // src/AppBundle/Controller/MediaCRUDController.php
+    // src/Controller/MediaCRUDController.php
 
-    namespace AppBundle\Controller;
+    namespace App\Controller;
 
     use Sonata\AdminBundle\Controller\CRUDController;
 
@@ -248,13 +248,13 @@ You can view all of the current routes defined for an Admin class by using the c
 
 .. code-block:: bash
 
- $ php app/console sonata:admin:explain <<admin.service.name>>
+ $ bin/console sonata:admin:explain <<admin.service.name>>
 
 for example if your Admin is called sonata.admin.foo you would run
 
 .. code-block:: bash
 
-    $ php app/console sonata:admin:explain app.admin.foo
+    $ bin/console sonata:admin:explain app.admin.foo
 
 Sonata internally checks for the existence of a route before linking to it. As a result, removing a
 route will prevent links to that action from appearing in the administrative interface. For example,
@@ -263,12 +263,10 @@ removing the 'create' route will prevent any links to "Add new" from appearing.
 Removing a single route
 ^^^^^^^^^^^^^^^^^^^^^^^
 
-Any single registered route can be easily removed by name:
-
-.. code-block:: php
+Any single registered route can be easily removed by name::
 
     <?php
-    // src/AppBundle/Admin/MediaAdmin.php
+    // src/Admin/MediaAdmin.php
 
     use Sonata\AdminBundle\Route\RouteCollection;
 
@@ -290,7 +288,7 @@ the ``clearExcept()`` method. This method accepts an array of routes you want to
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/MediaAdmin.php
+    // src/Admin/MediaAdmin.php
 
     use Sonata\AdminBundle\Route\RouteCollection;
 
@@ -313,7 +311,7 @@ If you want to remove all default routes, you can use ``clear()`` method.
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/MediaAdmin.php
+    // src/Admin/MediaAdmin.php
 
     use Sonata\AdminBundle\Route\RouteCollection;
 
@@ -336,7 +334,7 @@ can use ``hasParentFieldDescription()`` to detect this case and remove the route
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/TagAdmin.php
+    // src/Admin/TagAdmin.php
 
     use Sonata\AdminBundle\Route\RouteCollection;
 
@@ -362,7 +360,7 @@ method. This method will be used when a link is being generated.
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Admin/MediaAdmin.php
+    // src/Admin/MediaAdmin.php
 
     class MediaAdmin extends AbstractAdmin
     {
@@ -379,19 +377,18 @@ method. This method will be used when a link is being generated.
         }
     }
 
-If you then call ``$admin->generateUrl('create')`` somewhere, the generated URL looks like this: ``/admin/module/create?context=default``
+If you then call ``$admin->generateUrl('create')`` somewhere, the generated
+URL looks like this: ``/admin/module/create?context=default``
 
 Changing the default route in a List Action
 -------------------------------------------
 
 Usually the identifier column of a list action links to the edit screen. To change the
 list action's links to point to a different action, set the ``route`` option in your call to
-``ListMapper::addIdentifier()``. For example, to link to show instead of edit:
-
-.. code-block:: php
+``ListMapper::addIdentifier()``. For example, to link to show instead of edit::
 
     <?php
-    // src/AppBundle/Admin/PostAdmin.php
+    // src/Admin/PostAdmin.php
 
     class PostAdmin extends AbstractAdmin
     {
diff --git a/docs/reference/saving_hooks.rst b/docs/reference/saving_hooks.rst
index 43824a4679..4bc99ee8ae 100644
--- a/docs/reference/saving_hooks.rst
+++ b/docs/reference/saving_hooks.rst
@@ -45,6 +45,8 @@ solve the issue by using the ``preUpdate`` saving hook.
 
     use Sonata\AdminBundle\Admin\AbstractAdmin;
     use FOS\UserBundle\Model\UserManagerInterface;
+    use Sonata\AdminBundle\Form\Type\ModelType;
+    use Sonata\UserBundle\Form\Type\SecurityRolesType;
 
     class UserAdmin extends AbstractAdmin
     {
@@ -57,10 +59,10 @@ solve the issue by using the ``preUpdate`` saving hook.
                     ->add('plainPassword', 'text')
                 ->end()
                 ->with('Groups')
-                    ->add('groups', 'sonata_type_model', ['required' => false])
+                    ->add('groups', ModelType::class, ['required' => false])
                 ->end()
                 ->with('Management')
-                    ->add('roles', 'sonata_security_roles', ['multiple' => true])
+                    ->add('roles', SecurityRolesType::class, ['multiple' => true])
                     ->add('locked', null, ['required' => false])
                     ->add('expired', null, ['required' => false])
                     ->add('enabled', null, ['required' => false])
diff --git a/docs/reference/security.rst b/docs/reference/security.rst
index 9c0281efad..bb55be6dbe 100644
--- a/docs/reference/security.rst
+++ b/docs/reference/security.rst
@@ -1,6 +1,11 @@
 Security
 ========
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 User management
 ---------------
 
@@ -59,7 +64,7 @@ Using roles:
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             security:
@@ -74,7 +79,7 @@ Using ACL:
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             security:
@@ -132,14 +137,14 @@ service), Sonata will check if the user has the ``ROLE_APP_ADMIN_FOO_EDIT`` or `
 
 .. note::
 
-    Declaring the same admin as `AppBundle\Admin\FooAdmin` results in
+    Declaring the same admin as `App\Admin\FooAdmin` results in
     ``ROLE_APPBUNDLE\ADMIN\FOOADMIN_EDIT`` and ``ROLE_APPBUNDLE\ADMIN\FOOADMIN_ALL``!
 
 The role name will be based on the name of your admin service.
 ========================   ======================================================
 app.admin.foo              ROLE_APP_ADMIN_FOO_{PERMISSION}
 my.blog.admin.foo_bar      ROLE_MY_BLOG_ADMIN_FOO_BAR_{PERMISSION}
-AppBundle\Admin\FooAdmin   ROLE_APPBUNDLE\ADMIN\FOOADMIN_{PERMISSION}
+App\Admin\FooAdmin   ROLE_APPBUNDLE\ADMIN\FOOADMIN_{PERMISSION}
 ========================   ======================================================
 
 .. note::
@@ -152,7 +157,7 @@ So our ``security.yml`` file may look something like this:
 
     .. code-block:: yaml
 
-        # app/config/security.yml
+        # config/packages/security.yaml
 
         security:
             # ...
@@ -189,9 +194,7 @@ in the Symfony documentation.
 Usage
 ~~~~~
 
-You can now test if a user is authorized from an Admin class:
-
-.. code-block:: php
+You can now test if a user is authorized from an Admin class::
 
     if ($this->hasAccess('list')) {
         // ...
@@ -239,7 +242,7 @@ Then declare your handler as a service:
 
     .. code-block:: xml
 
-        <service id="app.security.handler.role" class="AppBundle\Security\Handler\RoleSecurityHandler" public="false">
+        <service id="app.security.handler.role" class="App\Security\Handler\RoleSecurityHandler" public="false">
             <argument type="service" id="security.context" on-invalid="null" />
             <argument type="collection">
                 <argument>ROLE_SUPER_ADMIN</argument>
@@ -252,7 +255,7 @@ And specify it as Sonata security handler on your configuration:
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             security:
@@ -284,9 +287,9 @@ User class (in a custom UserBundle). Do it as follows:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Entity/User.php
+    // src/Entity/User.php
 
-    namespace AppBundle\Entity;
+    namespace App\Entity;
 
     use Sonata\UserBundle\Entity\BaseUser as BaseUser;
     use Doctrine\ORM\Mapping as ORM;
@@ -311,18 +314,18 @@ User class (in a custom UserBundle). Do it as follows:
         }
     }
 
-In your ``app/config/config.yml`` you then need to put the following:
+In your ``config/packages/fos_user.yaml`` you then need to put the following:
 
 .. configuration-block::
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/fos_user.yaml
 
         fos_user:
             db_driver: orm
             firewall_name: main
-            user_class: AppBundle\Entity\User
+            user_class: App\Entity\User
 
 The following configuration for the SonataUserBundle defines:
 
@@ -337,31 +340,24 @@ The following configuration for the SonataUserBundle defines:
 
     .. code-block:: yaml
 
-        # src/AppBundle/Resources/config/services.yml
+        # config/services.yaml
 
-        # Symfony >= 3
         services:
             security.acl.permission.map:
               class: Sonata\AdminBundle\Security\Acl\Permission\AdminPermissionMap
 
-            # optionally use a custom MaskBuilder
-            #sonata.admin.security.mask.builder:
-            #  class: Sonata\AdminBundle\Security\Acl\Permission\MaskBuilder
-
-        # Symfony < 3
+        # optionally use a custom MaskBuilder
         parameters:
-            security.acl.permission.map.class: Sonata\AdminBundle\Security\Acl\Permission\AdminPermissionMap
+            sonata.admin.security.mask.builder.class: Sonata\AdminBundle\Security\Acl\Permission\MaskBuilder
 
-            # optionally use a custom MaskBuilder
-            #sonata.admin.security.mask.builder.class: Sonata\AdminBundle\Security\Acl\Permission\MaskBuilder
 
-In ``app/config/security.yml``:
+In ``config/packages/security.yaml``:
 
 .. configuration-block::
 
     .. code-block:: yaml
 
-        # app/config/security.yml
+        # config/packages/security.yaml
 
         security:
             providers:
@@ -416,13 +412,13 @@ In ``app/config/security.yml``:
             acl:
                 connection: default
 
-- Install the ACL tables ``php app/console init:acl``
+- Install the ACL tables ``bin/console init:acl``
 
 - Create a new root user:
 
 .. code-block:: bash
 
-    $ php app/console fos:user:create --super-admin
+    $ bin/console fos:user:create --super-admin
         Please choose a username:root
         Please choose an email:root@domain.com
         Please choose a password:root
@@ -432,7 +428,7 @@ If you have Admin classes, you can install or update the related CRUD ACL rules:
 
 .. code-block:: bash
 
-    $ php app/console sonata:admin:setup-acl
+    $ bin/console sonata:admin:setup-acl
     Starting ACL AdminBundle configuration
     > install ACL for sonata.media.admin.media
        - add role: ROLE_SONATA_MEDIA_ADMIN_MEDIA_GUEST, permissions: ["VIEW","LIST"]
@@ -446,7 +442,7 @@ object of an admin:
 
 .. code-block:: bash
 
-    $ php app/console sonata:admin:generate-object-acl
+    $ bin/console sonata:admin:generate-object-acl
 
 Optionally, you can specify an object owner, and step through each admin. See
 the help of the command for more information.
@@ -552,9 +548,9 @@ because for example you want to restrict access using extra rules:
 .. code-block:: php
 
     <?php
-    // src/AppBundle/Security/Authorization/Voter/UserAclVoter.php
+    // src/Security/Authorization/Voter/UserAclVoter.php
 
-    namespace AppBundle\Security\Authorization\Voter;
+    namespace App\Security\Authorization\Voter;
 
     use FOS\UserBundle\Model\UserInterface;
     use Symfony\Component\Security\Core\Authentication\Token\TokenInterface;
@@ -608,11 +604,11 @@ because for example you want to restrict access using extra rules:
 
     .. code-block:: xml
 
-        <!-- src/AppBundle/Resources/config/services.xml -->
+        <!-- src/Resources/config/services.xml -->
 
-        <!-- <service id="security.acl.user_permission.map" class="AppBundle\Security\Acl\Permission\UserAdminPermissionMap" public="false"></service> -->
+        <!-- <service id="security.acl.user_permission.map" class="App\Security\Acl\Permission\UserAdminPermissionMap" public="false"></service> -->
 
-        <service id="security.acl.voter.user_permissions" class="AppBundle\Security\Authorization\Voter\UserAclVoter" public="false">
+        <service id="security.acl.voter.user_permissions" class="App\Security\Authorization\Voter\UserAclVoter" public="false">
             <tag name="monolog.logger" channel="security" />
             <argument type="service" id="security.acl.provider" />
             <argument type="service" id="security.acl.object_identity_retrieval_strategy" />
@@ -628,7 +624,7 @@ because for example you want to restrict access using extra rules:
 
     .. code-block:: yaml
 
-        # app/config/security.yml
+        # config/packages/security.yaml
 
         security:
             access_decision_manager:
@@ -657,7 +653,7 @@ Usage
 ~~~~~
 
 Every time you create a new ``Admin`` class, you should start with the command
-``php app/console sonata:admin:setup-acl`` so the ACL database will be updated
+``bin/console sonata:admin:setup-acl`` so the ACL database will be updated
 with the latest roles and permissions.
 
 In the templates, or in your code, you can use the Admin method ``hasAccess()``:
@@ -775,7 +771,7 @@ service to use when retrieving your users.
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             security:
diff --git a/docs/reference/templates.rst b/docs/reference/templates.rst
index 2888d513f7..5897a84aa0 100644
--- a/docs/reference/templates.rst
+++ b/docs/reference/templates.rst
@@ -1,6 +1,11 @@
 Templates
 =========
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 ``SonataAdminBundle`` comes with a significant amount of ``twig`` files used to display the
 different parts of each ``Admin`` action's page. If you read the ``Templates`` part of the
 :doc:`architecture` section of this guide, you should know by now how these are organized in
@@ -108,7 +113,7 @@ You can specify your templates in the config.yml file, like so:
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # config/packages/sonata_admin.yaml
 
         sonata_admin:
             templates:
@@ -159,10 +164,10 @@ specify the templates to use in the ``Admin`` service definition:
 
     .. code-block:: xml
 
-        <service id="app.admin.post" class="AppBundle\Admin\PostAdmin">
+        <service id="app.admin.post" class="App\Admin\PostAdmin">
             <tag name="sonata.admin" manager_type="orm" group="Content" label="Post" />
             <argument />
-            <argument>AppBundle\Entity\Post</argument>
+            <argument>App\Entity\Post</argument>
             <argument />
             <call method="setTemplate">
                 <argument>edit</argument>
@@ -174,12 +179,12 @@ specify the templates to use in the ``Admin`` service definition:
 
         services:
             app.admin.post:
-                class: AppBundle\Admin\PostAdmin
+                class: App\Admin\PostAdmin
                 tags:
                     - { name: sonata.admin, manager_type: orm, group: "Content", label: "Post" }
                 arguments:
                     - ~
-                    - AppBundle\Entity\Post
+                    - App\Entity\Post
                     - ~
                 calls:
                     - [ setTemplate, [edit, "@App/PostAdmin/edit.html.twig"]]
@@ -215,4 +220,4 @@ function to access the templates of the current Admin, or the
 
     {% block field %}
         {# ... #}
-    {% endblock %}
\ No newline at end of file
+    {% endblock %}
diff --git a/docs/reference/translation.rst b/docs/reference/translation.rst
index 0f1ae22c5a..55fb2319ba 100644
--- a/docs/reference/translation.rst
+++ b/docs/reference/translation.rst
@@ -1,6 +1,11 @@
 Translation
 ===========
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 There are two main catalogue names in an Admin class:
 
 * ``SonataAdminBundle``: this catalogue is used to translate shared messages
@@ -76,29 +81,30 @@ Overriding the translation domain is of particular use when using
 :doc:`extensions`, where the extension and the translations would
 be defined in one bundle, but implemented in many different Admin instances.
 
-Setting the translation domain on an individual field:
+Setting the translation domain on an individual field::
 
-.. code-block:: php
+    use Symfony\Component\Form\Extension\Core\Type\CheckboxType;
 
     $formMapper
         ->with('form.my_group')
-            ->add('publishable', 'checkbox', [], [
+            ->add('publishable', CheckboxType::class, [], [
                 'translation_domain' => 'MyTranslationDomain',
             ])
         ->end()
     ;
 
 The following example sets the default translation domain on a form group and
-over-rides that setting for one of the fields:
+over-rides that setting for one of the fields::
 
-.. code-block:: php
+    use Symfony\Component\Form\Extension\Core\Type\CheckboxType;
+    use Symfony\Component\Form\Extension\Core\Type\DateType;
 
     $formMapper
         ->with('form.my_group', ['translation_domain' => 'MyDomain'])
-            ->add('publishable', 'checkbox', [], [
+            ->add('publishable', CheckboxType::class, [], [
                 'translation_domain' => 'AnotherDomain',
             ])
-            ->add('start_date', 'date', [], [])
+            ->add('start_date', DateType::class, [], [])
         ->end()
     ;
 
@@ -109,9 +115,7 @@ Setting the label name
 ^^^^^^^^^^^^^^^^^^^^^^
 
 By default, the label is set to a sanitized version of the field name. A custom
-label can be defined as the third argument of the ``add`` method:
-
-.. code-block:: php
+label can be defined as the third argument of the ``add`` method::
 
     class PageAdmin extends AbstractAdmin
     {
@@ -161,7 +165,7 @@ the Container:
 
     .. code-block:: xml
 
-        <service id="app.admin.project" class="AppBundle\Admin\ProjectAdmin">
+        <service id="app.admin.project" class="App\Admin\ProjectAdmin">
             <tag
                 name="sonata.admin"
                 manager_type="orm"
@@ -170,7 +174,7 @@ the Container:
                 label_translator_strategy="sonata.admin.label.strategy.native"
              />
             <argument />
-            <argument>AppBundle\Entity\Project</argument>
+            <argument>App\Entity\Project</argument>
             <argument />
         </service>
 
diff --git a/docs/reference/troubleshooting.rst b/docs/reference/troubleshooting.rst
index 45f1875b66..3e5ea1397d 100644
--- a/docs/reference/troubleshooting.rst
+++ b/docs/reference/troubleshooting.rst
@@ -1,18 +1,21 @@
 Troubleshooting
 ===============
 
+.. note::
+    This article assumes you are using Symfony 4. Using Symfony 2.8 or 3
+    will require to slightly modify some namespaces and paths when creating
+    entities and admins.
+
 The toString method
 -------------------
 
 Sometimes the bundle needs to display your model objects, in order to do it,
 objects are converted to string by using the `__toString`_ magic method.
 Take care to never return anything else than a string in this method.
-For example, if your method looks like that :
-
-.. code-block:: php
+For example, if your method looks like that::
 
     <?php
-    // src/AppBundle/Entity/Post.php
+    // src/Entity/Post.php
 
     class Post
     {
@@ -28,12 +31,10 @@ For example, if your method looks like that :
 
 You cannot be sure your object will *always* have a title when the bundle will want to convert it to a string.
 So in order to avoid any fatal error, you must return an empty string
-(or anything you prefer) for when the title is missing, like this :
-
-.. code-block:: php
+(or anything you prefer) for when the title is missing, like this::
 
     <?php
-    // src/AppBundle/Entity/Post.php
+    // src/Entity/Post.php
 
     class Post
     {