Merge branch '4.1'

* 4.1:
  review components documentation for belittling words
  review single doc pages for belittling words

Author: javiereguiluz

bundles.rst

@@ -44,7 +44,7 @@ file::
 Creating a Bundle
 -----------------
 
-This section creates and enables a new bundle to show how simple it is to do it.
+This section creates and enables a new bundle to show there are only a few steps required.
 The new bundle is called AcmeTestBundle, where the ``Acme`` portion is just a
 dummy name that should be replaced by some "vendor" name that represents you or
 your organization (e.g. ABCTestBundle for some company named ``ABC``).
@@ -83,9 +83,9 @@ And while it doesn't do anything yet, AcmeTestBundle is now ready to be used.
 Bundle Directory Structure
 --------------------------
 
-The directory structure of a bundle is simple and flexible. By default, the
-bundle system follows a set of conventions that help to keep code consistent
-between all Symfony bundles. Take a look at AcmeDemoBundle, as it contains some
+The directory structure of a bundle is meant to help to keep code consistent
+between all Symfony bundles. It follows a set of conventions, but is flexible
+to be adjusted if needed. Take a look at AcmeDemoBundle, as it contains some
 of the most common elements of a bundle:
 
 ``Controller/``

components/asset.rst

@@ -282,8 +282,8 @@ You can also pass a schema-agnostic URL::
     // result: //static.example.com/images/logo.png?v1
 
 This is useful because assets will automatically be requested via HTTPS if
-a visitor is viewing your site in https. Just make sure that your CDN host
-supports https.
+a visitor is viewing your site in https. If you want to use this, make sure
+that your CDN host supports HTTPS.
 
 In case you serve assets from more than one domain to improve application
 performance, pass an array of URLs as the first argument to the ``UrlPackage``

components/console/changing_default_command.rst

@@ -5,7 +5,7 @@ Changing the Default Command
 ============================
 
 The Console component will always run the ``ListCommand`` when no command name is
-passed. In order to change the default command you just need to pass the command
+passed. In order to change the default command you need to pass the command
 name to the ``setDefaultCommand()`` method::
 
     namespace Acme\Console\Command;

components/console/helpers/formatterhelper.rst

@@ -101,10 +101,10 @@ Custom Suffix
 ~~~~~~~~~~~~~
 
 By default, the ``...`` suffix is used. If you wish to use a different suffix,
-simply pass it as the third argument to the method.
+pass it as the third argument to the method.
 The suffix is always appended, unless truncate length is longer than a message
 and a suffix length.
-If you don't want to use suffix at all, just pass an empty string::
+If you don't want to use suffix at all, pass an empty string::
 
     $truncatedMessage = $formatter->truncate($message, 7, '!!'); // result: This is!!
     $truncatedMessage = $formatter->truncate($message, 7, '');   // result: This is

components/console/helpers/progressbar.rst

@@ -67,7 +67,7 @@ value and then call the ``setMaxSteps()`` method to update it as needed::
 .. versionadded:: 4.1
     The ``setMaxSteps()`` method was introduced in Symfony 4.1.
 
-Another solution is to just omit the steps argument when creating the
+Another solution is to omit the steps argument when creating the
 :class:`Symfony\\Component\\Console\\Helper\\ProgressBar` instance::
 
     $progressBar = new ProgressBar($output);

components/console/single_command_tool.rst

@@ -33,7 +33,7 @@ The method :method:`Symfony\\Component\\Console\\Application::setDefaultCommand`
 accepts a boolean as second parameter. If true, the command ``echo`` will then
 always be used, without having to pass its name.
 
-Of course, you can still register a command as usual::
+You can still register a command as usual::
 
   #!/usr/bin/env php
   <?php

components/console/usage.rst

@@ -139,7 +139,7 @@ commands, then you can run ``help`` like this:
 
     $ php application.php h
 
-If you have commands using ``:`` to namespace commands then you just have
+If you have commands using ``:`` to namespace commands then you only need
 to type the shortest unambiguous text for each part. If you have created the
 ``demo:greet`` as shown in :doc:`/components/console` then you
 can run it with:

components/debug.rst

@@ -22,7 +22,7 @@ Usage
 -----
 
 The Debug component provides several tools to help you debug PHP code.
-Enabling them all is as easy as it can get::
+Enabling them all can be done by calling the static method ``Debug::enable()``::
 
     use Symfony\Component\Debug\Debug;
 
@@ -80,7 +80,7 @@ throw more helpful exceptions when a class isn't found by the registered
 autoloaders. All autoloaders that implement a ``findFile()`` method are replaced
 with a ``DebugClassLoader`` wrapper.
 
-Using the ``DebugClassLoader`` is as easy as calling its static
+To activate the ``DebugClassLoader``, call its static
 :method:`Symfony\\Component\\Debug\\DebugClassLoader::enable` method::
 
     use Symfony\Component\Debug\DebugClassLoader;

components/dependency_injection.rst

@@ -32,7 +32,7 @@ Basic Usage
     independent component in any PHP application. Read the :doc:`/service_container`
     article to learn about how to use it in Symfony applications.
 
-You might have a simple class like the following ``Mailer`` that
+You might have a class like the following ``Mailer`` that
 you want to make available as a service::
 
     class Mailer

components/dependency_injection/compilation.rst

@@ -449,7 +449,7 @@ need to be parsed and the PHP configuration built from them. The compilation
 process makes the container more efficient but it takes time to run. You
 can have the best of both worlds though by using configuration files and
 then dumping and caching the resulting configuration. The ``PhpDumper``
-makes dumping the compiled container easy::
+serves at dumping the compiled container::
 
     use Symfony\Component\DependencyInjection\ContainerBuilder;
     use Symfony\Component\DependencyInjection\Dumper\PhpDumper;
@@ -534,7 +534,7 @@ You do not need to work out which files to cache as the container builder
 keeps track of all the resources used to configure it, not just the
 configuration files but the extension classes and compiler passes as well.
 This means that any changes to any of these files will invalidate the cache
-and trigger the container being rebuilt. You just need to ask the container
+and trigger the container being rebuilt. You need to ask the container
 for these resources and use them as metadata for the cache::
 
     // ...