Minor rewords

Author: javiereguiluz

rate_limiter.rst

@@ -356,18 +356,15 @@ the :class:`Symfony\\Component\\RateLimiter\\Reservation` object returned by the
         }
     }
 
-Storing Rate Limiter State: Caching
------------------------------------
+Storing Rate Limiter State
+--------------------------
 
-All rate limiter policies require to store the state of the rate limiter
-(e.g. how many hits were already made in the current time window). This
-state is stored by default using the :doc:`Cache component </cache>`.
+All rate limiter policies require to store their state(e.g. how many hits were
+already made in the current time window). By default, all limiters use the
+``cache.rate_limiter`` cache pool created with the :doc:`Cache component </cache>`.
 
-The default cache pool used by all limiters is ``cache.rate_limiter``. You
-can modify this cache pool by :ref:`defining a "rate_limiter" pool <cache-create-pools>`.
-
-You can also override the pool for a specific limiter using the ``cache_pool``
-option:
+Use the ``cache_pool`` option to override the cache used by a specific limiter
+(or even :ref:`create a new cache pool <cache-create-pools>` for it):
 
 .. configuration-block::
 
@@ -428,19 +425,19 @@ option:
     Instead of using the Cache component, you can also implement a custom
     storage. Create a PHP class that implements the
     :class:`Symfony\\Component\\RateLimiter\\Storage\\StorageInterface` and
-    set the ``storage_service`` setting of each limiter to the service ID
+    use the ``storage_service`` setting of each limiter to the service ID
     of this class.
 
 Using Locks to Prevent Race Conditions
 --------------------------------------
 
-Rate limiting can be affected by race conditions, if the same limiter is
-applied to simultaneous requests (e.g. 3 servers of the same client call
-the same API). To prevent these race conditions, the rate limiting
-operations are protected using :doc:`locks </lock>`.
+`Race conditions`_ can happen when the same rate limiter is used by multiple
+simultaneous requests (e.g. three servers of a company hitting your API at the
+same time). Rate limiters use :doc:`locks </lock>` to protect their operations
+against these race conditions.
 
-By default, the global lock (configured by ``framework.lock``) is used. You
-can use a specific :ref:`named lock <lock-named-locks>` via the
+By default, Symfony uses the global lock configured by ``framework.lock``), but
+you can use a specific :ref:`named lock <lock-named-locks>` via the
 ``lock_factory`` option:
 
 .. configuration-block::
@@ -502,3 +499,4 @@ can use a specific :ref:`named lock <lock-named-locks>` via the
 .. _`NGINX rate limiting`: https://www.nginx.com/blog/rate-limiting-nginx/
 .. _`token bucket algorithm`: https://en.wikipedia.org/wiki/Token_bucket
 .. _`PHP date relative formats`: https://www.php.net/datetime.formats.relative
+.. _`Race conditions`: https://en.wikipedia.org/wiki/Race_condition