Various fixes

Co-Authored-By: Toflar <yanick.witschi@terminal42.ch>

Author: 2 people

components/dotenv.rst

@@ -67,7 +67,7 @@ to have different files depending on the environment you're working in. Typicall
 this happens for local development or Continuous Integration where you might
 want to have different files for your ``test`` and ``dev`` environments.
 
-You can use ``Dotenv::loadEnv()`` to ease this process for you::
+You can use ``Dotenv::loadEnv()`` to ease this process::
 
     use Symfony\Component\Dotenv\Dotenv;
 
@@ -79,16 +79,16 @@ in the following order::
 
 1. If ``.env`` exists, it is loaded first. In case there's no ``.env`` file but a
    ``.env.dist``, this one will be loaded instead.
-2. If one of the previously mentioned files contains the variable ``APP_ENV``, the
-   variable is populated and used to load environment specific files hereafter. If
+2. If one of the previously mentioned files contains the ``APP_ENV`` variable, the
+   variable is populated and used to load environment-specific files hereafter. If
    ``APP_ENV`` is not defined in either of the previously mentioned files, ``dev`` is
    assumed for ``APP_ENV`` and populated by default.
-3. If there's an ``.env.$env.local`` file, this one is loaded. Otherwise, it falls
+3. If there's a ``.env.$env.local`` file, this one is loaded. Otherwise, it falls
    back to ``.env.$env``.
-4. If there's an ``env.local`` it's loaded last.
+4. If there's a ``.env.local`` it's loaded last.
 
 This might look complicated at first glance but it gives you the opportunity to commit
-multiple environment specific files that can then be adjusted to your local environment
+multiple environment-specific files that can then be adjusted to your local environment
 easily. Given you commit ``.env``, ``.env.test`` and ``.env.test`` to represent different
 configuration settings for your environments, each of them can be adjusted by using
 ``.env.local``, ``.env.test.local`` and ``.env.test.local`` respectively.
@@ -99,14 +99,14 @@ configuration settings for your environments, each of them can be adjusted by us
     same results for everyone.
 
 You can adjust the variable defining the environment, default environment and test
-environments by passing then as additional arguments to ``Dotenv::loadEnv()``
+environments by passing them as additional arguments to ``Dotenv::loadEnv()``
 (see :method:`Symfony\Component\Dotenv::loadEnv` for details).
 
 .. versionadded:: 4.2
     The ``Dotenv::loadEnv()`` method was introduced in Symfony 4.2.
 
 You should never store a ``.env`` file in your code repository as it might
-contain sensitive information; create a ``.env.dist`` (or multiple environment
+contain sensitive information; create a ``.env.dist`` (or multiple environment-
 specific ones as shown above)) file with sensible defaults instead.
 
 .. note::