minor tweaks

Author: weaverryan

controller.rst

@@ -766,15 +766,17 @@ abstraction around the HTTP response - the text-based message filled with
 headers and content that's sent back to the client::
 
     use Symfony\Component\HttpFoundation\Response;
+    use Symfony\Component\HttpFoundation\JsonResponse;
 
     // create a simple Response with a 200 status code (the default)
     $response = new Response('Hello '.$name, Response::HTTP_OK);
 
-    // create a JSON-response with a 200 status code
-    $response = new Response(json_encode(array('name' => $name)));
-    $response->headers->set('Content-Type', 'application/json');
+    // JsonResponse is a sub-class of Response
+    $response = new JsonResponse(array('name' => $name));
+    // set a header!
+    $response->headers->set('X-Rate-Limit', 10);
 
-There are also special classes to make certain kinds of responses easier:
+There are special classes that make certain kinds of responses easier:
 
 * For JSON, there is :class:`Symfony\\Component\\HttpFoundation\\JsonResponse`.
   See :ref:`component-http-foundation-json-response`.

page_creation.rst

@@ -83,6 +83,15 @@ to creating a page?
    return a ``Response`` object. You'll learn more about :doc:`controllers </controllers>`
    in their own section, including how to return JSON responses;
 
+The Web Debug Toolbar: Debugging Dream
+--------------------------------------
+
+If your page is working, then you should *also* see a bar along the bottom of your
+browser. This is called the Web Debug Toolbar: and it's your debugging best friend.
+You'll learn more about all the information it holds along the way, but feel free
+to experiment: hover over and click the different icons to get information about
+routing, performance, logging and more.
+
 Rendering a Template (with the Service Container)
 -------------------------------------------------
 

routing.rst

@@ -94,9 +94,8 @@ for you to use in your controller (keep reading). The ``blog_show`` is the
 internal name of the route, which doesn't have any meaning yet and just needs
 to be unique. Later, you'll use it to generate URLs.
 
-If you don't want to use annotations, because you don't like them or because
-you don't want to depend on the SensioFrameworkExtraBundle, you can also use
-Yaml, XML or PHP. In these formats, the ``_controller`` parameter is a special
+If you don't want to use annotations, you can also use Yaml, XML or PHP. In these
+formats, the ``_controller`` parameter is a special
 key that tells Symfony which controller should be executed when a URL matches
 this route. The ``_controller`` string is called the
 :ref:`logical name <controller-string-syntax>`. It follows a pattern that
@@ -272,8 +271,8 @@ will be explained shortly in the :ref:`controller-string-syntax` section.
 .. index::
    single: Routing; Placeholders
 
-Routing with Placeholders
-~~~~~~~~~~~~~~~~~~~~~~~~~
+Dynamic Routing with Placeholders
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Of course the routing system supports much more interesting routes. Many
 routes will contain one or more named "wildcard" placeholders: