minor #9932 Fixed typos (pborreli)

This PR was merged into the 3.4 branch.

Discussion
----------

Fixed typos

Commits
-------

fbc9066 Fixed typos

Author: javiereguiluz

components/cache/adapters/chain_adapter.rst

@@ -46,7 +46,7 @@ slowest storage engines, :class:`Symfony\\Component\\Cache\\Adapter\\ApcuAdapter
     ));
 
 When calling this adapter's :method:`Symfony\\Component\\Cache\\ChainAdapter::prune` method,
-the call is deligated to all its compatibe cache adapters. It is safe to mix both adapters
+the call is delegated to all its compatible cache adapters. It is safe to mix both adapters
 that *do* and do *not* implement :class:`Symfony\\Component\\Cache\\PruneableInterface`, as
 incompatible adapters are silently ignored::
 

components/cache/cache_pools.rst

@@ -155,18 +155,18 @@ Pruning Cache Items
     Cache adapter pruning functionality was introduced in Symfony 3.4.
 
 Some cache pools do not include an automated mechanism for pruning expired cache items.
-For example, the :ref:`FilesystemAdaper <component-cache-filesystem-adapter>` cache
+For example, the :ref:`FilesystemAdapter <component-cache-filesystem-adapter>` cache
 does not remove expired cache items *until an item is explicitly requested and determined to
 be expired*, for example, via a call to ``Psr\\Cache\\CacheItemPoolInterface::getItem``.
 Under certain workloads, this can cause stale cache entries to persist well past their
 expiration, resulting in a sizable consumption of wasted disk or memory space from excess,
 expired cache items.
 
-This shortcomming has been solved through the introduction of
+This shortcoming has been solved through the introduction of
 :class:`Symfony\\Component\\Cache\\PruneableInterface`, which defines the abstract method
 :method:`Symfony\\Component\\Cache\\PruneableInterface::prune`. The
 :ref:`ChainAdapter <component-cache-chain-adapter>`,
-:ref:`FilesystemAdaper <component-cache-filesystem-adapter>`,
+:ref:`FilesystemAdapter <component-cache-filesystem-adapter>`,
 :ref:`PdoAdapter <pdo-doctrine-adapter>`, and
 :ref:`PhpFilesAdapter <component-cache-files-adapter>` all implement this new interface,
 allowing manual removal of stale cache items::
@@ -180,7 +180,7 @@ allowing manual removal of stale cache items::
 The :ref:`ChainAdapter <component-cache-chain-adapter>` implementation does not directly
 contain any pruning logic itself. Instead, when calling the chain adapter's
 :method:`Symfony\\Component\\Cache\\ChainAdapter::prune` method, the call is delegated to all
-its compatibe cache adapters (and those that do not implement ``PruneableInterface`` are
+its compatible cache adapters (and those that do not implement ``PruneableInterface`` are
 silently ignored)::
 
     use Symfony\Component\Cache\Adapter\ApcuAdapter;

frontend/encore/legacy-apps.rst

@@ -19,7 +19,7 @@ Using Libraries that Expect jQuery to be Global
 Some legacy JavaScript applications use programming practices that don't play
 well with the new practices promoted by Webpack. The most common of these
 problems is using code (e.g. jQuery plugins) that assume that jQuery is already
-available via the the ``$`` or ``jQuery`` global variables. If those variables
+available via the ``$`` or ``jQuery`` global variables. If those variables
 are not defined, you'll get these errors:
 
 .. code-block:: text

security/ldap.rst

@@ -190,13 +190,13 @@ use the ``ldap`` user provider.
     provider is used. However, the LDAP component itself does not provide
     any escaping yet. Thus, it's your responsibility to prevent LDAP injection
     attacks when using the component directly.
-    
+
 .. caution::
 
-    The user configured above in the the user provider is only used to retrieve
+    The user configured above in the user provider is only used to retrieve
     data. It's a static user defined by its username and password (for improved
     security, define the password as an environment variable).
-    
+
     If your LDAP server allows to retrieve information anonymously, you can
     set the ``search_dn`` and ``search_password`` options to ``null``.
 
@@ -207,7 +207,7 @@ service
 
 **type**: ``string`` **default**: ``ldap``
 
-This is the name of your configured LDAP client. You can freely chose the
+This is the name of your configured LDAP client. You can freely choose the
 name, but it must be unique in your application and it cannot start with a
 number or contain white spaces.
 
@@ -286,7 +286,7 @@ service
 
 **type**: ``string`` **default**: ``ldap``
 
-This is the name of your configured LDAP client. You can freely chose the
+This is the name of your configured LDAP client. You can freely choose the
 name, but it must be unique in your application and it cannot start with a
 number or contain white spaces.