symfony · weaverryan · May 26, 2013 · May 23, 2013
diff --git a/components/config/definition.rst b/components/config/definition.rst
@@ -387,7 +387,7 @@ and sometimes only:
 
 By default ``connection`` would be an array in the first case and a string
 in the second making it difficult to validate. You can ensure it is always
-an array with with ``fixXmlConfig``.
+an array with ``fixXmlConfig``.
 
 You can further control the normalization process if you need to. For example,
 you may want to allow a string to be set and used as a particular key or several

diff --git a/components/event_dispatcher/container_aware_dispatcher.rst b/components/event_dispatcher/container_aware_dispatcher.rst
@@ -59,7 +59,7 @@ Adding Subscriber Services
 ``EventSubscribers`` can be added using the
 :method:`Symfony\\Component\\EventDispatcher\\ContainerAwareEventDispatcher::addSubscriberService`
 method where the first argument is the service ID of the subscriber service,
-and the second argument is the the service's class name (which must implement
+and the second argument is the service's class name (which must implement
 :class:`Symfony\\Component\\EventDispatcher\\EventSubscriberInterface`) as follows::
 
     $dispatcher->addSubscriberService(

diff --git a/cookbook/console/sending_emails.rst b/cookbook/console/sending_emails.rst
@@ -6,7 +6,7 @@ How to generate URLs and send Emails from the Console
 =====================================================
 
 Unfortunately, the command line context does not know about your VirtualHost
-or domain name. This means that if if you generate absolute URLs within a
+or domain name. This means that if you generate absolute URLs within a
 Console Command you'll probably end up with something like ``http://localhost/foo/bar``
 which is not very useful.
 

diff --git a/cookbook/deployment-tools.rst b/cookbook/deployment-tools.rst
@@ -23,7 +23,7 @@ The typical steps taken while deploying a Symfony2 application include:
 
 A deployment may also include other things, such as:
 
-* Tagging a particular version of of your code as a release in your source control repository;
+* Tagging a particular version of your code as a release in your source control repository;
 * Creating a temporary staging area to build your updated setup "offline";
 * Running any tests available to ensure code and/or server stability;
 * Removal of any unnecessary files from ``web`` to keep your production environment clean;

diff --git a/reference/constraints/Collection.rst b/reference/constraints/Collection.rst
@@ -226,7 +226,7 @@ field is optional but must be a valid email if supplied, you can do the followin
 
 Even without ``allowMissingFields`` set to true, you can now omit the ``alternate_email``
 property completely from the ``profileData`` array, since it is ``Optional``.
-However, if the the ``personal_email`` field does not exist in the array,
+However, if the ``personal_email`` field does not exist in the array,
 the ``NotBlank`` constraint will still be applied (since it is wrapped in
 ``Required``) and you will receive a constraint violation.
 

diff --git a/reference/constraints/Length.rst b/reference/constraints/Length.rst
@@ -39,7 +39,7 @@ To verify that the ``firstName`` field length of a class is between "2" and
                         min: 2
                         max: 50
                         minMessage: "Your first name must be at least {{ limit }} characters length"
-                        maxMessage: "Your first name cannot be longer than than {{ limit }} characters length"
+                        maxMessage: "Your first name cannot be longer than {{ limit }} characters length"
 
     .. code-block:: php-annotations
 
@@ -55,7 +55,7 @@ To verify that the ``firstName`` field length of a class is between "2" and
              *      min = "2",
              *      max = "50",
              *      minMessage = "Your first name must be at least {{ limit }} characters length",
-             *      maxMessage = "Your first name cannot be longer than than {{ limit }} characters length"
+             *      maxMessage = "Your first name cannot be longer than {{ limit }} characters length"
              * )
              */
              protected $firstName;
@@ -70,7 +70,7 @@ To verify that the ``firstName`` field length of a class is between "2" and
                     <option name="min">2</option>
                     <option name="max">50</option>
                     <option name="minMessage">Your first name must be at least {{ limit }} characters length</option>
-                    <option name="maxMessage">Your first name cannot be longer than than {{ limit }} characters length</option>
+                    <option name="maxMessage">Your first name cannot be longer than {{ limit }} characters length</option>
                 </constraint>
             </property>
         </class>
@@ -91,7 +91,7 @@ To verify that the ``firstName`` field length of a class is between "2" and
                     'min'        => 2,
                     'max'        => 50,
                     'minMessage' => 'Your first name must be at least {{ limit }} characters length',
-                    'maxMessage' => 'Your first name cannot be longer than than {{ limit }} characters length',
+                    'maxMessage' => 'Your first name cannot be longer than {{ limit }} characters length',
                 )));
             }
         }
@@ -121,7 +121,7 @@ charset
 **type**: ``string``  **default**: ``UTF-8``
 
 The charset to be used when computing value's length. The :phpfunction:`grapheme_strlen` PHP
-function is used if available. If not, the the :phpfunction:`mb_strlen` PHP function
+function is used if available. If not, the :phpfunction:`mb_strlen` PHP function
 is used if available. If neither are available, the :phpfunction:`strlen` PHP function
 is used.