[WIP] More changes

Author: weaverryan

book/installation.rst

@@ -28,7 +28,7 @@ ways.
 Linux and Mac OS X Systems
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Open your command console and execute the following commands::
+Open your command console and execute the following commands:
 
 .. code-block:: bash
 
@@ -40,14 +40,14 @@ This will create a global ``symfony`` command in your system.
 Windows Systems
 ~~~~~~~~~~~~~~~
 
-Open your command console and execute the following command::
+Open your command console and execute the following command:
 
 .. code-block:: bash
 
     c:\> php -r "readfile('https://symfony.com/installer');" > symfony
 
 Then, move the downloaded ``symfony`` file to your project's directory and
-execute it as follows::
+execute it as follows:
 
 .. code-block:: bash
 
@@ -60,7 +60,7 @@ Creating the Symfony Application
 --------------------------------
 
 Once the Symfony Installer is available, create your first Symfony application
-with the ``new`` command::
+with the ``new`` command:
 
 .. code-block:: bash
 
@@ -92,7 +92,7 @@ Basing your Project on a Specific Symfony Version
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 In case your project needs to be based on a specific Symfony version, use the
-optional second argument of the ``new`` command::
+optional second argument of the ``new`` command:
 
 .. code-block:: bash
 
@@ -109,7 +109,7 @@ optional second argument of the ``new`` command::
     $ symfony new my_project 2.7.0-RC1
 
 The installer also supports a special version called ``lts`` which installs the
-most recent :ref:`Symfony LTS version <releases-lts>` available::
+most recent :ref:`Symfony LTS version <releases-lts>` available:
 
 .. code-block:: bash
 
@@ -141,14 +141,14 @@ Creating a Symfony Application with Composer
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Once Composer is installed on your computer, execute the ``create-project`` Composer
-command to create a new Symfony application based on its latest stable version::
+command to create a new Symfony application based on its latest stable version:
 
 .. code-block:: bash
 
     $ composer create-project symfony/framework-standard-edition my_project_name
 
 If you need to base your application on a specific Symfony version, provide that
-version as the second argument of the ``create-project`` Composer command::
+version as the second argument of the ``create-project`` Composer command:
 
 .. code-block:: bash
 
@@ -160,14 +160,12 @@ 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
 -------------------------------
 
 Symfony leverages the internal web server provided by PHP to run applications
 while developing them. Therefore, running a Symfony application is a matter of
-browsing the project directory and executing this command::
+browsing the project directory and executing this command:
 
 .. code-block:: bash
 
@@ -187,16 +185,12 @@ possible solutions depending on your operating system. All of them are
 explained in the :ref:`Setting up Permissions <book-installation-permissions>`
 section of this chapter.
 
-Using PHP's internal web server is only suitable while developing the application.
-In order to run Symfony applications on production servers, you'll have to
-configure your `Apache`_ or `Nginx`_ web server and virtual host as explained in
-cookbook article :doc:`/cookbook/configuration/web_server_configuration`.
+PHP's internal web server is great for developing, but should **not** be used on
+production. Instead, use Apache or Nginx. See :doc:`/cookbook/configuration/web_server_configuration`.
 
 .. note::
 
-    PHP's internal web server is available in PHP 5.4 or higher versions. So, if you
-    still use the legacy PHP 5.3 version, you'll also have to configure `Apache`_ or
-    `Nginx`_ web server and virtual host.
+    PHP's internal web server is available in PHP 5.4 or higher versions.
 
 When you are finished working on your Symfony application, you can stop the
 server by pressing `Ctrl+C` from terminal.
@@ -206,7 +200,7 @@ Checking Symfony Application Configuration and Setup
 
 Symfony applications come with a visual server configuration tester to show if
 your environment is ready to use Symfony. Access the following URL to check your
-configuration::
+configuration:
 
 .. code-block:: text
 
@@ -301,7 +295,7 @@ and they are managed exclusively by Composer.
 
 Updating those third-party libraries frequently is a good practice to prevent bugs
 and security vulnerabilities. Execute the ``update`` Composer command to update
-them all at once::
+them all at once:
 
 .. code-block:: bash
 
@@ -311,6 +305,18 @@ them all at once::
 Depending on the complexity of your project, this update process can take up to
 several minutes to complete.
 
+.. tip::
+
+    Symfony provides a command to check whether your project's dependencies
+    contain any known security vulnerability:
+
+    .. code-block:: bash
+
+        $ php app/console security:check
+
+    A good security practice is to execute this command regularly to be able to
+    update or replace compromised dependencies as soon as possible.
+
 Installing the Symfony Demo Application
 ---------------------------------------
 
@@ -320,7 +326,7 @@ conceived as a learning tool for Symfony newcomers and its source code contains
 tons of comments and helpful notes.
 
 In order to download the Symfony Demo application, execute the ``demo`` command
-of the Symfony Installer anywhere in your system::
+of the Symfony Installer anywhere in your system:
 
 .. code-block:: bash
 
@@ -344,7 +350,7 @@ Symfony project packages "distributions", which are fully-functional application
 that include the Symfony core libraries, a selection of useful bundles, a
 sensible directory structure and some default configuration. In fact, when you
 created a Symfony application in the previous sections, you actually downloaded the
-default distribution provided by Symfony, which is called *`Symfony Standard Edition`_*.
+default distribution provided by Symfony, which is called `Symfony Standard Edition`_.
 
 The Symfony Standard Edition is by far the most popular distribution and it's
 also the best choice for developers starting with Symfony. However, the Symfony
@@ -353,25 +359,43 @@ applications:
 
 * The `Symfony CMF Standard Edition`_ is the best distribution to get started
   with the `Symfony CMF`_ project, which is a project that makes it easier for
-  developers to add `CMS`_ functionality to applications built with the Symfony
+  developers to add CMS functionality to applications built with the Symfony
   Framework.
 * The `Symfony REST Edition`_ shows how to build an application that provides a
   RESTful API using the `FOSRestBundle`_ and several other related bundles.
 
-Configuration Formats
----------------------
+Using Source Control
+--------------------
+
+If you're using a version control system like `Git`_, you can safely commit all
+your project's code. The reason is that Symfony applications already contain a
+``.gitignore`` file specially prepared for Symfony.
+
+For specific instructions on how best to set up your project to be stored
+in Git, see :doc:`/cookbook/workflow/new_project_git`.
+
+Checking out a versioned Symfony Application
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When using Composer to manage application's dependencies, it's recommended to
+ignore the entire ``vendor/`` directory before committing its code to the
+repository. This means that when checking out a Symfony application from a Git
+repository, there will be no ``vendor/`` directory and the application won't
+work out-of-the-box.
 
-Symfony supports several configuration formats: YAML, XML and PHP. Throughout
-the chapters, all configuration examples will be shown in all three formats.
-Each has its own advantages and disadvantages. The choice of which to use is up
-to you:
+In order to make it work, check out the Symfony application and then execute the
+``install`` Composer command to download and install all the dependencies required
+by the application:
 
-* *YAML*: Simple, clean and readable (learn more about YAML in the Yaml component
-  documentation :doc:`/components/yaml/yaml_format`);
+.. code-block:: bash
 
-* *XML*: More powerful than YAML at times and supports IDE autocompletion;
+    $ cd my_project_name/
+    $ composer install
 
-* *PHP*: Very powerful but less readable than standard configuration formats.
+How does Composer know which specific dependencies to install? Because when a
+Symfony application is committed to a repository, the ``composer.json`` and
+``composer.lock`` files are also committed. These files tell Composer which
+dependencies (and which specific versions) to install for the application.
 
 Beginning Development
 ---------------------
@@ -391,13 +415,10 @@ a wide variety of articles about solving specific problems with Symfony.
 .. _`explained in this post`: http://fabien.potencier.org/signing-project-releases.html
 .. _`Phar extension`: http://php.net/manual/en/intro.phar.php
 .. _`Composer`: https://getcomposer.org/
-.. _`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

book/page_creation.rst

@@ -13,7 +13,7 @@ simple two-step process:
 #. *Create a route*: A route is the URL (e.g. ``/about``) to your page and
    points to a controller;
 
-#. *Create a controller*: A :term:`controller` is the PHP function you write that
+#. *Create a controller*: A controller is the PHP function you write that
    builds the page. You take the incoming request information and use it to
    create a Symfony ``Response`` object, which can hold HTML content, a JSON
    string or even a binary file like an image or PDF. The only rule is that
@@ -24,21 +24,16 @@ simple two-step process:
 Just like on the web, every interaction is initiated by an HTTP request.
 Your job is pure and simple: understand that request and return a response.
 
+.. index::
+   single:: Page creation; Example
+
 Creating a Page: Route and Controller
 -------------------------------------
 
 .. tip::
 
-    Before continuing, make sure you've read the
-    :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.
-
-    Using PHP's internal web server is only suitable while developing the
-    application. In order to run Symfony applications on production servers,
-    you'll have to configure your Apache or Nginx web server and virtual
-    host as explained in :doc:`/cookbook/configuration/web_server_configuration`.
+    Before continuing, make sure you've read the :doc:`Installation </book/installation>`
+    chapter and can access your new Symfony app in the browser.
 
 Suppose you want to create a page ``/lucky/number`` that generates a lucky (well,
 random) number and prints it. To do that, create a "Controller class" and a