use "full-stack" instead of "full stack"

xabbuh · xabbuh · commit bd5ca2662bca · 2015-05-01T10:37:35.000+02:00
diff --git a/components/dependency_injection/compilation.rst b/components/dependency_injection/compilation.rst
@@ -207,7 +207,7 @@ The XML version of the config would then look like this:
 
 .. note::
 
-    In the Symfony full stack framework there is a base Extension class which
+    In the Symfony full-stack framework there is a base Extension class which
     implements these methods as well as a shortcut method for processing the
     configuration. See :doc:`/cookbook/bundles/extension` for more details.
 
@@ -347,9 +347,9 @@ will then be called when the container is compiled::
 
 .. note::
 
-    Compiler passes are registered differently if you are using the full
-    stack framework, see :doc:`/cookbook/service_container/compiler_passes`
-    for more details.
+    Compiler passes are registered differently if you are using the full-stack
+    framework, see :doc:`/cookbook/service_container/compiler_passes` for
+    more details.
 
 Controlling the Pass Ordering
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -510,5 +510,5 @@ to see if the files have changed, if they have the cache will be considered stal
 
 .. note::
 
-    In the full stack framework the compilation and caching of the container
+    In the full-stack framework the compilation and caching of the container
     is taken care of for you.
diff --git a/components/dependency_injection/tags.rst b/components/dependency_injection/tags.rst
@@ -173,9 +173,9 @@ run when the container is compiled::
 
 .. note::
 
-    Compiler passes are registered differently if you are using the full
-    stack framework. See :doc:`/cookbook/service_container/compiler_passes`
-    for more details.
+    Compiler passes are registered differently if you are using the full-stack
+    framework. See :doc:`/cookbook/service_container/compiler_passes` for
+    more details.
 
 Adding additional Attributes on Tags
 ------------------------------------
diff --git a/components/dependency_injection/workflow.rst b/components/dependency_injection/workflow.rst
@@ -8,11 +8,11 @@ In the preceding pages of this section, there has been little to say about
 where the various files and classes should be located. This is because this
 depends on the application, library or framework in which you want to use
 the container. Looking at how the container is configured and built in the
-Symfony full stack framework will help you see how this all fits together,
-whether you are using the full stack framework or looking to use the service
+Symfony full-stack framework will help you see how this all fits together,
+whether you are using the full-stack framework or looking to use the service
 container in another application.
 
-The full stack framework uses the HttpKernel component to manage the loading
+The full-stack framework uses the HttpKernel component to manage the loading
 of the service container configuration from the application and bundles and
 also handles the compilation and caching. Even if you are not using HttpKernel,
 it should give you an idea of one way of organizing configuration in a modular
diff --git a/cookbook/console/usage.rst b/cookbook/console/usage.rst
@@ -5,8 +5,8 @@ How to Use the Console
 ======================
 
 The :doc:`/components/console/usage` page of the components documentation looks
-at the global console options. When you use the console as part of the full
-stack framework, some additional global options are available as well.
+at the global console options. When you use the console as part of the full-stack
+framework, some additional global options are available as well.
 
 By default, console commands run in the ``dev`` environment and you may want
 to change this for some commands. For example, you may want to run some commands
