Browse Source

CS fixes, typos

Peter Kokot 11 years ago
parent
commit
3c2fdb2784

+ 4 - 4
Resources/doc/reference/architecture.rst

@@ -107,7 +107,7 @@ The ``CRUDController`` is no different to any other Symfony2 controller, meaning
 that you have all the usual options available to you, like getting services from
 the Dependency Injection Container (DIC).
 
-This is particulary useful if you decide to extend the ``CRUDController`` to
+This is particularly useful if you decide to extend the ``CRUDController`` to
 add new actions or change the behavior of existing ones. You can specify which controller
 to use when declaring the ``Admin`` service by passing it as the 3rd argument. For example
 to set the controller to ``AcmeDemoBundle:PostAdmin``:
@@ -167,7 +167,7 @@ which stores instances of ``FieldDescriptionInterface``. Picking up on our previ
 
    class PostAdmin extends Admin
    {
-       //Fields to be shown on create/edit forms
+       // Fields to be shown on create/edit forms
        protected function configureFormFields(FormMapper $formMapper)
        {
            $formMapper
@@ -177,7 +177,7 @@ which stores instances of ``FieldDescriptionInterface``. Picking up on our previ
            ;
        }
 
-       //Fields to be shown on filter forms
+       // Fields to be shown on filter forms
        protected function configureDatagridFilters(DatagridMapper $datagridMapper)
        {
            $datagridMapper
@@ -186,7 +186,7 @@ which stores instances of ``FieldDescriptionInterface``. Picking up on our previ
            ;
        }
 
-       //Fields to be shown on lists
+       // Fields to be shown on lists
        protected function configureListFields(ListMapper $listMapper)
        {
            $listMapper

+ 1 - 1
Resources/doc/reference/form_types.rst

@@ -173,7 +173,7 @@ to the underlying forms.
         {
             $formMapper
                 ->add('sales', 'sonata_type_collection', array(
-                    //Prevents the "Delete" option from being displayed
+                    // Prevents the "Delete" option from being displayed
                     'type_options' => array('delete' => false)
                 ), array(
                     'edit' => 'inline',

+ 3 - 3
Resources/doc/reference/getting_started.rst

@@ -76,7 +76,7 @@ for it could look like:
 
    class PostAdmin extends Admin
    {
-       //Fields to be shown on create/edit forms
+       // Fields to be shown on create/edit forms
        protected function configureFormFields(FormMapper $formMapper)
        {
            $formMapper
@@ -86,7 +86,7 @@ for it could look like:
            ;
        }
 
-       //Fields to be shown on filter forms
+       // Fields to be shown on filter forms
        protected function configureDatagridFilters(DatagridMapper $datagridMapper)
        {
            $datagridMapper
@@ -95,7 +95,7 @@ for it could look like:
            ;
        }
 
-       //Fields to be shown on lists
+       // Fields to be shown on lists
        protected function configureListFields(ListMapper $listMapper)
        {
            $listMapper

+ 5 - 5
Resources/doc/reference/installation.rst

@@ -60,18 +60,18 @@ forget to enable SonataAdminBundle too:
         return array(
             // ...
 
-            //Add you dependencies
+            // Add you dependencies
             new Sonata\BlockBundle\SonataBlockBundle(),
             new Sonata\jQueryBundle\SonatajQueryBundle(),
             new Knp\Bundle\MenuBundle\KnpMenuBundle(),
             //...
 
-            //If you haven't already, add the storage bundle
-            //This example uses SonataDoctrineORMAdmin but
-            //it works the same with the alternatives
+            // If you haven't already, add the storage bundle
+            // This example uses SonataDoctrineORMAdmin but
+            // it works the same with the alternatives
             new Sonata\DoctrineORMAdminBundle\SonataDoctrineORMAdminBundle(),
 
-            //Then add SonataAdminBundle
+            // Then add SonataAdminBundle
             new Sonata\AdminBundle\SonataAdminBundle(),
             // ...
         );

+ 2 - 2
Resources/doc/reference/routing.rst

@@ -211,7 +211,7 @@ the ``clearExcept()`` method. This method accepts an array of routes you want to
     {
         protected function configureRoutes(RouteCollection $collection)
         {
-            //Only `list` and `edit` route will be active
+            // Only `list` and `edit` route will be active
             $collection->clearExcept(array('list', 'edit'));
         }
     }
@@ -230,7 +230,7 @@ If you want to remove all default routes, you can use ``clear()`` method.
     {
         protected function configureRoutes(RouteCollection $collection)
         {
-            //All routes are removed
+            // All routes are removed
             $collection->clear();
         }
     }

+ 1 - 1
Resources/doc/reference/security.rst

@@ -662,7 +662,7 @@ User list customization
 By default, the ACL editor allows to set permissions for all users managed by
 ``FOSUserBundle``.
 
-To cutomize displayed user override
+To customize displayed user override
 `Sonata\AdminBundle\Controller\CRUDController::getAclUsers()`. This method must
 return an iterable collection of users.