From 2e77e290673811c75d48e13a150ac124bb6e4644 Mon Sep 17 00:00:00 2001 From: sr972 Date: Fri, 25 Jul 2014 08:09:54 +0200 Subject: [PATCH 1/2] Update doctrine.rst In 'Deleting an Object' you are not going to delete the entity itself but the given object. --- book/doctrine.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/doctrine.rst b/book/doctrine.rst index ad681d971a4..84a54b49017 100644 --- a/book/doctrine.rst +++ b/book/doctrine.rst @@ -699,7 +699,7 @@ method of the entity manager:: $em->flush(); As you might expect, the ``remove()`` method notifies Doctrine that you'd -like to remove the given entity from the database. The actual ``DELETE`` query, +like to remove the given object from the database. The actual ``DELETE`` query, however, isn't actually executed until the ``flush()`` method is called. .. _`book-doctrine-queries`: From 2512efbe8722fd8c06d4b271a9c44e2513d834d9 Mon Sep 17 00:00:00 2001 From: Daniel Santana Date: Fri, 25 Jul 2014 13:36:14 -0400 Subject: [PATCH 2/2] eraseCredentials method typo --- cookbook/security/entity_provider.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cookbook/security/entity_provider.rst b/cookbook/security/entity_provider.rst index 352427eb64e..80e0b08270b 100644 --- a/cookbook/security/entity_provider.rst +++ b/cookbook/security/entity_provider.rst @@ -194,7 +194,7 @@ interface forces the class to implement the five following methods: * :method:`Symfony\\Component\\Security\\Core\\User\\UserInterface::getPassword` * :method:`Symfony\\Component\\Security\\Core\\User\\UserInterface::getSalt` * :method:`Symfony\\Component\\Security\\Core\\User\\UserInterface::getUsername` -* :method:`Symfony\\Component\\Security\\Core\\User\\UserInterface::eraseCredential` +* :method:`Symfony\\Component\\Security\\Core\\User\\UserInterface::eraseCredentials` For more details on each of these, see :class:`Symfony\\Component\\Security\\Core\\User\\UserInterface`.