minor #10535 review doc chapters for belittling words (dbu)

This PR was merged into the 4.1 branch.

Discussion
----------

review doc chapters for belittling words

and a rather hefty chunk of changes for symfony/diversity#9

i hope this one has not gotten too big.

Commits
-------

84e6684 review doc chapter for belittling words

Author: javiereguiluz

bundles/best_practices.rst

@@ -23,7 +23,7 @@ vendor segment, followed by zero or more category segments, and it ends with the
 namespace short name, which must end with ``Bundle``.
 
 A namespace becomes a bundle as soon as you add a bundle class to it. The
-bundle class name must follow these simple rules:
+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);
@@ -467,8 +467,9 @@ Retrieve the configuration parameters in your code from the container::
 
     $container->getParameter('acme_blog.author.email');
 
-Even if this mechanism is simple enough, you should consider using the more
-advanced :doc:`semantic bundle configuration </bundles/configuration>`.
+While this mechanism requires the least effort, you should consider using the
+more advanced :doc:`semantic bundle configuration </bundles/configuration>` to
+make your configuration more robust.
 
 Versioning
 ----------

bundles/override.rst

@@ -68,7 +68,7 @@ the routes from any bundle, then they must be manually imported from somewhere
 in your application (e.g. ``config/routes.yaml``).
 
 The easiest way to "override" a bundle's routing is to never import it at
-all. Instead of importing a third-party bundle's routing, simply copy
+all. Instead of importing a third-party bundle's routing, copy
 that routing file into your application, modify it, and import it instead.
 
 Controllers

configuration/configuration_organization.rst

@@ -5,7 +5,7 @@ How to Organize Configuration Files
 ===================================
 
 The Symfony skeleton defines three :doc:`execution environments </configuration/environments>`
-called ``dev``, ``prod`` and ``test``. An environment simply represents a way
+called ``dev``, ``prod`` and ``test``. An environment represents a way
 to execute the same codebase with different configurations.
 
 In order to select the configuration file to load for each environment, Symfony
@@ -129,9 +129,9 @@ Global Configuration Files
 
 Some system administrators may prefer to store sensitive parameters in files
 outside the project directory. Imagine that the database credentials for your
-website are stored in the ``/etc/sites/mysite.com/parameters.yaml`` file. Loading
-this file is as simple as indicating the full file path when importing it from
-any other configuration file:
+website are stored in the ``/etc/sites/mysite.com/parameters.yaml`` file. You
+can load files from outside the project folder by indicating the full file path
+when importing it from any other configuration file:
 
 .. configuration-block::
 

configuration/environments.rst

@@ -199,7 +199,7 @@ Creating a new Environment
 --------------------------
 
 Since an environment is nothing more than a string that corresponds to a set of
-configuration, creating a new environment is quite easy.
+configuration, you can also create your own environments for specific purposes.
 
 Suppose, for example, that before deployment, you need to benchmark your
 application. One way to benchmark the application is to use near-production
@@ -355,7 +355,7 @@ includes the following:
 
 .. note::
 
-    You can easily change the directory location and name. For more information
+    You can change the directory location and name. For more information
     read the article :doc:`/configuration/override_dir_structure`.
 
 Going further

configuration/front_controllers_and_kernel.rst

@@ -51,7 +51,7 @@ You can choose the front controller that's used by adding it in the URL, like:
      http://localhost/index.php/some/path/...
 
 As you can see, this URL contains the PHP script to be used as the front
-controller. You can use that to easily switch to a custom made front controller
+controller. You can use that to switch to a custom made front controller
 that is located in the ``public/`` directory.
 
 .. seealso::
@@ -123,7 +123,7 @@ controller to make use of the new kernel.
 The Environments
 ----------------
 
-As just mentioned, the ``Kernel`` has to implement another method -
+As mentioned above, the ``Kernel`` has to implement another method -
 :method:`Symfony\\Bundle\\FrameworkBundle\\Kernel\\MicroKernelTrait::configureContainer`.
 This method is responsible for loading the application's configuration from the
 right *environment*.

configuration/micro_kernel_trait.rst

@@ -5,8 +5,8 @@ The default ``Kernel`` class included in Symfony applications uses a
 :class:`Symfony\\Bundle\\FrameworkBundle\\Kernel\\MicroKernelTrait` to configure
 the bundles, the routes and the service container in the same class.
 
-This micro-kernel approach is so flexible that let you control your application
-structure and features quite easily.
+This micro-kernel approach is flexible, allowing you to control your application
+structure and features.
 
 A Single-File Symfony Application
 ---------------------------------

configuration/multiple_kernels.rst

@@ -124,7 +124,7 @@ According to the above code, this config will live in one or multiple files
 stored in ``config/api/`` and ``config/api/ENVIRONMENT_NAME/`` directories.
 
 The new configuration files can be created from scratch when you load just a few
-bundles, because it will be very simple. Otherwise, duplicate the existing
+bundles, because it will be small. Otherwise, duplicate the existing
 config files in ``config/packages/`` or better, import them and override the
 needed options.
 

configuration/override_dir_structure.rst

@@ -5,7 +5,7 @@ How to Override Symfony's default Directory Structure
 =====================================================
 
 Symfony automatically ships with a default directory structure. You can
-easily override this directory structure to create your own. The default
+override this directory structure to create your own. The default
 directory structure is:
 
 .. code-block:: text

console/input.rst

@@ -71,7 +71,7 @@ to greet all your friends). Only the last argument can be a list::
             'Who do you want to greet (separate multiple names with a space)?'
         );
 
-To use this, just specify as many names as you want:
+To use this, specify as many names as you want:
 
 .. code-block:: terminal
 

console/lazy_commands.rst

@@ -42,7 +42,7 @@ Built-in Command Loaders
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
 The :class:`Symfony\\Component\\Console\\CommandLoader\\FactoryCommandLoader`
-class provides a simple way of getting commands lazily loaded as it takes an
+class provides a way of getting commands lazily loaded as it takes an
 array of ``Command`` factories as its only constructor argument::
 
     use Symfony\Component\Console\CommandLoader\FactoryCommandLoader;