Changes for correctness

Author: jbafford

book/page_creation.rst

@@ -42,19 +42,21 @@ also load specific bundles based on the selected environment. For example,
 Symfony2 comes with the WebProfilerBundle (described below), enabled only
 in the ``dev`` and ``test`` environments.
 
-To make your application respond faster, Symfony2 maintains a cache under the
-``app/cache/`` directory. In the ``dev`` environment, this cache is flushed
-automatically whenever you make changes to any code or configuration. But that's
-not the case in the ``prod`` environment, where performance is key. That's why you
-should always use the development environment when developing your application.
-
 Symfony2 comes with two web-accessible front controllers: ``app_dev.php`` 
 provides the ``dev`` environment, and ``app.php`` provides the ``prod`` environment.
 All web accesses to Symfony2 normally go through one of these front controllers.
 (The ``test`` environment is normally only used when running unit tests, and so 
 doesn't have a dedicated front controller. The console tool also provides a
 front controller that can be used with any environment.)
 
+When the front controller initializes the kernel, it provides two parameters:
+the environment, and also whether the kernel should run in debug mode.
+To make your application respond faster, Symfony2 maintains a cache under the
+``app/cache/`` directory. When in debug mode is enabled (such as ``app_dev.php``
+does by default), this cache is flushed automatically whenever you make changes
+to any code or configuration. When running in debug mode, Symfony2 runs
+slower, but your changes are reflected without having to manually clear the
+cache.
 
 .. index::
    single: Page creation; Example

quick_tour/the_big_picture.rst

@@ -419,7 +419,7 @@ Symfony2 developer's best friend.
 .. image:: /images/quick_tour/web_debug_toolbar.png
    :align: center
 
-What you see initially is only the tip of the iceberg; click on the long
+What you see initially is only the tip of the iceberg; click on the
 hexadecimal number (the session token) to reveal yet another very useful
 Symfony2 debugging tool: the profiler.
 
@@ -429,14 +429,17 @@ Symfony2 debugging tool: the profiler.
 .. note::
 
     You can also get more information quickly by hovering over the items
-    on the Web Debug Toolbar.
-
-When enabled (by default in the dev and test environments), the Profiler
-records a great deal of information on each request made to your application.
-It allows you to view details of each request, including, but not limited to,
-GET or POST parameters and the request headers; logs; an execution timeline;
-information on the currently logged in user; Doctrine queries; and more.
-
+    on the Web Debug Toolbar, or clicking them to go to their respective
+    pages in the profiler.
+
+When loaded (by default in the dev and test environments), and enabled
+(by default, only in the dev environment) the Profiler provides an interface
+to view a great deal of information recorded on each request made to your
+application. It allows you to view details of each request, including, but
+not limited to, GET or POST parameters and the request headers; logs; an
+execution timeline; information on the currently logged in user; Doctrine
+queries; and more.
+ 
 Of course, it would be unwise to have these tools enabled when you deploy
 your application, so by default, the profiler is not enabled in the ``prod``
 environment. (In fact, its bundle is not even loaded).