changes according to comments after PR + some other typos

Author: talitakz

book/from_flat_php_to_symfony2.rst

@@ -102,7 +102,7 @@ the code that prepares the HTML "presentation"::
     require 'templates/list.php';
 
 
-The HTML code is now stored in a separate file ``templates/list.php``, which
+The HTML code is now stored in a separate ``templates/list.php`` file, which
 is primarily an HTML file that uses a template-like PHP syntax:
 
 .. code-block:: html+php
@@ -458,7 +458,7 @@ into a ``vendor/`` directory:
 
 Beside downloading your dependencies, Composer generates a ``vendor/autoload.php`` file,
 which takes care of autoloading for all the files in the Symfony Framework as well as
-the files mentioned in the autoload section of your ``composer.json``.
+the files mentioned in the ``autoload`` section of your ``composer.json``.
 
 Core to Symfony's philosophy is the idea that an application's main job is
 to interpret each request and return a response. To this end, Symfony provides
@@ -726,7 +726,7 @@ And rewriting ``layout.html.php`` template in Twig would look like this:
 
 Twig is well-supported in Symfony. And while PHP templates will always
 be supported in Symfony, the many advantages of Twig will continue to
-be discussed. For more information, see the :doc:`templating chapter </book/templating>`.
+be discussed. For more information, see the :doc:`Templating chapter </book/templating>`.
 
 
 Where Symfony Delivers
@@ -776,7 +776,7 @@ Learn more from the Cookbook
 .. _`Composer`: https://getcomposer.org
 .. _`download Composer`: https://getcomposer.org/download/
 .. _`Symfony distribution`: https://github.com/symfony/symfony-standard
+.. _`Twig`: http://twig.sensiolabs.org
 .. _`Validator`: https://github.com/symfony/validator
 .. _`Varnish`: https://www.varnish-cache.org/
-.. _`KnpBundles.com`: http://knpbundles.com/
-.. _`Twig`: http://twig.sensiolabs.org
+.. _`KnpBundles.com`: http://knpbundles.com/

book/http_fundamentals.rst

@@ -41,6 +41,9 @@ Symfony is built from the ground up around that reality. Whether you realize
 it or not, HTTP is something you use every day. With Symfony, you'll learn
 how to master it.
 
+.. index::
+   single: HTTP; Request-response paradigm
+
 Step1: The Client Sends a Request
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -98,10 +101,10 @@ delete a specific blog entry, for example:
     but many of them are not widely used or supported. In reality, many
     modern browsers only support ``POST`` and ``GET`` in HTML forms. Various
     others are however supported in `XMLHttpRequest`_, as well as by Symfony's
-    :doc:`router </components/routing/introduction>`.
+    :doc:`Routing component </components/routing/introduction>`.
 
-In addition to the first line, an HTTP request invariably contains other
-lines of information called request headers. The headers can supply a wide
+In addition to the first line, a HTTP request invariably contains other
+lines of information called request **headers**. The headers can supply a wide
 range of information such as the host of the resource being requested (``Host``),
 the response formats the client accepts (``Accept``) and the application the
 client is using to make the request (``User-Agent``). Many other headers exist
@@ -252,17 +255,18 @@ have all the request information at your fingertips::
 ``Request`` class has several public properties via which we can access information
 about the client request. As seen above, the ``$_GET`` and ``$_POST`` PHP global
 variables are accessible via the public ``query`` and ``request`` properties
-respectively, ``$_COOKIE`` is accessible via ``cookies``, ``$_FILES`` via ``files``
-and ``$_SERVER`` via ``server``. ``headers`` property is mostly equivalent to
-a subset of ``$_SERVER`` (e.g. $request->headers->get('User-Agent')). Each property is a
+respectively, ``$_COOKIE`` is accessible via ``cookies`` property, ``$_FILES``
+via ``files`` property and ``$_SERVER`` via ``server`` property. ``headers``
+property is mostly equivalent to a subset of ``$_SERVER``
+(e.g. $request->headers->get('User-Agent')). Each property is a
 :class:`Symfony\\Component\\HttpFoundation\\ParameterBag` instance (or a sub-class
 of: :class:`Symfony\\Component\\HttpFoundation\\ServerBag`,
 :class:`Symfony\\Component\\HttpFoundation\\FileBag`,
-:class:`Symfony\\Component\\HttpFoundation\\HeaderBag`,
+:class:`Symfony\\Component\\HttpFoundation\\HeaderBag`
 ), which is a data holder class. All ``ParameterBag`` instances have methods to
 retrieve and update their data like: ``get()`` to return a parameter by name,
 ``has()`` to return true if the parameter is defined, ``all()`` to return all
-the parameters and many more...
+the parameters and many more.
 
 .. _book-fundamentals-attributes:
 
@@ -438,7 +442,7 @@ the same simple pattern for every request:
    :align: center
    :alt: Symfony request flow
 
-   Incoming requests are interpreted by the :doc:`router component </book/routing>` and
+   Incoming requests are interpreted by the :doc:`Routing component </book/routing>` and
    passed to PHP functions that return ``Response`` objects.
 
 Each "page" of your site is defined in a routing configuration file that
@@ -509,7 +513,7 @@ When someone visits the ``/contact`` page, this route is matched, and the
 specified controller is executed. As you'll learn in the
 :ref:`routing chapter <controller-string-syntax>`, the ``AppBundle:Main:contact``
 string is a short syntax named *logical controller name* that points to a specific
-controller ``contactAction()`` inside a controller class called ``MainController)+``.
+controller ``contactAction()`` inside a controller class called ``MainController``.
 In the routing chapter you will also learn about routing parameters like
 ``_controller``, ``_route`` and the ``defaults`` array.
 
@@ -529,13 +533,13 @@ object with the HTML ``<h1>Contact us!</h1>``::
         }
     }
 
-In the :doc:`controller chapter </book/controller>`, you'll learn how a controller can
+In the :doc:`Controller chapter </book/controller>`, you'll learn how a controller can
 render templates, allowing your "presentation" code (i.e. anything that actually
 writes out HTML) to live in a separate template file. This frees up the controller
 to worry only about the hard stuff: interacting with the database, handling
 submitted data, or sending email messages.
 
--.. _symfony2-build-your-app-not-your-tools:
+.. _symfony2-build-your-app-not-your-tools:
 
 Symfony: Build your App, not your Tools
 ---------------------------------------

book/installation.rst

@@ -158,6 +158,8 @@ version as the second argument of the ``create-project`` Composer command::
     doing anything. If that's your case, add the ``-vvv`` flag to the previous
     command to display a detailed output of everything that Composer is doing.
 
+    $ composer create-project -vvv symfony/framework-standard-edition my_project_name "2.3.*"
+
 Running the Symfony Application
 -------------------------------
 
@@ -445,10 +447,10 @@ a wide variety of articles about solving specific problems with Symfony.
 .. _`Apache`: http://httpd.apache.org/docs/current/mod/core.html#documentroot
 .. _`Nginx`: http://wiki.nginx.org/Symfony
 .. _`enable ACL support`: https://help.ubuntu.com/community/FilePermissionsACLs
+.. _`Git`: http://git-scm.com/
 .. _`Symfony Standard Edition`: https://github.com/symfony/symfony-standard
 .. _`Symfony CMF Standard Edition`: https://github.com/symfony-cmf/symfony-cmf-standard
 .. _`Symfony CMF`: http://cmf.symfony.com/
 .. _`CMS`: https://en.wikipedia.org/wiki/Content_management_system
 .. _`Symfony REST Edition`: https://github.com/gimler/symfony-rest-edition
 .. _`FOSRestBundle`: https://github.com/FriendsOfSymfony/FOSRestBundle
-.. _`Git`: http://git-scm.com/

book/page_creation.rst

@@ -33,7 +33,7 @@ Creating a Page: Route and Controller
     :doc:`Installation </book/installation>` chapter, installed
     `Symfony Standard Edition`_ and can access your new Symfony app in the
     browser either using PHP's internal web server or by setting proper
-    virtual host in Apache or Nginx replace.
+    virtual host in Apache or Nginx.
 
     Using PHP's internal web server is only suitable while developing the
     application. In order to run Symfony applications on production servers,
@@ -121,7 +121,7 @@ If you see a lucky number being printed back to you, congratulations! But before
 you run off to play the lottery, check out how this works.
 
 The ``@Route`` above ``numberAction()`` method is called an :term:`annotation`
-and defines the route so that :doc:`router </book/routing>` can match the incoming URL
+and defines the route so that :doc:`Router </book/routing>` can match the incoming URL
 (``http://localhost:8000/lucky/number``) to a specific route (``/lucky/number``)
 and therefore returns information about the route, including the controller method
 that should be executed. The correct controller from the matched route is executed
@@ -131,7 +131,7 @@ object.
 .. note::
 
     You can also write routes in YAML, XML or PHP: you will learn about
-    this in the :doc:`routing </book/routing>` chapter. If you look closer
+    this in the :doc:`Routing </book/routing>` chapter. If you look closer
     the above example has tabs that show you how each format looks - all three additional
     formats use routing configuration file to define routes. Actually, most
     routing examples in the docs have tabs that show you how each format looks.
@@ -485,20 +485,14 @@ which you'll use to enable new bundles (and one of a *very* short list of
 PHP files in ``app/``).
 
 The ``src/`` directory has just one directory ``src/AppBundle`` and everything
-lives inside of it.  Is where your code lives.
-Symfony Standard Edition comes with ``AppBundle`` but there is nothing special about
-``AppBundle``. Your project can have as many bundles as you want, you can even use
-bundles written bay other
-
-The ``src/`` directory has just one directory ``src/AppBundle`` and everything
-lives inside of it. Is where your code lives. It's a set of files within a
+lives inside of it.  Is where your code lives. It's a set of files within a
 directory that implement a single feature. Symfony Standard Edition comes with
 ``AppBundle`` but there is nothing special about ``AppBundle``. Your project can
-have as many bundles as you want, you can even use third-party bundles that you can
-find at `KnpBundles.com`_. So, a :term:`bundle` is like a "plugin" in other software,
-but even better. To find out more about bundles and why you might create multiple
-bundles (hint: sharing code between projects), see the :doc:`Bundles </book/bundles>`
-chapter.
+have as many bundles as you want, you can even use third-party bundles written
+by other that you can find at `KnpBundles.com`_. So, a :term:`bundle` is like a
+"plugin" in other software, but even better. To find out more about bundles and
+why you might create multiple bundles (hint: sharing code between projects), see
+the :doc:`Bundles </book/bundles>` chapter.
 
 So what about the other directories in the project?
 
@@ -514,7 +508,8 @@ So what about the other directories in the project?
 .. seealso::
 
     Symfony is flexible. If you need to, you can easily override the default
-    directory structure. See :doc:`/cookbook/configuration/override_dir_structure`.
+    directory structure. See cookbook article
+    :doc:`/cookbook/configuration/override_dir_structure`.
 
 Application Configuration
 -------------------------