Fixed some typos

cookbook/security/voters.rst

@@ -92,7 +92,6 @@ the security layer. This can be done easily through the service container.
     methods in your implementation of the ``vote()`` method and return ``ACCESS_ABSTAIN``
     if your voter does not support the class or attribute.
 
-
 .. tip::
 
     An
@@ -204,8 +203,8 @@ application configuration file with the following code.
 That's it! Now, when deciding whether or not a user should have access,
 the new voter will deny access to any user in the list of blacklisted IPs.
 
-Note that the voters are only called, if any access is actually checked. So 
-you need at least something like 
+Note that the voters are only called, if any access is actually checked. So
+you need at least something like
 
 .. configuration-block::
 

cookbook/security/voters_data_permission.rst

@@ -117,13 +117,13 @@ To recap, here's what's expected from the three abstract methods:
 
 :method:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\AbstractVoter::getSupportedClasses`
     It tells Symfony that your voter should be called whenever an object of one
-    of the given classes is passed to ``isGranted()``  For example, if you return
+    of the given classes is passed to ``isGranted()``. For example, if you return
     ``array('AppBundle\Model\Product')``, Symfony will call your voter when a
     ``Product`` object is passed to ``isGranted()``.
 
 :method:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\AbstractVoter::getSupportedAttributes`
     It tells Symfony that your voter should be called whenever one of these
-    strings is passes as the first argument to ``isGranted()``. For example, if
+    strings is passed as the first argument to ``isGranted()``. For example, if
     you return ``array('CREATE', 'READ')``, then Symfony will call your voter
     when one of these is passed to ``isGranted()``.