fixing doc roles

symfony · Mar 13, 2014 · c7f2ee6 · c7f2ee6
1 parent 5d4a3a4
commit c7f2ee6
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/components/security/authentication.rst b/components/security/authentication.rst
@@ -204,7 +204,7 @@ own, it just needs to follow these rules:
    :method:`Symfony\\Component\\Security\\Core\\Encoder\\PasswordEncoderInterface::isPasswordValid`
    must first of all make sure the password is not too long, i.e. the password length is no longer
    than 4096 characters. This is for security reasons (see `CVE-2013-5750`_), and you can use the
-   :method:`Symfony\\Component\\Security\\Core\\Encoder\\BasePasswordEncoder::isPasswordTooLong`_
+   :method:`Symfony\\Component\\Security\\Core\\Encoder\\BasePasswordEncoder::isPasswordTooLong`
    method for this check:
 
        use Symfony\Component\Security\Core\Exception\BadCredentialsException;

diff --git a/cookbook/email/cloud.rst b/cookbook/email/cloud.rst
@@ -7,7 +7,7 @@ How to use the Cloud to Send Emails
 Requirements for sending emails from a production system differ from your
 development setup as you don't want to be limited in the number of emails,
 the sending rate or the sender address. Thus,
-:doc:`using Gmail </cookbook/email/gmail>`_ or similar services is not an
+:doc:`using Gmail </cookbook/email/gmail>` or similar services is not an
 option. If setting up and maintaining your own reliable mail server causes
 you a headache there's a simple solution: Leverage the cloud to send your
 emails.