minor #7147 Some minor tweaks related to Doctrine docs (bocharsky-bw)

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

Discussion
----------

Some minor tweaks related to Doctrine docs

Commits
-------

d048d98 Some minor tweaks related to Doctrine docs

Author: xabbuh

doctrine/event_listeners_subscribers.rst

@@ -122,7 +122,7 @@ Creating the Listener Class
 
 In the previous example, a service ``my.listener`` was configured as a Doctrine
 listener on the event ``postPersist``. The class behind that service must have
-a ``postPersist`` method, which will be called when the event is dispatched::
+a ``postPersist()`` method, which will be called when the event is dispatched::
 
     // src/AppBundle/EventListener/SearchIndexer.php
     namespace AppBundle\EventListener;

doctrine/mapping_model_classes.rst

@@ -96,7 +96,7 @@ be adapted for your case::
         }
     }
 
-Note the :phpfunction:`class_exists` check. This is crucial, as you do not want your
+Note the :phpfunction:`class_exists()` check. This is crucial, as you do not want your
 bundle to have a hard dependency on all Doctrine bundles but let the user
 decide which to use.
 

doctrine/registration_form.rst

@@ -120,6 +120,11 @@ With some validation added, your class may look something like this::
             $this->plainPassword = $password;
         }
 
+        public function getPassword()
+        {
+            return $this->password;
+        }
+
         public function setPassword($password)
         {
             $this->password = $password;
@@ -180,8 +185,8 @@ Next, create the form for the ``User`` entity::
                     'type' => 'password',
                     'first_options'  => array('label' => 'Password'),
                     'second_options' => array('label' => 'Repeat Password'),
-                )
-            );
+                ))
+            ;
         }
 
         public function configureOptions(OptionsResolver $resolver)

doctrine/resolve_target_entity.rst

@@ -39,9 +39,9 @@ brevity) to explain how to set up and use the ``ResolveTargetEntityListener``.
 
 A Customer entity::
 
-    // src/Acme/AppBundle/Entity/Customer.php
+    // src/AppBundle/Entity/Customer.php
 
-    namespace Acme\AppBundle\Entity;
+    namespace AppBundle\Entity;
 
     use Doctrine\ORM\Mapping as ORM;
     use Acme\CustomerBundle\Entity\Customer as BaseCustomer;
@@ -118,7 +118,7 @@ about the replacement:
             orm:
                 # ...
                 resolve_target_entities:
-                    Acme\InvoiceBundle\Model\InvoiceSubjectInterface: Acme\AppBundle\Entity\Customer
+                    Acme\InvoiceBundle\Model\InvoiceSubjectInterface: AppBundle\Entity\Customer
 
     .. code-block:: xml
 
@@ -132,7 +132,7 @@ about the replacement:
             <doctrine:config>
                 <doctrine:orm>
                     <!-- ... -->
-                    <doctrine:resolve-target-entity interface="Acme\InvoiceBundle\Model\InvoiceSubjectInterface">Acme\AppBundle\Entity\Customer</doctrine:resolve-target-entity>
+                    <doctrine:resolve-target-entity interface="Acme\InvoiceBundle\Model\InvoiceSubjectInterface">AppBundle\Entity\Customer</doctrine:resolve-target-entity>
                 </doctrine:orm>
             </doctrine:config>
         </container>
@@ -144,7 +144,7 @@ about the replacement:
             'orm' => array(
                 // ...
                 'resolve_target_entities' => array(
-                    'Acme\InvoiceBundle\Model\InvoiceSubjectInterface' => 'Acme\AppBundle\Entity\Customer',
+                    'Acme\InvoiceBundle\Model\InvoiceSubjectInterface' => 'AppBundle\Entity\Customer',
                 ),
             ),
         ));