diff --git a/controller.rst b/controller.rst
index 1718c3866af..70b6ed7f290 100644
--- a/controller.rst
+++ b/controller.rst
@@ -417,47 +417,25 @@ you'll use this key to retrieve the message.
 In the template of the next page (or even better, in your base layout template),
 read any flash messages from the session:
 
-.. configuration-block::
+.. code-block:: html+twig
 
-    .. code-block:: html+twig
+    {# app/Resources/views/base.html.twig #}
 
-        {# app/Resources/views/base.html.twig #}
+    {# you can read and display just one flash message type... #}
+    {% for flash_message in app.session.flashBag.get('notice') %}
+        <div class="flash-notice">
+            {{ flash_message }}
+        </div>
+    {% endfor %}
 
-        {# you can read and display just one flash message type... #}
-        {% for flash_message in app.session.flashBag.get('notice') %}
-            <div class="flash-notice">
+    {# ...or you can read and display every flash message available #}
+    {% for type, flash_messages in app.session.flashBag.all %}
+        {% for flash_message in flash_messages %}
+            <div class="flash-{{ type }}">
                 {{ flash_message }}
             </div>
         {% endfor %}
-
-        {# ...or you can read and display every flash message available #}
-        {% for type, flash_messages in app.session.flashBag.all %}
-            {% for flash_message in flash_messages %}
-                <div class="flash-{{ type }}">
-                    {{ flash_message }}
-                </div>
-            {% endfor %}
-        {% endfor %}
-
-    .. code-block:: html+php
-
-        <!-- app/Resources/views/base.html.php -->
-
-        // you can read and display just one flash message type...
-        <?php foreach ($view['session']->getFlashBag()->get('notice') as $message): ?>
-            <div class="flash-notice">
-                <?php echo $message ?>
-            </div>
-        <?php endforeach ?>
-
-        // ...or you can read and display every flash message available
-        <?php foreach ($view['session']->getFlashBag()->all() as $type => $flash_messages): ?>
-            <?php foreach ($flash_messages as $flash_message): ?>
-                <div class="flash-<?php echo $type ?>">
-                    <?php echo $message ?>
-                </div>
-            <?php endforeach ?>
-        <?php endforeach ?>
+    {% endfor %}
 
 .. note::
 
diff --git a/forms.rst b/forms.rst
index 21b07ce48a1..7f43ab2fa86 100644
--- a/forms.rst
+++ b/forms.rst
@@ -152,21 +152,12 @@ done by passing a special form "view" object to your template (notice the
 ``$form->createView()`` in the controller above) and using a set of form
 helper functions:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {# app/Resources/views/default/new.html.twig #}
-        {{ form_start(form) }}
-        {{ form_widget(form) }}
-        {{ form_end(form) }}
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <!-- app/Resources/views/default/new.html.php -->
-        <?php echo $view['form']->start($form) ?>
-        <?php echo $view['form']->widget($form) ?>
-        <?php echo $view['form']->end($form) ?>
+    {# app/Resources/views/default/new.html.twig #}
+    {{ form_start(form) }}
+    {{ form_widget(form) }}
+    {{ form_end(form) }}
 
 .. image:: /_images/form/simple-form.png
     :align: center
@@ -432,21 +423,12 @@ Validation is a very powerful feature of Symfony and has its own
     but are being prevented by your browser from, for example, submitting
     blank fields.
 
-    .. configuration-block::
-
-        .. code-block:: html+twig
-
-            {# app/Resources/views/default/new.html.twig #}
-            {{ form_start(form, {'attr': {'novalidate': 'novalidate'}}) }}
-            {{ form_widget(form) }}
-            {{ form_end(form) }}
-
-        .. code-block:: html+php
+.. code-block:: html+twig
 
-            <!-- app/Resources/views/default/new.html.php -->
-            <?php echo $view['form']->start($form, array('attr' => array('novalidate' => 'novalidate') ?>
-            <?php echo $view['form']->widget($form) ?>
-            <?php echo $view['form']->end($form) ?>
+    {# app/Resources/views/default/new.html.twig #}
+    {{ form_start(form, {'attr': {'novalidate': 'novalidate'}}) }}
+    {{ form_widget(form) }}
+    {{ form_end(form) }}
 
 .. index::
    single: Forms; Built-in field types
diff --git a/frontend/assetic/apply_to_option.rst b/frontend/assetic/apply_to_option.rst
index a144f08172f..02507a8028f 100644
--- a/frontend/assetic/apply_to_option.rst
+++ b/frontend/assetic/apply_to_option.rst
@@ -67,22 +67,11 @@ Filter a single File
 You can now serve up a single CoffeeScript file as JavaScript from within your
 templates:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {% javascripts '@AppBundle/Resources/public/js/example.coffee' filter='coffee' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
+.. code-block:: html+twig
 
-    .. code-block:: html+php
-
-        <?php foreach ($view['assetic']->javascripts(
-            array('@AppBundle/Resources/public/js/example.coffee'),
-            array('coffee')
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts '@AppBundle/Resources/public/js/example.coffee' filter='coffee' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 This is all that's needed to compile this CoffeeScript file and serve it
 as the compiled JavaScript.
@@ -92,27 +81,13 @@ Filter multiple Files
 
 You can also combine multiple CoffeeScript files into a single output file:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
+.. code-block:: html+twig
 
-        {% javascripts '@AppBundle/Resources/public/js/example.coffee'
-                       '@AppBundle/Resources/public/js/another.coffee'
-            filter='coffee' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
-
-    .. code-block:: html+php
-
-        <?php foreach ($view['assetic']->javascripts(
-            array(
-                '@AppBundle/Resources/public/js/example.coffee',
-                '@AppBundle/Resources/public/js/another.coffee',
-            ),
-            array('coffee')
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts '@AppBundle/Resources/public/js/example.coffee'
+                   '@AppBundle/Resources/public/js/another.coffee'
+        filter='coffee' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 Both files will now be served up as a single file compiled into regular JavaScript.
 
@@ -188,24 +163,12 @@ template. You can also list regular JavaScript files, all of which will be
 combined and rendered as a single JavaScript file (with only the ``.coffee``
 files being run through the CoffeeScript filter):
 
-.. configuration-block::
+.. code-block:: html+twig
+
+    {% javascripts '@AppBundle/Resources/public/js/example.coffee'
+                   '@AppBundle/Resources/public/js/another.coffee'
+                   '@AppBundle/Resources/public/js/regular.js' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
+
 
-    .. code-block:: html+twig
-
-        {% javascripts '@AppBundle/Resources/public/js/example.coffee'
-                       '@AppBundle/Resources/public/js/another.coffee'
-                       '@AppBundle/Resources/public/js/regular.js' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
-
-    .. code-block:: html+php
-
-        <?php foreach ($view['assetic']->javascripts(
-            array(
-                '@AppBundle/Resources/public/js/example.coffee',
-                '@AppBundle/Resources/public/js/another.coffee',
-                '@AppBundle/Resources/public/js/regular.js',
-            )
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
diff --git a/frontend/assetic/asset_management.rst b/frontend/assetic/asset_management.rst
index 2706f4e3040..80d442b798c 100644
--- a/frontend/assetic/asset_management.rst
+++ b/frontend/assetic/asset_management.rst
@@ -97,15 +97,9 @@ to the user.
 Without Assetic, you just serve the files that are stored in the application
 directly:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
+.. code-block:: html+twig
 
-        <script src="{{ asset('js/script.js') }}"></script>
-
-    .. code-block:: php
-
-        <script src="<?php echo $view['assets']->getUrl('js/script.js') ?>"></script>
+    <script src="{{ asset('js/script.js') }}"></script>
 
 But *with* Assetic, you can manipulate these assets however you want (or
 load them from anywhere) before serving them. This means you can:
@@ -138,21 +132,11 @@ Including JavaScript Files
 
 To include JavaScript files, use the ``javascripts`` tag in any template:
 
-.. configuration-block::
+.. code-block:: html+twig
 
-    .. code-block:: html+twig
-
-        {% javascripts '@AppBundle/Resources/public/js/*' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
-
-    .. code-block:: html+php
-
-        <?php foreach ($view['assetic']->javascripts(
-            array('@AppBundle/Resources/public/js/*')
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts '@AppBundle/Resources/public/js/*' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 .. note::
 
@@ -194,22 +178,11 @@ Including CSS Stylesheets
 To bring in CSS stylesheets, you can use the same technique explained above,
 except with the ``stylesheets`` tag:
 
-.. configuration-block::
+.. code-block:: html+twig
 
-    .. code-block:: html+twig
-
-        {% stylesheets 'bundles/app/css/*' filter='cssrewrite' %}
-            <link rel="stylesheet" href="{{ asset_url }}" />
-        {% endstylesheets %}
-
-    .. code-block:: html+php
-
-        <?php foreach ($view['assetic']->stylesheets(
-            array('bundles/app/css/*'),
-            array('cssrewrite')
-        ) as $url): ?>
-            <link rel="stylesheet" href="<?php echo $view->escape($url) ?>" />
-        <?php endforeach ?>
+    {% stylesheets 'bundles/app/css/*' filter='cssrewrite' %}
+        <link rel="stylesheet" href="{{ asset_url }}" />
+    {% endstylesheets %}
 
 .. note::
 
@@ -247,21 +220,11 @@ Including Images
 
 To include an image you can use the ``image`` tag.
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {% image '@AppBundle/Resources/public/images/example.jpg' %}
-            <img src="{{ asset_url }}" alt="Example" />
-        {% endimage %}
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <?php foreach ($view['assetic']->image(
-            array('@AppBundle/Resources/public/images/example.jpg')
-        ) as $url): ?>
-            <img src="<?php echo $view->escape($url) ?>" alt="Example" />
-        <?php endforeach ?>
+    {% image '@AppBundle/Resources/public/images/example.jpg' %}
+        <img src="{{ asset_url }}" alt="Example" />
+    {% endimage %}
 
 You can also use Assetic for image optimization. More information in
 :doc:`/frontend/assetic/jpeg_optimize`.
@@ -299,28 +262,14 @@ manageable parts. This can help with re-usability as you can easily split
 project-specific files from those which can be used in other applications,
 but still serve them as a single file:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
+.. code-block:: html+twig
 
-        {% javascripts
-            '@AppBundle/Resources/public/js/*'
-            '@AcmeBarBundle/Resources/public/js/form.js'
-            '@AcmeBarBundle/Resources/public/js/calendar.js' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
-
-    .. code-block:: html+php
-
-        <?php foreach ($view['assetic']->javascripts(
-            array(
-                '@AppBundle/Resources/public/js/*',
-                '@AcmeBarBundle/Resources/public/js/form.js',
-                '@AcmeBarBundle/Resources/public/js/calendar.js',
-            )
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts
+        '@AppBundle/Resources/public/js/*'
+        '@AcmeBarBundle/Resources/public/js/form.js'
+        '@AcmeBarBundle/Resources/public/js/calendar.js' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 In the ``dev`` environment, each file is still served individually, so that
 you can debug problems more easily. However, in the ``prod`` environment
@@ -338,26 +287,13 @@ the JavaScript files.
 And combining files doesn't only apply to *your* files. You can also use Assetic to
 combine third party assets, such as jQuery, with your own into a single file:
 
-.. configuration-block::
+.. code-block:: html+twig
 
-    .. code-block:: html+twig
-
-        {% javascripts
-            '@AppBundle/Resources/public/js/thirdparty/jquery.js'
-            '@AppBundle/Resources/public/js/*' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
-
-    .. code-block:: html+php
-
-        <?php foreach ($view['assetic']->javascripts(
-            array(
-                '@AppBundle/Resources/public/js/thirdparty/jquery.js',
-                '@AppBundle/Resources/public/js/*',
-            )
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts
+        '@AppBundle/Resources/public/js/thirdparty/jquery.js'
+        '@AppBundle/Resources/public/js/*' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 Using Named Assets
 ~~~~~~~~~~~~~~~~~~
@@ -416,26 +352,13 @@ configuration under the ``assetic`` section. Read more in the
 After you have defined the named assets, you can reference them in your templates
 with the ``@named_asset`` notation:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {% javascripts
-            '@jquery_and_ui'
-            '@AppBundle/Resources/public/js/*' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <?php foreach ($view['assetic']->javascripts(
-            array(
-                '@jquery_and_ui',
-                '@AppBundle/Resources/public/js/*',
-            )
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts
+        '@jquery_and_ui'
+        '@AppBundle/Resources/public/js/*' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 .. _assetic-filters:
 
@@ -506,22 +429,11 @@ should be defined:
 Now, to actually *use* the filter on a group of JavaScript files, add it
 into your template:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {% javascripts '@AppBundle/Resources/public/js/*' filter='uglifyjs2' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <?php foreach ($view['assetic']->javascripts(
-            array('@AppBundle/Resources/public/js/*'),
-            array('uglifyjs2')
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts '@AppBundle/Resources/public/js/*' filter='uglifyjs2' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 A more detailed guide about configuring and using Assetic filters as well as
 details of Assetic's debug mode can be found in :doc:`/frontend/assetic/uglifyjs`.
@@ -532,23 +444,11 @@ Controlling the URL Used
 If you wish to, you can control the URLs that Assetic produces. This is
 done from the template and is relative to the public document root:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {% javascripts '@AppBundle/Resources/public/js/*' output='js/compiled/main.js' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
+.. code-block:: html+twig
 
-    .. code-block:: html+php
-
-        <?php foreach ($view['assetic']->javascripts(
-            array('@AppBundle/Resources/public/js/*'),
-            array(),
-            array('output' => 'js/compiled/main.js')
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts '@AppBundle/Resources/public/js/*' output='js/compiled/main.js' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 .. note::
 
@@ -669,22 +569,10 @@ Since running this command in the ``dev`` environment may generate a bunch
 of files, it's usually a good idea to point your generated asset files to
 some isolated directory (e.g. ``/js/compiled``), to keep things organized:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {% javascripts '@AppBundle/Resources/public/js/*' output='js/compiled/main.js' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <?php foreach ($view['assetic']->javascripts(
-            array('@AppBundle/Resources/public/js/*'),
-            array(),
-            array('output' => 'js/compiled/main.js')
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts '@AppBundle/Resources/public/js/*' output='js/compiled/main.js' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 .. _`LiipImagineBundle`: https://github.com/liip/LiipImagineBundle
diff --git a/frontend/assetic/jpeg_optimize.rst b/frontend/assetic/jpeg_optimize.rst
index 8e6871163d1..324975cbae7 100644
--- a/frontend/assetic/jpeg_optimize.rst
+++ b/frontend/assetic/jpeg_optimize.rst
@@ -61,23 +61,12 @@ using the ``bin`` option of the ``jpegoptim`` filter:
 
 It can now be used from a template:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {% image '@AppBundle/Resources/public/images/example.jpg'
-            filter='jpegoptim' output='/images/example.jpg' %}
-            <img src="{{ asset_url }}" alt="Example"/>
-        {% endimage %}
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <?php foreach ($view['assetic']->image(
-            array('@AppBundle/Resources/public/images/example.jpg'),
-            array('jpegoptim')
-        ) as $url): ?>
-            <img src="<?php echo $view->escape($url) ?>" alt="Example"/>
-        <?php endforeach ?>
+    {% image '@AppBundle/Resources/public/images/example.jpg'
+        filter='jpegoptim' output='/images/example.jpg' %}
+        <img src="{{ asset_url }}" alt="Example"/>
+    {% endimage %}
 
 Removing all EXIF Data
 ~~~~~~~~~~~~~~~~~~~~~~
diff --git a/frontend/assetic/uglifyjs.rst b/frontend/assetic/uglifyjs.rst
index 89b39fd7b4a..4da6c61e005 100644
--- a/frontend/assetic/uglifyjs.rst
+++ b/frontend/assetic/uglifyjs.rst
@@ -183,22 +183,11 @@ Minify your Assets
 In order to apply UglifyJS on your assets, add the ``filter`` option in the
 asset tags of your templates to tell Assetic to use the ``uglifyjs2`` filter:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {% javascripts '@AppBundle/Resources/public/js/*' filter='uglifyjs2' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
+.. code-block:: html+twig
 
-    .. code-block:: html+php
-
-        <?php foreach ($view['assetic']->javascripts(
-            array('@AppBundle/Resources/public/js/*'),
-            array('uglifyj2s')
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts '@AppBundle/Resources/public/js/*' filter='uglifyjs2' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 .. note::
 
@@ -218,22 +207,11 @@ debug (e.g. ``app_dev.php``) mode. You can do this by prefixing the filter name
 in your template with a question mark: ``?``. This tells Assetic to only
 apply this filter when debug mode is off (e.g. ``app.php``):
 
-.. configuration-block::
-
-    .. code-block:: html+twig
+.. code-block:: html+twig
 
-        {% javascripts '@AppBundle/Resources/public/js/*' filter='?uglifyjs2' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
-
-    .. code-block:: html+php
-
-        <?php foreach ($view['assetic']->javascripts(
-            array('@AppBundle/Resources/public/js/*'),
-            array('?uglifyjs2')
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts '@AppBundle/Resources/public/js/*' filter='?uglifyjs2' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 To try this out, switch to your ``prod`` environment (``app.php``). But before
 you do, don't forget to :ref:`clear your cache <page-creation-prod-cache-clear>`
@@ -305,23 +283,11 @@ Next, add the configuration for this filter:
 To use the filter for your CSS files, add the filter to the Assetic ``stylesheets``
 helper:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {% stylesheets 'bundles/App/css/*' filter='uglifycss' filter='cssrewrite' %}
-             <link rel="stylesheet" href="{{ asset_url }}" />
-        {% endstylesheets %}
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <?php foreach ($view['assetic']->stylesheets(
-            array('bundles/App/css/*'),
-            array('uglifycss'),
-            array('cssrewrite')
-        ) as $url): ?>
-            <link rel="stylesheet" href="<?php echo $view->escape($url) ?>" />
-        <?php endforeach ?>
+    {% stylesheets 'bundles/App/css/*' filter='uglifycss' filter='cssrewrite' %}
+         <link rel="stylesheet" href="{{ asset_url }}" />
+    {% endstylesheets %}
 
 Just like with the ``uglifyjs2`` filter, if you prefix the filter name with
 ``?`` (i.e. ``?uglifycss``), the minification will only happen when you're
diff --git a/frontend/assetic/yuicompressor.rst b/frontend/assetic/yuicompressor.rst
index 1b71bb417c3..c0d4aa8018a 100644
--- a/frontend/assetic/yuicompressor.rst
+++ b/frontend/assetic/yuicompressor.rst
@@ -95,22 +95,11 @@ You have YUI Compressor configured now, but nothing is going to happen until
 you apply one of these filters to an asset. Since your assets are a part of
 the view layer, this work is done in your templates:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {% javascripts '@AppBundle/Resources/public/js/*' filter='yui_js' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
+.. code-block:: html+twig
 
-    .. code-block:: html+php
-
-        <?php foreach ($view['assetic']->javascripts(
-            array('@AppBundle/Resources/public/js/*'),
-            array('yui_js')
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts '@AppBundle/Resources/public/js/*' filter='yui_js' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 .. note::
 
@@ -123,22 +112,11 @@ With the addition of the ``yui_js`` filter to the asset tags above, you should
 now see minified JavaScripts coming over the wire much faster. The same process
 can be repeated to minify your stylesheets.
 
-.. configuration-block::
-
-    .. code-block:: html+twig
+.. code-block:: html+twig
 
-        {% stylesheets '@AppBundle/Resources/public/css/*' filter='yui_css' %}
-            <link rel="stylesheet" type="text/css" media="screen" href="{{ asset_url }}" />
-        {% endstylesheets %}
-
-    .. code-block:: html+php
-
-        <?php foreach ($view['assetic']->stylesheets(
-            array('@AppBundle/Resources/public/css/*'),
-            array('yui_css')
-        ) as $url): ?>
-            <link rel="stylesheet" type="text/css" media="screen" href="<?php echo $view->escape($url) ?>" />
-        <?php endforeach ?>
+    {% stylesheets '@AppBundle/Resources/public/css/*' filter='yui_css' %}
+        <link rel="stylesheet" type="text/css" media="screen" href="{{ asset_url }}" />
+    {% endstylesheets %}
 
 Disable Minification in Debug Mode
 ----------------------------------
@@ -149,22 +127,11 @@ application is in debug mode. You can do this by prefixing the filter name
 in your template with a question mark: ``?``. This tells Assetic to only
 apply this filter when debug mode is off.
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {% javascripts '@AppBundle/Resources/public/js/*' filter='?yui_js' %}
-            <script src="{{ asset_url }}"></script>
-        {% endjavascripts %}
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <?php foreach ($view['assetic']->javascripts(
-            array('@AppBundle/Resources/public/js/*'),
-            array('?yui_js')
-        ) as $url): ?>
-            <script src="<?php echo $view->escape($url) ?>"></script>
-        <?php endforeach ?>
+    {% javascripts '@AppBundle/Resources/public/js/*' filter='?yui_js' %}
+        <script src="{{ asset_url }}"></script>
+    {% endjavascripts %}
 
 .. tip::
 
diff --git a/reference/configuration/framework.rst b/reference/configuration/framework.rst
index fee66841949..adb53871f19 100644
--- a/reference/configuration/framework.rst
+++ b/reference/configuration/framework.rst
@@ -1153,15 +1153,9 @@ You can group assets into packages, to specify different base URLs for them:
 
 Now you can use the ``avatars`` package in your templates:
 
-.. configuration-block:: php
+.. code-block:: html+twig
 
-    .. code-block:: html+twig
-
-        <img src="{{ asset('...', 'avatars') }}">
-
-    .. code-block:: html+php
-
-        <img src="<?php echo $view['assets']->getUrl('...', 'avatars') ?>">
+    <img src="{{ asset('...', 'avatars') }}">
 
 Each package can configure the following options:
 
@@ -1185,15 +1179,9 @@ equivalent) as well as assets rendered with Assetic.
 
 For example, suppose you have the following:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        <img src="{{ asset('images/logo.png') }}" alt="Symfony!" />
-
-    .. code-block:: php
+.. code-block:: html+twig
 
-        <img src="<?php echo $view['assets']->getUrl('images/logo.png') ?>" alt="Symfony!" />
+    <img src="{{ asset('images/logo.png') }}" alt="Symfony!" />
 
 By default, this will render a path to your image such as ``/images/logo.png``.
 Now, activate the ``version`` option:
diff --git a/reference/forms/twig_reference.rst b/reference/forms/twig_reference.rst
index 581061f75ae..96c19ab9196 100644
--- a/reference/forms/twig_reference.rst
+++ b/reference/forms/twig_reference.rst
@@ -315,21 +315,12 @@ reference the variables on the ``name`` field, accessing the variables is
 done by using a public ``vars`` property on the
 :class:`Symfony\\Component\\Form\\FormView` object:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        <label for="{{ form.name.vars.id }}"
-            class="{{ form.name.vars.required ? 'required' : '' }}">
-            {{ form.name.vars.label }}
-        </label>
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <label for="<?php echo $view['form']->get('name')->vars['id'] ?>"
-            class="<?php echo $view['form']->get('name')->vars['required'] ? 'required' : '' ?>">
-            <?php echo $view['form']->get('name')->vars['label'] ?>
-        </label>
+    <label for="{{ form.name.vars.id }}"
+        class="{{ form.name.vars.required ? 'required' : '' }}">
+        {{ form.name.vars.label }}
+    </label>
 
 .. versionadded:: 2.3
     The ``method`` and ``action`` variables were introduced in Symfony 2.3.
diff --git a/reference/forms/types/collection.rst b/reference/forms/types/collection.rst
index faa1c5fcefb..17f9b03d5dd 100644
--- a/reference/forms/types/collection.rst
+++ b/reference/forms/types/collection.rst
@@ -69,47 +69,25 @@ address as its own input text box::
 
 The simplest way to render this is all at once:
 
-.. configuration-block::
+.. code-block:: twig
 
-    .. code-block:: twig
-
-        {{ form_row(form.emails) }}
-
-    .. code-block:: php
-
-        <?php echo $view['form']->row($form['emails']) ?>
+    {{ form_row(form.emails) }}
 
 A much more flexible method would look like this:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {{ form_label(form.emails) }}
-        {{ form_errors(form.emails) }}
-
-        <ul>
-        {% for emailField in form.emails %}
-            <li>
-                {{ form_errors(emailField) }}
-                {{ form_widget(emailField) }}
-            </li>
-        {% endfor %}
-        </ul>
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <?php echo $view['form']->label($form['emails']) ?>
-        <?php echo $view['form']->errors($form['emails']) ?>
+    {{ form_label(form.emails) }}
+    {{ form_errors(form.emails) }}
 
-        <ul>
-        <?php foreach ($form['emails'] as $emailField): ?>
-            <li>
-                <?php echo $view['form']->errors($emailField) ?>
-                <?php echo $view['form']->widget($emailField) ?>
-            </li>
-        <?php endforeach ?>
-        </ul>
+    <ul>
+    {% for emailField in form.emails %}
+        <li>
+            {{ form_errors(emailField) }}
+            {{ form_widget(emailField) }}
+        </li>
+    {% endfor %}
+    </ul>
 
 In both cases, no input fields would render unless your ``emails`` data
 array already contained some emails.
@@ -359,15 +337,9 @@ be added to your underlying array due to the `allow_add`_ option.
 The prototype field can be rendered via the ``prototype`` variable in the
 collection field:
 
-.. configuration-block::
-
-    .. code-block:: twig
-
-        {{ form_row(form.emails.vars.prototype) }}
-
-    .. code-block:: php
+.. code-block:: twig
 
-        <?php echo $view['form']->row($form['emails']->vars['prototype']) ?>
+    {{ form_row(form.emails.vars.prototype) }}
 
 Note that all you really need is the "widget", but depending on how you're
 rendering your form, having the entire "form row" may be easier for you.
diff --git a/reference/forms/types/repeated.rst b/reference/forms/types/repeated.rst
index 3a100827ee6..17e2c52e994 100644
--- a/reference/forms/types/repeated.rst
+++ b/reference/forms/types/repeated.rst
@@ -68,30 +68,17 @@ The repeated field type is actually two underlying fields, which you can
 render all at once, or individually. To render all at once, use something
 like:
 
-.. configuration-block::
+.. code-block:: twig
 
-    .. code-block:: twig
-
-        {{ form_row(form.password) }}
-
-    .. code-block:: php
-
-        <?php echo $view['form']->row($form['password']) ?>
+    {{ form_row(form.password) }}
 
 To render each field individually, use something like this:
 
-.. configuration-block::
-
-    .. code-block:: twig
-
-        {# .first and .second may vary in your use - see the note below #}
-        {{ form_row(form.password.first) }}
-        {{ form_row(form.password.second) }}
-
-    .. code-block:: php
+.. code-block:: twig
 
-        <?php echo $view['form']->row($form['password']['first']) ?>
-        <?php echo $view['form']->row($form['password']['second']) ?>
+    {# .first and .second may vary in your use - see the note below #}
+    {{ form_row(form.password.first) }}
+    {{ form_row(form.password.second) }}
 
 .. note::
 
diff --git a/security.rst b/security.rst
index 0ba07f778ad..62def3292cb 100644
--- a/security.rst
+++ b/security.rst
@@ -879,19 +879,11 @@ Access Control in Templates
 If you want to check if the current user has a role inside a template, use
 the built-in ``is_granted()`` helper function:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
+.. code-block:: html+twig
 
-        {% if is_granted('ROLE_ADMIN') %}
-            <a href="...">Delete</a>
-        {% endif %}
-
-    .. code-block:: html+php
-
-        <?php if ($view['security']->isGranted('ROLE_ADMIN')): ?>
-            <a href="...">Delete</a>
-        <?php endif ?>
+    {% if is_granted('ROLE_ADMIN') %}
+        <a href="...">Delete</a>
+    {% endif %}
 
 .. note::
 
@@ -1070,19 +1062,11 @@ Retrieving the User in a Template
 In a Twig Template this object can be accessed via the :ref:`app.user <reference-twig-global-app>`
 key:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {% if is_granted('IS_AUTHENTICATED_FULLY') %}
-            <p>Username: {{ app.user.username }}</p>
-        {% endif %}
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <?php if ($view['security']->isGranted('IS_AUTHENTICATED_FULLY')): ?>
-            <p>Username: <?php echo $app->getUser()->getUsername() ?></p>
-        <?php endif; ?>
+    {% if is_granted('IS_AUTHENTICATED_FULLY') %}
+        <p>Username: {{ app.user.username }}</p>
+    {% endif %}
 
 .. _security-logging-out:
 
diff --git a/templating.rst b/templating.rst
index 33427cf8c2f..413e3ae4807 100644
--- a/templating.rst
+++ b/templating.rst
@@ -170,59 +170,30 @@ that overrides certain methods of its parent class").
 
 First, build a base layout file:
 
-.. configuration-block::
+.. code-block:: html+twig
 
-    .. code-block:: html+twig
+    {# app/Resources/views/base.html.twig #}
+    <!DOCTYPE html>
+    <html>
+        <head>
+            <meta charset="UTF-8">
+            <title>{% block title %}Test Application{% endblock %}</title>
+        </head>
+        <body>
+            <div id="sidebar">
+                {% block sidebar %}
+                    <ul>
+                        <li><a href="/">Home</a></li>
+                        <li><a href="/blog">Blog</a></li>
+                    </ul>
+                {% endblock %}
+            </div>
 
-        {# app/Resources/views/base.html.twig #}
-        <!DOCTYPE html>
-        <html>
-            <head>
-                <meta charset="UTF-8">
-                <title>{% block title %}Test Application{% endblock %}</title>
-            </head>
-            <body>
-                <div id="sidebar">
-                    {% block sidebar %}
-                        <ul>
-                            <li><a href="/">Home</a></li>
-                            <li><a href="/blog">Blog</a></li>
-                        </ul>
-                    {% endblock %}
-                </div>
-
-                <div id="content">
-                    {% block body %}{% endblock %}
-                </div>
-            </body>
-        </html>
-
-    .. code-block:: html+php
-
-        <!-- app/Resources/views/base.html.php -->
-        <!DOCTYPE html>
-        <html>
-            <head>
-                <meta charset="UTF-8">
-                <title><?php $view['slots']->output('title', 'Test Application') ?></title>
-            </head>
-            <body>
-                <div id="sidebar">
-                    <?php if ($view['slots']->has('sidebar')): ?>
-                        <?php $view['slots']->output('sidebar') ?>
-                    <?php else: ?>
-                        <ul>
-                            <li><a href="/">Home</a></li>
-                            <li><a href="/blog">Blog</a></li>
-                        </ul>
-                    <?php endif ?>
-                </div>
-
-                <div id="content">
-                    <?php $view['slots']->output('body') ?>
-                </div>
-            </body>
-        </html>
+            <div id="content">
+                {% block body %}{% endblock %}
+            </div>
+        </body>
+    </html>
 
 .. note::
 
@@ -238,35 +209,19 @@ simply retain the default values used in this template.
 
 A child template might look like this:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {# app/Resources/views/blog/index.html.twig #}
-        {% extends 'base.html.twig' %}
-
-        {% block title %}My cool blog posts{% endblock %}
-
-        {% block body %}
-            {% for entry in blog_entries %}
-                <h2>{{ entry.title }}</h2>
-                <p>{{ entry.body }}</p>
-            {% endfor %}
-        {% endblock %}
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <!-- app/Resources/views/blog/index.html.php -->
-        <?php $view->extend('base.html.php') ?>
+    {# app/Resources/views/blog/index.html.twig #}
+    {% extends 'base.html.twig' %}
 
-        <?php $view['slots']->set('title', 'My cool blog posts') ?>
+    {% block title %}My cool blog posts{% endblock %}
 
-        <?php $view['slots']->start('body') ?>
-            <?php foreach ($blog_entries as $entry): ?>
-                <h2><?php echo $entry->getTitle() ?></h2>
-                <p><?php echo $entry->getBody() ?></p>
-            <?php endforeach ?>
-        <?php $view['slots']->stop() ?>
+    {% block body %}
+        {% for entry in blog_entries %}
+            <h2>{{ entry.title }}</h2>
+            <p>{{ entry.body }}</p>
+        {% endfor %}
+    {% endblock %}
 
 .. note::
 
@@ -480,60 +435,30 @@ a new PHP class or function. The same is true for templates. By moving the
 reused template code into its own template, it can be included from any other
 template. First, create the template that you'll need to reuse.
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {# app/Resources/views/article/article_details.html.twig #}
-        <h2>{{ article.title }}</h2>
-        <h3 class="byline">by {{ article.authorName }}</h3>
-
-        <p>
-            {{ article.body }}
-        </p>
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <!-- app/Resources/views/article/article_details.html.php -->
-        <h2><?php echo $article->getTitle() ?></h2>
-        <h3 class="byline">by <?php echo $article->getAuthorName() ?></h3>
+    {# app/Resources/views/article/article_details.html.twig #}
+    <h2>{{ article.title }}</h2>
+    <h3 class="byline">by {{ article.authorName }}</h3>
 
-        <p>
-            <?php echo $article->getBody() ?>
-        </p>
+    <p>
+        {{ article.body }}
+    </p>
 
 Including this template from any other template is simple:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {# app/Resources/views/article/list.html.twig #}
-        {% extends 'layout.html.twig' %}
-
-        {% block body %}
-            <h1>Recent Articles<h1>
-
-            {% for article in articles %}
-                {{ include('article/article_details.html.twig', { 'article': article }) }}
-            {% endfor %}
-        {% endblock %}
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <!-- app/Resources/article/list.html.php -->
-        <?php $view->extend('layout.html.php') ?>
+    {# app/Resources/views/article/list.html.twig #}
+    {% extends 'layout.html.twig' %}
 
-        <?php $view['slots']->start('body') ?>
-            <h1>Recent Articles</h1>
+    {% block body %}
+        <h1>Recent Articles<h1>
 
-            <?php foreach ($articles as $article): ?>
-                <?php echo $view->render(
-                    'Article/article_details.html.php',
-                    array('article' => $article)
-                ) ?>
-            <?php endforeach ?>
-        <?php $view['slots']->stop() ?>
+        {% for article in articles %}
+            {{ include('article/article_details.html.twig', { 'article': article }) }}
+        {% endfor %}
+    {% endblock %}
 
 The template is included using the ``{{ include() }}`` function. Notice that the
 template name follows the same typical convention. The ``article_details.html.twig``
@@ -626,15 +551,9 @@ configuration:
 
 To link to the page, just use the ``path()`` Twig function and refer to the route:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        <a href="{{ path('welcome') }}">Home</a>
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <a href="<?php echo $view['router']->path('welcome') ?>">Home</a>
+    <a href="{{ path('welcome') }}">Home</a>
 
 .. versionadded:: 2.8
     The ``path()`` PHP templating helper was introduced in Symfony 2.8. Prior
@@ -702,44 +621,22 @@ a value for the ``{slug}`` parameter. Using this route, revisit the
 ``recent_list.html.twig`` template from the previous section and link to the articles
 correctly:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {# app/Resources/views/article/recent_list.html.twig #}
-        {% for article in articles %}
-            <a href="{{ path('article_show', {'slug': article.slug}) }}">
-                {{ article.title }}
-            </a>
-        {% endfor %}
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <!-- app/Resources/views/Article/recent_list.html.php -->
-        <?php foreach ($articles as $article): ?>
-            <a href="<?php echo $view['router']->path('article_show', array(
-                'slug' => $article->getSlug(),
-            )) ?>">
-                <?php echo $article->getTitle() ?>
-            </a>
-        <?php endforeach ?>
+    {# app/Resources/views/article/recent_list.html.twig #}
+    {% for article in articles %}
+        <a href="{{ path('article_show', {'slug': article.slug}) }}">
+            {{ article.title }}
+        </a>
+    {% endfor %}
 
 .. tip::
 
     You can also generate an absolute URL by using the ``url()`` Twig function:
 
-    .. configuration-block::
-
-        .. code-block:: html+twig
-
-            <a href="{{ url('welcome') }}">Home</a>
-
-        .. code-block:: html+php
+.. code-block:: html+twig
 
-            <a href="<?php echo $view['router']->url(
-                'welcome',
-                array()
-            ) ?>">Home</a>
+    <a href="{{ url('welcome') }}">Home</a>
 
     .. versionadded:: 2.8
         The ``url()`` PHP templating helper was introduced in Symfony 2.8. Prior
@@ -759,19 +656,11 @@ Templates also commonly refer to images, JavaScript, stylesheets and other
 assets. Of course you could hard-code the path to these assets (e.g. ``/images/logo.png``),
 but Symfony provides a more dynamic option via the ``asset()`` Twig function:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        <img src="{{ asset('images/logo.png') }}" alt="Symfony!" />
-
-        <link href="{{ asset('css/blog.css') }}" rel="stylesheet" />
-
-    .. code-block:: html+php
+.. code-block:: html+twig
 
-        <img src="<?php echo $view['assets']->getUrl('images/logo.png') ?>" alt="Symfony!" />
+    <img src="{{ asset('images/logo.png') }}" alt="Symfony!" />
 
-        <link href="<?php echo $view['assets']->getUrl('css/blog.css') ?>" rel="stylesheet" />
+    <link href="{{ asset('css/blog.css') }}" rel="stylesheet" />
 
 The ``asset()`` function's main purpose is to make your application more portable.
 If your application lives at the root of your host (e.g. ``http://example.com``),
@@ -819,76 +708,43 @@ one called ``stylesheets`` inside the ``head`` tag and another called ``javascri
 just above the closing ``body`` tag. These blocks will contain all of the
 stylesheets and JavaScripts that you'll need throughout your site:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {# app/Resources/views/base.html.twig #}
-        <html>
-            <head>
-                {# ... #}
-
-                {% block stylesheets %}
-                    <link href="{{ asset('css/main.css') }}" rel="stylesheet" />
-                {% endblock %}
-            </head>
-            <body>
-                {# ... #}
-
-                {% block javascripts %}
-                    <script src="{{ asset('js/main.js') }}"></script>
-                {% endblock %}
-            </body>
-        </html>
-
-    .. code-block:: php
+.. code-block:: html+twig
 
-        // app/Resources/views/base.html.php
-        <html>
-            <head>
-                <?php ... ?>
+    {# app/Resources/views/base.html.twig #}
+    <html>
+        <head>
+            {# ... #}
 
-                <?php $view['slots']->start('stylesheets') ?>
-                    <link href="<?php echo $view['assets']->getUrl('css/main.css') ?>" rel="stylesheet" />
-                <?php $view['slots']->stop() ?>
-            </head>
-            <body>
-                <?php ... ?>
+            {% block stylesheets %}
+                <link href="{{ asset('css/main.css') }}" rel="stylesheet" />
+            {% endblock %}
+        </head>
+        <body>
+            {# ... #}
 
-                <?php $view['slots']->start('javascripts') ?>
-                    <script src="<?php echo $view['assets']->getUrl('js/main.js') ?>"></script>
-                <?php $view['slots']->stop() ?>
-            </body>
-        </html>
+            {% block javascripts %}
+                <script src="{{ asset('js/main.js') }}"></script>
+            {% endblock %}
+        </body>
+    </html>
 
 That's easy enough! But what if you need to include an extra stylesheet or
 JavaScript from a child template? For example, suppose you have a contact
 page and you need to include a ``contact.css`` stylesheet *just* on that
 page. From inside that contact page's template, do the following:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {# app/Resources/views/contact/contact.html.twig #}
-        {% extends 'base.html.twig' %}
-
-        {% block stylesheets %}
-            {{ parent() }}
-
-            <link href="{{ asset('css/contact.css') }}" rel="stylesheet" />
-        {% endblock %}
+.. code-block:: html+twig
 
-        {# ... #}
+    {# app/Resources/views/contact/contact.html.twig #}
+    {% extends 'base.html.twig' %}
 
-    .. code-block:: php
+    {% block stylesheets %}
+        {{ parent() }}
 
-        // app/Resources/views/contact/contact.html.twig
-        <?php $view->extend('base.html.php') ?>
+        <link href="{{ asset('css/contact.css') }}" rel="stylesheet" />
+    {% endblock %}
 
-        <?php $view['slots']->start('stylesheets') ?>
-            <link href="<?php echo $view['assets']->getUrl('css/contact.css') ?>" rel="stylesheet" />
-        <?php $view['slots']->stop() ?>
+    {# ... #}
 
 In the child template, you simply override the ``stylesheets`` block and
 put your new stylesheet tag inside of that block. Of course, since you want
diff --git a/validation.rst b/validation.rst
index 2196107c11b..cdd2be841fc 100644
--- a/validation.rst
+++ b/validation.rst
@@ -179,27 +179,15 @@ You could also pass the collection of errors into a template::
 
 Inside the template, you can output the list of errors exactly as needed:
 
-.. configuration-block::
-
-    .. code-block:: html+twig
-
-        {# app/Resources/views/author/validation.html.twig #}
-        <h3>The author has the following errors</h3>
-        <ul>
-        {% for error in errors %}
-            <li>{{ error.message }}</li>
-        {% endfor %}
-        </ul>
-
-    .. code-block:: html+php
-
-        <!-- app/Resources/views/author/validation.html.php -->
-        <h3>The author has the following errors</h3>
-        <ul>
-        <?php foreach ($errors as $error): ?>
-            <li><?php echo $error->getMessage() ?></li>
-        <?php endforeach ?>
-        </ul>
+.. code-block:: html+twig
+
+    {# app/Resources/views/author/validation.html.twig #}
+    <h3>The author has the following errors</h3>
+    <ul>
+    {% for error in errors %}
+        <li>{{ error.message }}</li>
+    {% endfor %}
+    </ul>
 
 .. note::