Fix proper nouns and some formatting

Author: bicpi

book/doctrine.rst

@@ -1485,7 +1485,7 @@ and ``nullable``. Take a few examples:
         fields:
             # A string field length 255 that cannot be null
             # (reflecting the default values for the "length" and *nullable* options)
-            # type attribute is necessary in yaml definitions
+            # type attribute is necessary in YAML definitions
             name:
                 type: string
 
@@ -1502,7 +1502,7 @@ and ``nullable``. Take a few examples:
         <!--
             A string field length 255 that cannot be null
             (reflecting the default values for the "length" and *nullable* options)
-            type attribute is necessary in xml definitions
+            type attribute is necessary in XML definitions
         -->
         <field name="name" type="string" />
         <field name="email"

book/installation.rst

@@ -321,11 +321,11 @@ Using Source Control
 
 If you're using a version control system like ``Git`` or ``Subversion``, you
 can setup your version control system and begin committing your project to
-it as normal. The Symfony Standard edition *is* the starting point for your
+it as normal. The Symfony Standard Edition *is* the starting point for your
 new project.
 
 For specific instructions on how best to setup your project to be stored
-in git, see :doc:`/cookbook/workflow/new_project_git`.
+in Git, see :doc:`/cookbook/workflow/new_project_git`.
 
 Ignoring the ``vendor/`` Directory
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

book/page_creation.rst

@@ -854,7 +854,7 @@ options of each feature.
     three formats (YAML, XML and PHP). Each has its own advantages and
     disadvantages. The choice of which to use is up to you:
 
-    * *YAML*: Simple, clean and readable (learn more about yaml in
+    * *YAML*: Simple, clean and readable (learn more about YAML in
       ":doc:`/components/yaml/yaml_format`");
 
     * *XML*: More powerful than YAML at times and supports IDE autocompletion;
@@ -867,7 +867,7 @@ Default Configuration Dump
 .. versionadded:: 2.1
     The ``config:dump-reference`` command was added in Symfony 2.1
 
-You can dump the default configuration for a bundle in yaml to the console using
+You can dump the default configuration for a bundle in YAML to the console using
 the ``config:dump-reference`` command.  Here is an example of dumping the default
 FrameworkBundle configuration:
 

book/service_container.rst

@@ -255,8 +255,8 @@ looks up the value of each parameter and uses it in the service definition.
 .. note::
 
     If you want to use a string that starts with an ``@`` sign as a parameter
-    value (i.e. a very safe mailer password) in a yaml file, you need to escape
-    it by adding another ``@`` sign (This only applies to the YAML format):
+    value (i.e. a very safe mailer password) in a YAML file, you need to escape
+    it by adding another ``@`` sign (this only applies to the YAML format):
 
     .. code-block:: yaml
 

components/config/definition.rst

@@ -12,7 +12,7 @@ and their structure can be validated using the "Definition" part of the Config
 Component. Configuration values are usually expected to show some kind of
 hierarchy. Also, values should be of a certain type, be restricted in number
 or be one of a given set of values. For example, the following configuration
-(in Yaml) shows a clear hierarchy and some validation rules that should be
+(in YAML) shows a clear hierarchy and some validation rules that should be
 applied to it (like: "the value for ``auto_connect`` must be a boolean value"):
 
 .. code-block:: yaml
@@ -396,19 +396,19 @@ Normalization
 When the config files are processed they are first normalized, then merged
 and finally the tree is used to validate the resulting array. The normalization
 process is used to remove some of the differences that result from different
-configuration formats, mainly the differences between Yaml and XML.
+configuration formats, mainly the differences between YAML and XML.
 
-The separator used in keys is typically ``_`` in Yaml and ``-`` in XML. For
-example, ``auto_connect`` in Yaml and ``auto-connect``. The normalization would
+The separator used in keys is typically ``_`` in YAML and ``-`` in XML. For
+example, ``auto_connect`` in YAML and ``auto-connect``. The normalization would
 make both of these ``auto_connect``.
 
 .. caution::
 
     The target key will not be altered if it's mixed like
     ``foo-bar_moo`` or if it already exists.
 
-Another difference between Yaml and XML is in the way arrays of values may
-be represented. In Yaml you may have:
+Another difference between YAML and XML is in the way arrays of values may
+be represented. In YAML you may have:
 
 .. code-block:: yaml
 
@@ -447,7 +447,7 @@ a second argument::
         ->end()
     ;
 
-As well as fixing this, ``fixXmlConfig`` ensures that single xml elements
+As well as fixing this, ``fixXmlConfig`` ensures that single XML elements
 are still turned into an array. So you may have:
 
 .. code-block:: xml

components/config/introduction.rst

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

components/config/resources.rst

@@ -27,7 +27,7 @@ all matches.
 Resource loaders
 ----------------
 
-For each type of resource (Yaml, XML, annotation, etc.) a loader must be defined.
+For each type of resource (YAML, XML, annotation, etc.) a loader must be defined.
 Each loader should implement :class:`Symfony\\Component\\Config\\Loader\\LoaderInterface`
 or extend the abstract :class:`Symfony\\Component\\Config\\Loader\\FileLoader`
 class, which allows for recursively importing other resources::

components/dependency_injection/introduction.rst

@@ -179,7 +179,7 @@ Setting Up the Container with Configuration Files
 -------------------------------------------------
 
 As well as setting up the services using PHP as above you can also use
-configuration files. This allows you to use XML or Yaml to write the definitions
+configuration files. This allows you to use XML or YAML to write the definitions
 for the services rather than using PHP to define the services as in the above
 examples. In anything but the smallest applications it make sense to organize
 the service definitions by moving them into one or more configuration files.

components/dependency_injection/parameters.rst

@@ -275,7 +275,7 @@ key, and define the type as ``constant``.
 
 .. note::
 
-    This does not work for Yaml configuration. If you're using Yaml, you can
+    This does not work for YAML configuration. If you're using YAML, you can
     import an XML file to take advantage of this functionality:
 
     .. configuration-block::
@@ -316,7 +316,7 @@ To disable this behavior, use the ``string`` type:
 
 .. note::
 
-    This is not available for Yaml and PHP, because they already have built-in
+    This is not available for YAML and PHP, because they already have built-in
     support for the PHP keywords.
 
 Syntax for Referencing Services
@@ -327,10 +327,10 @@ each format. You can configure the behavior if the referenced service does
 not exist. By default, an exception is thrown when a non-existent service
 is referenced.
 
-Yaml
+YAML
 ~~~~
 
-Start the string with  ``@`` or ``@?`` to reference a service in Yaml.
+Start the string with  ``@`` or ``@?`` to reference a service in YAML.
 
 * ``@mailer`` references the ``mailer`` service. If the service does not
   exists, an exception will be thrown;
@@ -339,7 +339,7 @@ Start the string with  ``@`` or ``@?`` to reference a service in Yaml.
 
 .. tip::
 
-    Use ``@@`` to escape the ``@`` symbol in Yaml. ``@@mailer`` will be
+    Use ``@@`` to escape the ``@`` symbol in YAML. ``@@mailer`` will be
     converted into the string ``"@mailer"`` instead of referencing the
     ``mailer`` service.
 

components/http_kernel/introduction.rst

@@ -386,7 +386,7 @@ to create a ``Response``.
 This can be useful if you want to use a "view" layer: instead of returning
 a ``Response`` from the controller, you return data that represents the page.
 A listener to this event could then use this data to create a ``Response`` that
-is in the correct format (e.g HTML, json, etc).
+is in the correct format (e.g HTML, JSON, etc).
 
 At this stage, if no listener sets a response on the event, then an exception
 is thrown: either the controller *or* one of the view listeners must always

components/options_resolver.rst

@@ -257,7 +257,7 @@ be anything, but it must be an integer. You can configure these types by calling
         ));
     }
 
-Possible types are the ones associated with the ``is_*`` php functions or a
+Possible types are the ones associated with the ``is_*`` PHP functions or a
 class name. You can also pass an array of types as the value. For instance,
 ``array('null', 'string')`` allows ``port`` to be ``null`` or a ``string``.
 

components/routing/introduction.rst

@@ -265,7 +265,7 @@ other loaders that work the same way:
 * :class:`Symfony\\Component\\Routing\\Loader\\PhpFileLoader`
 
 If you use the :class:`Symfony\\Component\\Routing\\Loader\\PhpFileLoader` you
-have to provide the name of a php file which returns a :class:`Symfony\\Component\\Routing\\RouteCollection`::
+have to provide the name of a PHP file which returns a :class:`Symfony\\Component\\Routing\\RouteCollection`::
 
     // RouteProvider.php
     use Symfony\Component\Routing\RouteCollection;

components/serializer.rst

@@ -6,7 +6,7 @@ The Serializer Component
 ========================
 
    The Serializer Component is meant to be used to turn objects into a
-   specific format (XML, JSON, Yaml, ...) and the other way around.
+   specific format (XML, JSON, YAML, ...) and the other way around.
 
 In order to do so, the Serializer Component follows the following
 simple schema.
@@ -128,7 +128,7 @@ JMSSerializer
 A popular third-party library, `JMS serializer`_, provides a more
 sophisticated albeit more complex solution. This library includes the
 ability to configure how your objects should be serialize/deserialized via
-annotations (as well as YML, XML and PHP), integration with the Doctrine ORM,
+annotations (as well as YAML, XML and PHP), integration with the Doctrine ORM,
 and handling of other complex cases (e.g. circular references).
 
 .. _`JMS serializer`: https://github.com/schmittjoh/serializer

components/yaml/yaml_format.rst

@@ -1,5 +1,5 @@
 .. index::
-    single: Yaml; Yaml Format
+    single: Yaml; YAML Format
 
 The YAML Format
 ===============

contributing/code/patches.rst

@@ -44,7 +44,7 @@ Set up your user information with your real name and a working email address:
     Windows users: when installing Git, the installer will ask what to do with
     line endings, and suggests replacing all LF with CRLF. This is the wrong
     setting if you wish to contribute to Symfony! Selecting the as-is method is
-    your best choice, as git will convert your line feeds to the ones in the
+    your best choice, as Git will convert your line feeds to the ones in the
     repository. If you have already installed Git, you can check the value of
     this setting by typing:
 
@@ -375,7 +375,7 @@ patch. Before re-submitting the patch, rebase with ``upstream/master`` or
 .. note::
 
     when doing a ``push --force``, always specify the branch name explicitly
-    to avoid messing other branches in the repo (``--force`` tells git that
+    to avoid messing other branches in the repo (``--force`` tells Git that
     you really want to mess with things so do it carefully).
 
 Often, moderators will ask you to "squash" your commits. This means you will
@@ -397,7 +397,7 @@ type this command, an editor will popup showing a list of commits:
 
 To squash all commits into the first one, remove the word "pick" before the
 second and the last commits, and replace it by the word "squash" or just "s".
-When you save, git will start rebasing, and if successful, will ask you to
+When you save, Git will start rebasing, and if successful, will ask you to
 edit the commit message, which by default is a listing of the commit messages
 of all the commits. When you finish, execute the push command.
 

contributing/documentation/standards.rst

@@ -72,9 +72,9 @@ Configuration examples should show all supported formats using
 :ref:`configuration blocks <docs-configuration-blocks>`. The supported formats
 (and their orders) are:
 
-* **Configuration** (including services and routing): Yaml, Xml, Php
-* **Validation**: Yaml, Annotations, Xml, Php
-* **Doctrine Mapping**: Annotations, Yaml, Xml, Php
+* **Configuration** (including services and routing): YAML, XML, PHP
+* **Validation**: YAML, Annotations, XML, PHP
+* **Doctrine Mapping**: Annotations, YAML, XML, PHP
 
 Example
 ~~~~~~~
@@ -101,7 +101,7 @@ Example
 
 .. caution::
 
-    In Yaml you should put a space after ``{`` and before ``}`` (e.g. ``{ _controller: ... }``),
+    In YAML you should put a space after ``{`` and before ``}`` (e.g. ``{ _controller: ... }``),
     but this should not be done in Twig (e.g.  ``{'hello' : 'value'}``).
 
 .. _`the Sphinx documentation`: http://sphinx-doc.org/rest.html#source-code