Merge branch '3.4' into 4.3

* 3.4:
  Fixed many spelling issues

Author: wouterj

bundles/best_practices.rst

@@ -26,7 +26,7 @@ A namespace becomes a bundle as soon as you add a bundle class to it. The
 bundle class name must follow these rules:
 
 * Use only alphanumeric characters and underscores;
-* Use a StudlyCaps name (i.e. camelCase with the first letter uppercased);
+* Use a StudlyCaps name (i.e. camelCase with an uppercase first letter);
 * Use a descriptive and short name (no more than two words);
 * Prefix the name with the concatenation of the vendor (and optionally the
   category namespaces);

components/asset.rst

@@ -119,8 +119,9 @@ suffix to any asset path::
     echo $package->getUrl('image.png');
     // result: image.png?v1
 
-In case you want to modify the version format, pass a sprintf-compatible format
-string as the second argument of the ``StaticVersionStrategy`` constructor::
+In case you want to modify the version format, pass a ``sprintf``-compatible
+format string as the second argument of the ``StaticVersionStrategy``
+constructor::
 
     // puts the 'version' word before the version value
     $package = new Package(new StaticVersionStrategy('v1', '%s?version=%s'));

components/config.rst

@@ -6,7 +6,7 @@ The Config Component
 ====================
 
     The Config component provides several classes to help you find, load,
-    combine, autofill and validate configuration values of any kind, whatever
+    combine, fill and validate configuration values of any kind, whatever
     their source may be (YAML, XML, INI files, or for instance a database).
 
 Installation

components/console/helpers/processhelper.rst

@@ -9,7 +9,7 @@ useful information about process status.
 
 To display process details, use the :class:`Symfony\\Component\\Console\\Helper\\ProcessHelper`
 and run your command with verbosity. For example, running the following code with
-a very verbose verbosity (e.g. -vv)::
+a very verbose verbosity (e.g. ``-vv``)::
 
     use Symfony\Component\Process\Process;
 

components/console/helpers/progressbar.rst

@@ -272,7 +272,7 @@ the example above.
 Bar Settings
 ~~~~~~~~~~~~
 
-Amongst the placeholders, ``bar`` is a bit special as all the characters used
+Among the placeholders, ``bar`` is a bit special as all the characters used
 to display it can be customized::
 
     // the finished part of the bar

components/console/helpers/questionhelper.rst

@@ -242,7 +242,7 @@ convenient for passwords::
 .. caution::
 
     When you ask for a hidden response, Symfony will use either a binary, change
-    stty mode or use another trick to hide the response. If none is available,
+    ``stty`` mode or use another trick to hide the response. If none is available,
     it will fallback and allow the response to be visible unless you set this
     behavior to ``false`` using
     :method:`Symfony\\Component\\Console\\Question\\Question::setHiddenFallback`

components/console/usage.rst

@@ -10,7 +10,7 @@ built-in options as well as a couple of built-in commands for the Console compon
 .. note::
 
     These examples assume you have added a file ``application.php`` to run at
-    the cli::
+    the CLI::
 
         #!/usr/bin/env php
         <?php

components/debug.rst

@@ -58,7 +58,7 @@ Enabling the Exception Handler
 
 The :class:`Symfony\\Component\\Debug\\ExceptionHandler` class catches
 uncaught PHP exceptions and converts them to a nice PHP response. It is useful
-in debug mode to replace the default PHP/XDebug output with something prettier
+in debug mode to replace the default PHP/Xdebug output with something prettier
 and more useful::
 
     use Symfony\Component\Debug\ExceptionHandler;

components/dependency_injection/compilation.rst

@@ -78,7 +78,7 @@ A very simple extension may just load configuration files into the container::
 
 This does not gain very much compared to loading the file directly into
 the overall container being built. It just allows the files to be split
-up amongst the modules/bundles. Being able to affect the configuration
+up among the modules/bundles. Being able to affect the configuration
 of a module from configuration files outside of the module/bundle is needed
 to make a complex application configurable. This can be done by specifying
 sections of config files loaded directly into the container as being for

components/dom_crawler.rst

@@ -157,7 +157,7 @@ and :method:`Symfony\\Component\\DomCrawler\\Crawler::filter`::
     method.
 
     The default namespace is removed when loading the content if it's the only
-    namespace in the document. It's done to simplify the xpath queries.
+    namespace in the document. It's done to simplify the XPath queries.
 
 Namespaces can be explicitly registered with the
 :method:`Symfony\\Component\\DomCrawler\\Crawler::registerNamespace` method::
@@ -203,7 +203,7 @@ Get all the direct child nodes matching a CSS selector::
 Accessing Node Values
 ~~~~~~~~~~~~~~~~~~~~~
 
-Access the node name (HTML tag name) of the first node of the current selection (eg. "p" or "div")::
+Access the node name (HTML tag name) of the first node of the current selection (e.g. "p" or "div")::
 
     // returns the node name (HTML tag name) of the first child element under <body>
     $tag = $crawler->filterXPath('//body/*')->nodeName();