diff --git a/cookbook/bundles/best_practices.rst b/cookbook/bundles/best_practices.rst
index 5e41d3b76d5..604f710105c 100644
--- a/cookbook/bundles/best_practices.rst
+++ b/cookbook/bundles/best_practices.rst
@@ -138,7 +138,7 @@ All classes and files must follow the Symfony2 coding :doc:`standards
 Some classes should be seen as facades and should be as short as possible, like
 Commands, Helpers, Listeners, and Controllers.
 
-Classes that connects to the Event Dispatcher should be suffixed with
+Classes that connect to the Event Dispatcher should be suffixed with
 ``Listener``.
 
 Exceptions classes should be stored in an ``Exception`` sub-namespace.
diff --git a/cookbook/bundles/extension.rst b/cookbook/bundles/extension.rst
index 70dd030b89b..1e06b734cbd 100644
--- a/cookbook/bundles/extension.rst
+++ b/cookbook/bundles/extension.rst
@@ -318,7 +318,7 @@ configuration based on some of the input values. For example, suppose you
 have a service who's first argument is some string "type" that it will use
 internally. You'd like this to be easily configured by the bundle user, so
 in your service configuration file (e.g. ``services.xml``), you define this
-service and use a blank parameter - ``acme_hello.my_service_options`` - as
+service and use a blank parameter - ``acme_hello.my_service_type`` - as
 its first argument:
 
 .. code-block:: xml
diff --git a/cookbook/form/simple_signup_form_with_mongodb.rst b/cookbook/form/simple_signup_form_with_mongodb.rst
index d048edecfea..de4cf635b93 100644
--- a/cookbook/form/simple_signup_form_with_mongodb.rst
+++ b/cookbook/form/simple_signup_form_with_mongodb.rst
@@ -234,7 +234,7 @@ controller for displaying the registration form::
         }
     }
 
-and it's template:
+and its template:
 
 .. code-block:: html+jinja
 
@@ -270,4 +270,4 @@ the validation and saves the data into MongoDB::
     }
 
 That's it! Your form now validates, and allows you to save the ``User``
-object to MongoDB.
\ No newline at end of file
+object to MongoDB.