minor #101 Update some screenshots to wrap them with a browser window (javiereguiluz)

This PR was squashed before being merged into the 2.7 branch (closes #101).

Discussion
----------

Update some screenshots to wrap them with a browser window

This change just adds a CSS class to the generated `<div>` element that wraps images.

Commits
-------

38bb120 Update some screenshots to wrap them with a browser window

Author: javiereguiluz

_images/quick_tour/welcome.png

@@ -39,6 +39,8 @@ while you're reading the Symfony documentation.
 and you'll be redirected to GitHub:
 
 .. image:: /_images/contributing/docs-github-edit-page.png
+   :align: center
+   :class: with-browser
 
 **Step 2.** Edit the contents, describe your changes and click on the
 **Propose file change** button.
@@ -48,6 +50,8 @@ and you'll be redirected to GitHub:
 also display a preview of your changes:
 
 .. image:: /_images/contributing/docs-github-create-pr.png
+   :align: center
+   :class: with-browser
 
 If everything is correct, click on the **Create pull request** button.
 

contributing/documentation/overview.rst

@@ -15,13 +15,17 @@ with lots of debug information to help you quickly discover the root problem:
 
 .. image:: /_images/controller/error_pages/exceptions-in-dev-environment.png
    :alt: A typical exception page in the development environment
+   :align: center
+   :class: with-browser
 
 Since these pages contain a lot of sensitive internal information, Symfony won't
 display them in the production environment. Instead, it'll show a simple and
 generic **error page**:
 
 .. image:: /_images/controller/error_pages/errors-in-prod-environment.png
    :alt: A typical error page in the production environment
+   :align: center
+   :class: with-browser
 
 Error pages for the production environment can be customized in different ways
 depending on your needs:
@@ -273,19 +277,19 @@ will be passed two parameters:
 Instead of creating a new exception controller from scratch you can, of course,
 also extend the default :class:`Symfony\\Bundle\\TwigBundle\\Controller\\ExceptionController`.
 In that case, you might want to override one or both of the ``showAction()`` and
-``findTemplate()`` methods. The latter one locates the template to be used. 
+``findTemplate()`` methods. The latter one locates the template to be used.
 
 .. note::
-  
+
     In case of extending the
     :class:`Symfony\\Bundle\\TwigBundle\\Controller\\ExceptionController` you
     may configure a service to pass the Twig environment and the ``debug`` flag
-    to the constructor. 
-    
+    to the constructor.
+
     .. configuration-block::
-    
+
         .. code-block:: yaml
-    
+
             # app/config/services.yml
             services:
                 app.exception_controller:

controller/error_pages.rst

@@ -175,13 +175,15 @@ developer's best friend!
 
 .. image:: /_images/quick_tour/web_debug_toolbar.png
    :align: center
+   :class: with-browser
 
 But what you see initially is only the tip of the iceberg; click on any
 of the bar sections to open the profiler and get much more detailed information
 about the request, the query parameters, security details and database queries:
 
 .. image:: /_images/quick_tour/profiler.png
    :align: center
+   : class: with-browser
 
 This tool provides so much internal information about your application that
 you may be worried about your visitors accessing sensible information. Symfony

quick_tour/the_big_picture.rst

@@ -137,6 +137,7 @@ Welcome Page of Symfony:
 .. image:: /_images/quick_tour/welcome.png
    :align: center
    :alt:   Symfony Welcome Page
+   :class: with-browser
 
 If you see a blank page or an error page instead of the Welcome Page, there is
 a directory permission misconfiguration. The solution to this problem is

setup.rst

@@ -41,6 +41,8 @@ using a deprecated feature. When visiting your application in the
 in your browser, these notices are shown in the web dev toolbar:
 
 .. image:: /_images/install/deprecations-in-profiler.png
+   :align: center
+   :class: with-browser
 
 Of course ultimately, you want to stop using the deprecated functionality.
 Sometimes, this is easy: the warning might tell you exactly what to change.