"web debug toolbar" instead of "Web Debug Toolbar"

book/internals.rst

@@ -351,7 +351,7 @@ The FrameworkBundle registers several listeners:
     Collects data for the current request.
 
 :class:`Symfony\\Bundle\\WebProfilerBundle\\EventListener\\WebDebugToolbarListener`
-    Injects the Web Debug Toolbar.
+    Injects the web debug toolbar.
 
 :class:`Symfony\\Component\\HttpKernel\\EventListener\\ResponseListener`
     Fixes the Response ``Content-Type`` based on the request format.
@@ -455,7 +455,7 @@ enhance performance; use it in the production environment to explore problems
 after the fact.
 
 You rarely have to deal with the profiler directly as Symfony provides
-visualizer tools like the Web Debug Toolbar and the Web Profiler. If you use
+visualizer tools like the web debug toolbar and the web profiler. If you use
 the Symfony Standard Edition, the profiler, the web debug toolbar, and the
 web profiler are all already configured with sensible settings.
 
@@ -481,7 +481,7 @@ bottom of all pages. It displays a good summary of the profiling data that
 gives you instant access to a lot of useful information when something does
 not work as expected.
 
-If the summary provided by the Web Debug Toolbar is not enough, click on the
+If the summary provided by the web debug toolbar is not enough, click on the
 token link (a string made of 13 random characters) to access the Web Profiler.
 
 .. note::

cookbook/email/dev_environment.rst

@@ -186,7 +186,7 @@ Viewing from the Web Debug Toolbar
 ----------------------------------
 
 You can view any email sent during a single response when you are in the
-``dev`` environment using the Web Debug Toolbar. The email icon in the toolbar
+``dev`` environment using the web debug toolbar. The email icon in the toolbar
 will show how many emails were sent. If you click it, a report will open
 showing the details of the sent emails.
 

quick_tour/the_big_picture.rst

@@ -269,7 +269,7 @@ Working with Environments
 
 Now that you have a better understanding of how Symfony works, take a closer
 look at the bottom of any Symfony rendered page. You should notice a small
-bar with the Symfony logo. This is the "Web Debug Toolbar" and it is a Symfony
+bar with the Symfony logo. This is the "web debug toolbar" and it is a Symfony
 developer's best friend!
 
 .. image:: /images/quick_tour/web_debug_toolbar.png
@@ -310,8 +310,8 @@ URL, you can visit ``http://localhost:8000/app_dev.php`` URL.
 The main difference between environments is that ``dev`` is optimized to
 provide lots of information to the developer, which means worse application
 performance. Meanwhile, ``prod`` is optimized to get the best performance,
-which means that debug information is disabled, as well as the Web Debug
-Toolbar.
+which means that debug information is disabled, as well as the web debug
+toolbar.
 
 The other difference between environments is the configuration options used
 to execute the application. When you access the ``dev`` environment, Symfony