Merge pull request #204 from qpleple/doc

Documentation update

Resources/doc/reference/form_field_definition.rst

@@ -112,13 +112,11 @@ display a ``User`` field.
 
 The AdminBundle provides 3 edit options:
 
- - ``standard``: default value, the user list is set in a select widget
- - ``list``: the user list is set in a model where you can search and select a user
+ - ``standard``: default value, the ``User`` list is set in a select widget
+ - ``list``: the ``User`` list is set in a model where you can search and select a user
+ - ``inline``: embed the ``User`` form into the ``Post`` form, great for one-to-one, or if your want to allow the user to edit the ``User`` information.
 
-In both case, you can create a new ``User`` by clicking on the "+" icon.
-
-The last option, is ``inline`` this option embed the ``User`` form into the ``Post`` Form. This option is
-great for one-to-one, or if your want to allow the user to edit the ``User`` information.
+With the ``standard`` and ``list`` options, you can create a new ``User`` by clicking on the "+" icon.
 
 .. code-block:: php
 

Resources/doc/reference/saving_hooks.rst

@@ -42,7 +42,7 @@ is how the Admin bundle can be used to solve the issue by using the ``prePersist
             'groups'
         );
 
-        public function prePersist($user)
+        public function preUpdate($user)
         {
             $this->getUserManager()->updateCanonicalFields($user);
             $this->getUserManager()->updatePassword($user);