Merge pull request #3590 from pborreli/typos

Fixed typos

Form/FormMapper.php

@@ -178,7 +178,7 @@ class FormMapper extends BaseGroupedMapper
      *
      * @param string $group          The group to delete
      * @param string $tab            The tab the group belongs to, defaults to 'default'
-     * @param bool   $deleteEmptyTab Wether or not the Tab should be deleted, when the deleted group leaves the tab emmpty after deletion
+     * @param bool   $deleteEmptyTab Whether or not the Tab should be deleted, when the deleted group leaves the tab empty after deletion
      */
     public function removeGroup($group, $tab = 'default', $deleteEmptyTab = false)
     {

Resources/doc/cookbook/recipe_custom_action.rst

@@ -112,7 +112,7 @@ to implement a ``clone`` action.
 
             return new RedirectResponse($this->admin->generateUrl('list'));
 
-            // if you have a filtererd list and want to keep your filters after the redirect
+            // if you have a filtered list and want to keep your filters after the redirect
             // return new RedirectResponse($this->admin->generateUrl('list', $this->admin->getFilterParameters()));
         }
     }

Resources/doc/cookbook/recipe_select2.rst

@@ -59,7 +59,7 @@ to enable ``allowClear`` or ``data-sonata-select2-allow-clear = "false"`` to dis
 
     public function configureFormFields(FormMapper $formMapper)
     {
-        $formMaper
+        $formMapper
             ->add('category', 'sonata_type_model', array(
                 'attr' => array(
                     'data-sonata-select2-allow-clear' => 'false'

Resources/doc/cookbook/recipe_sortable_listing.rst

@@ -178,7 +178,7 @@ also define the sort by field to be position:
 
 .. note::
 
-   To avoid pitfalls, do not rename ``$last_postion`` to ``$lastPostion``, as ``$last_postion`` is used directly in the template.
+   To avoid pitfalls, do not rename ``$last_position`` to ``$lastPosition``, as ``$last_position`` is used directly in the template.
 
 And add the following call the ``admin.yml``
 

Resources/doc/getting_started/the_list_view.rst

@@ -117,14 +117,14 @@ category.
 Adding Filter/Search Options
 ----------------------------
 
-Assume you had a very succesfull blog site containing many blog posts. After a
+Assume you had a very successful blog site containing many blog posts. After a
 while, finding the blog post you wanted to edit would be like finding a needle
 in a haystack. As with all user experience problems, Sonata provides a solution
 for it!
 
 It does this by allowing you to configure datagrid filters in the
 ``Admin#configureDatagridFilters()`` method. For instance, to allow the admin
-to search blog posts by title (and also order them by alfabet in the list), you
+to search blog posts by title (and also order them by alphabet in the list), you
 would do something like:
 
 .. code-block:: php

Resources/doc/reference/action_list.rst

@@ -510,7 +510,7 @@ To do:
 Visual configuration
 --------------------
 
-You have the possibility to configure your List View to customize the render without overring to whole template.
+You have the possibility to configure your List View to customize the render without overriding to whole template.
 You can :
 
 - `header_style`: Customize the style of header (width, color, background, align...)

Resources/doc/reference/dashboard.rst

@@ -38,7 +38,7 @@ The ``Admin`` list block
 ------------------------
 
 The ``Admin`` list is a ``Block`` that fetches information from the ``Admin`` service's
-``Pool`` and prints it in the nicely formated list you have on your default Dashboard.
+``Pool`` and prints it in the nicely formatted list you have on your default Dashboard.
 The ``Admin`` list is defined by the ``sonata.admin.block.admin_list`` service, which is
 implemented by the ``Block\AdminListBlockService`` class. It is then rendered using the
 ``SonataAdminBundle:Block:block_admin_list.html.twig`` template file.
@@ -53,7 +53,7 @@ As you probably noticed by now, the ``Admin`` list groups ``Admin`` mappings tog
 There are several ways in which you can configure these groups.
 
 By default the admins are ordered the way you defined them. With the setting ``sort_admins``
-groups and admins will be orderd by their respective label with a fallback to the admin id.
+groups and admins will be ordered by their respective label with a fallback to the admin id.
 
 Using the ``Admin`` service declaration
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -339,7 +339,7 @@ The layout is as follows:
 
     BOTTOM BOTTOM BOTTOM
 
-On ``top`` and ``bottom`` positions, you can also specify an optionnal ``class`` option to set the width of the block.
+On ``top`` and ``bottom`` positions, you can also specify an optional ``class`` option to set the width of the block.
 
 .. configuration-block::
 

Resources/doc/reference/form_help_message.rst

@@ -97,7 +97,7 @@ This Extension for example adds a note field to some entities which use a custom
     class NoteAdminExtension extends AdminExtension
     {
 
-        // add this field to the datagrid everytime its available
+        // add this field to the datagrid every time its available
         /**
          * @param DatagridMapper $datagridMapper
          */

Resources/doc/reference/translation.rst

@@ -13,7 +13,7 @@ other Admin classes.
 
 You have two options to configure the catalogue for the Admin class:
 
-* overrride the ``$translationDomain`` property
+* override the ``$translationDomain`` property
 
   .. code-block:: php