minor #16305 Correct spelling & grammar in 5.3 (gnito-org)

This PR was merged into the 5.3 branch.

Discussion
----------

Correct spelling & grammar in 5.3

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/releases for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `6.x` for features of unreleased versions).

-->

Commits
-------

534486b Correct spelling & grammar in 5.3

Author: javiereguiluz

cache.rst

@@ -800,5 +800,5 @@ Then, register the ``SodiumMarshaller`` service using this key:
 
 When configuring multiple keys, the first key will be used for reading and
 writing, and the additional key(s) will only be used for reading. Once all
-cache items encrypted with the old key have expired, you can remove
-``OLD_CACHE_DECRYPTION_KEY`` completely.
+cache items encrypted with the old key have expired, you can completely remove
+``OLD_CACHE_DECRYPTION_KEY``.

components/browser_kit.rst

@@ -185,7 +185,7 @@ Custom Header Handling
 The optional HTTP headers passed to the ``request()`` method follows the FastCGI
 request format (uppercase, underscores instead of dashes and prefixed with ``HTTP_``).
 Before saving those headers to the request, they are lower-cased, with ``HTTP_``
-stripped, and underscores turned to dashes.
+stripped, and underscores converted into dashes.
 
 If you're making a request to an application that has special rules about header
 capitalization or punctuation, override the ``getHeaders()`` method, which must

components/http_foundation.rst

@@ -81,7 +81,7 @@ can be accessed via several public properties:
   (``$request->headers->get('User-Agent')``).
 
 Each property is a :class:`Symfony\\Component\\HttpFoundation\\ParameterBag`
-instance (or a sub-class of), which is a data holder class:
+instance (or a subclass of), which is a data holder class:
 
 * ``request``: :class:`Symfony\\Component\\HttpFoundation\\ParameterBag` or
   :class:`Symfony\\Component\\HttpFoundation\\InputBag` if the data is
@@ -726,7 +726,7 @@ The ``JsonResponse`` class sets the ``Content-Type`` header to
 .. caution::
 
     To avoid XSSI `JSON Hijacking`_, you should pass an associative array
-    as the outer-most array to ``JsonResponse`` and not an indexed array so
+    as the outermost array to ``JsonResponse`` and not an indexed array so
     that the final result is an object (e.g. ``{"object": "not inside an array"}``)
     instead of an array (e.g. ``[{"object": "inside an array"}]``). Read
     the `OWASP guidelines`_ for more information.

components/lock.rst

@@ -210,7 +210,7 @@ as seconds) and ``isExpired()`` (which returns a boolean).
 Automatically Releasing The Lock
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Locks are automatically released when their Lock objects are destructed. This is
+Locks are automatically released when their Lock objects are destroyed. This is
 an implementation detail that will be important when sharing Locks between
 processes. In the example below, ``pcntl_fork()`` creates two processes and the
 Lock will be released automatically as soon as one process finishes::
@@ -508,7 +508,7 @@ locks::
     $store = new PostgreSqlStore($databaseConnectionOrDSN);
 
 In opposite to the ``PdoStore``, the ``PostgreSqlStore`` does not need a table to
-store locks and does not expire.
+store locks and it does not expire.
 
 .. versionadded:: 5.2
 

components/messenger.rst

@@ -77,7 +77,7 @@ middleware stack. The component comes with a set of middleware that you can use.
 When using the message bus with Symfony's FrameworkBundle, the following middleware
 are configured for you:
 
-#. :class:`Symfony\\Component\\Messenger\\Middleware\\SendMessageMiddleware` (enables asynchronous processing, logs the processing of your messages if you pass a logger)
+#. :class:`Symfony\\Component\\Messenger\\Middleware\\SendMessageMiddleware` (enables asynchronous processing, logs the processing of your messages if you provide a logger)
 #. :class:`Symfony\\Component\\Messenger\\Middleware\\HandleMessageMiddleware` (calls the registered handler(s))
 
 Example::

components/phpunit_bridge.rst

@@ -295,7 +295,7 @@ Baseline Deprecations
 If your application has some deprecations that you can't fix for some reasons,
 you can tell Symfony to ignore them. The trick is to create a file with the
 allowed deprecations and define it as the "deprecation baseline". Deprecations
-inside that file are ignore but the rest of deprecations are still reported.
+inside that file are ignored but the rest of deprecations are still reported.
 
 First, generate the file with the allowed deprecations (run the same command
 whenever you want to update the existing file):

components/runtime.rst

@@ -383,7 +383,7 @@ application outside of the global state in 6 steps:
    that knows how to "run" the application object.
 #. The ``RunnerInterface::run(object $application)`` is called and it returns the
    exit status code as `int`.
-#. The PHP engine is exited with this status code.
+#. The PHP engine is terminated with this status code.
 
 When creating a new runtime, there are two things to consider: First, what arguments
 will the end user use? Second, what will the user's application look like?

components/semaphore.rst

@@ -45,7 +45,7 @@ class, which in turn requires another class to manage the storage::
 The semaphore is created by calling the
 :method:`Symfony\\Component\\Semaphore\\SemaphoreFactory::createSemaphore`
 method. Its first argument is an arbitrary string that represents the locked
-resource. Its second argument is the maximum number of process allowed. Then, a
+resource. Its second argument is the maximum number of processes allowed. Then, a
 call to the :method:`Symfony\\Component\\Semaphore\\SemaphoreInterface::acquire`
 method will try to acquire the semaphore::
 
@@ -54,7 +54,7 @@ method will try to acquire the semaphore::
 
     if ($semaphore->acquire()) {
         // The resource "pdf-invoice-generation" is locked.
-        // You can compute and generate invoice safely here.
+        // Here you can safely compute and generate the invoice.
 
         $semaphore->release();
     }

components/string.rst

@@ -36,7 +36,7 @@ However, other languages require thousands of symbols to display their contents.
 They need complex encoding standards such as `Unicode`_ and concepts like
 "character" no longer make sense. Instead, you have to deal with these terms:
 
-* `Code points`_: they are the atomic unit of information. A string is a series
+* `Code points`_: they are the atomic units of information. A string is a series
   of code points. Each code point is a number whose meaning is given by the
   `Unicode`_ standard. For example, the English letter ``A`` is the ``U+0041``
   code point and the Japanese *kana* ``の`` is the ``U+306E`` code point.

components/uid.rst

@@ -331,7 +331,7 @@ type, which converts to/from ULID objects automatically::
         // ...
     }
 
-There's also a Doctrine generator to help autogenerate ULID values for the
+There's also a Doctrine generator to help auto-generate ULID values for the
 entity primary keys::
 
     use Symfony\Bridge\Doctrine\IdGenerator\UlidGenerator;