fix Composer notation

Author: bicpi

book/installation.rst

@@ -180,7 +180,7 @@ Symfony itself - into the ``vendor/`` directory.
 .. tip::
 
     When running ``php composer.phar install`` or ``php composer.phar update``,
-    composer will execute post install/update commands to clear the cache
+    Composer will execute post install/update commands to clear the cache
     and install assets. By default, the assets will be copied into your ``web``
     directory.
 

cookbook/bundles/installation.rst

@@ -13,7 +13,7 @@ Add Composer Dependencies
 Starting from Symfony 2.1, dependencies are managed with Composer. It's
 a good idea to learn some basics of Composer in `their documentation`_.
 
-Before you can use composer to install a bundle, you should look for a
+Before you can use Composer to install a bundle, you should look for a
 `Packagist`_ package of that bundle. For example, if you search for the popular
 `FOSUserBundle`_ you will find a packaged called `friendsofsymfony/user-bundle`_.
 

cookbook/form/unit_testing.rst

@@ -23,8 +23,8 @@ It is used to test the core types and you can use it to test your types too.
 .. note::
 
     Depending on the way you installed your Symfony or Symfony Form Component
-    the tests may not be downloaded. Use the --prefer-source option with
-    composer if this is the case.
+    the tests may not be downloaded. Use the ``--prefer-source`` option with
+    Composer if this is the case.
 
 The Basics
 ----------

cookbook/workflow/_vendor_deps.rst.inc

@@ -1,5 +1,5 @@
-Managing Vendor Libraries with composer.json
---------------------------------------------
+Managing Vendor Libraries with ``composer.json``
+------------------------------------------------
 
 How does it work?
 ~~~~~~~~~~~~~~~~~

cookbook/workflow/new_project_git.rst

@@ -69,7 +69,7 @@ git repository:
         $ git commit -m "Initial commit"
 
 8. Finally, download all of the third-party vendor libraries by
-   executing composer. For details, see :ref:`installation-updating-vendors`.
+   executing Composer. For details, see :ref:`installation-updating-vendors`.
 
 At this point, you have a fully-functional Symfony2 project that's correctly
 committed to Git. You can immediately begin development, committing the new
@@ -95,7 +95,7 @@ Instead of using the ``composer.json`` system for managing your vendor
 libraries, you may instead choose to use native `git submodules`_. There
 is nothing wrong with this approach, though the ``composer.json`` system
 is the official way to solve this problem and probably much easier to
-deal with. Unlike Git submodules, ``Composer`` is smart enough to calculate
+deal with. Unlike Git submodules, Composer is smart enough to calculate
 which libraries depend on which other libraries.
 
 Storing your Project on a Remote Server

cookbook/workflow/new_project_svn.rst

@@ -101,7 +101,7 @@ To get started, you'll need to download Symfony2 and get the basic Subversion se
    developing.
 
 8. Finally, download all of the third-party vendor libraries by
-   executing composer. For details, see :ref:`installation-updating-vendors`.
+   executing Composer. For details, see :ref:`installation-updating-vendors`.
 
 .. tip::