renamed Symfony2 to Symfony

README.md

@@ -1,4 +1,4 @@
-SonataAdminBundle - The missing Symfony2 Admin Generator
+SonataAdminBundle - The missing Symfony Admin Generator
 ========================================================
 
 [![Build Status](https://secure.travis-ci.org/sonata-project/SonataAdminBundle.png?branch=master)](http://travis-ci.org/sonata-project/SonataAdminBundle)

Resources/doc/reference/architecture.rst

@@ -111,7 +111,7 @@ or how to build the list view. Inside the ``CRUDController``, you can access the
 
     `CRUD is an acronym`_ for "Create, Read, Update and Delete"
 
-The ``CRUDController`` is no different from any other Symfony2 controller, meaning
+The ``CRUDController`` is no different from any other Symfony controller, meaning
 that you have all the usual options available to you, like getting services from
 the Dependency Injection Container (DIC).
 
@@ -305,7 +305,7 @@ instead of the default ones.
 Managing ``Admin`` Service
 --------------------------
 
-Your ``Admin`` service definitions are parsed when Symfony2 is loaded, and handled by
+Your ``Admin`` service definitions are parsed when Symfony is loaded, and handled by
 the ``Pool`` class. This class, available as the ``sonata.admin.pool`` service from the
 DIC, handles the ``Admin`` classes, lazy-loading them on demand (to reduce overhead)
 and matching each of them to a group. It is also responsible for handling the top level

Resources/doc/reference/getting_started.rst

@@ -192,7 +192,7 @@ translating labels on the admin pages. If you don't call ``setTranslationDomain`
 More info on the `Symfony translations page`_.
 
 Now that you have a configuration file with your admin service, you just need to tell
-Symfony2 to load it. There are two ways to do so:
+Symfony to load it. There are two ways to do so:
 
 Have your bundle load it
 ^^^^^^^^^^^^^^^^^^^^^^^^

Resources/doc/reference/installation.rst

@@ -2,7 +2,7 @@ Installation
 ============
 
 SonataAdminBundle can be installed at any moment during a project's lifecycle,
-whether it's a clean Symfony2 installation or an existing project.
+whether it's a clean Symfony installation or an existing project.
 
 Downloading the code
 --------------------
@@ -14,7 +14,7 @@ Use composer to manage your dependencies and download SonataAdminBundle:
     $ php composer.phar require sonata-project/admin-bundle
 
 You'll be asked to type in a version constraint. 'dev-master' will get you the latest
-version, compatible with the latest Symfony2 version. Check `packagist <https://packagist.org/packages/sonata-project/admin-bundle>`_
+version, compatible with the latest Symfony version. Check `packagist <https://packagist.org/packages/sonata-project/admin-bundle>`_
 for older versions:
 
 .. code-block:: bash
@@ -106,7 +106,7 @@ Configuring SonataAdminBundle dependencies
 
 You will need to configure SonataAdminBundle's dependencies. For each of the above
 mentioned bundles, check their respective installation/configuration instructions
-files to see what changes you have to make to your Symfony2 configuration.
+files to see what changes you have to make to your Symfony configuration.
 
 SonataAdminBundle provides a SonataBlockBundle block that's used on the administration
 dashboard. To be able to use it, make sure it's enabled on SonataBlockBundle's configuration:
@@ -146,7 +146,7 @@ Usually, when installing new bundles, it is a good practice to also delete your
 
     $ php app/console cache:clear
 
-At this point, your Symfony2 installation should be fully functional, with no errors
+At this point, your Symfony installation should be fully functional, with no errors
 showing up from SonataAdminBundle or its dependencies. SonataAdminBundle is installed
 but not yet configured (more on that in the next section), so you won't be able to
 use it yet.

Resources/doc/reference/saving_hooks.rst

@@ -29,7 +29,7 @@ advantage.
 Example used with the FOS/UserBundle
 ------------------------------------
 
-The ``FOSUserBundle`` provides authentication features for your Symfony2 Project,
+The ``FOSUserBundle`` provides authentication features for your Symfony Project,
 and is compatible with Doctrine ORM, Doctrine ODM and Propel. See
 `FOSUserBundle on GitHub`_ for more information.
 

Resources/doc/reference/security.rst

@@ -8,7 +8,7 @@ By default, the SonataAdminBundle does not come with any user management,
 however it is most likely the application requires such a feature. The Sonata
 Project includes a ``SonataUserBundle`` which integrates the ``FOSUserBundle``.
 
-The ``FOSUserBundle`` adds support for a database-backed user system in Symfony2.
+The ``FOSUserBundle`` adds support for a database-backed user system in Symfony.
 It provides a flexible framework for user management that aims to handle common
 tasks such as user login, registration and password retrieval.
 
@@ -36,7 +36,7 @@ The security part is managed by a ``SecurityHandler``, the bundle comes with 3 h
 - ``sonata.admin.security.handler.role``: ROLES to handle permissions
 - ``sonata.admin.security.handler.acl``: ACL and ROLES to handle permissions
 - ``sonata.admin.security.handler.noop``: always returns true, can be used
-  with the Symfony2 firewall
+  with the Symfony firewall
 
 The default value is ``sonata.admin.security.handler.noop``, if you want to
 change the default value you can set the ``security_handler`` to
@@ -204,7 +204,7 @@ Yon can also create your own permissions, for example ``EMAIL``
 Going further
 ~~~~~~~~~~~~~
 
-Because Sonata role handler supplements Symfony2 security, but does not override it, you are free to do more advanced operations.
+Because Sonata role handler supplements Symfony security, but does not override it, you are free to do more advanced operations.
 For example, you can `create your own voter`_
 
 Customizing the handler behavior