Fix misc grammar issues

best_practices.rst

@@ -200,7 +200,7 @@ If you use the :ref:`default services.yaml configuration <service-container-serv
 most services will be configured automatically. However, in some edge cases
 you'll need to configure services (or parts of them) manually.
 
-YAML is the format recommended configuring services because it's friendly to
+YAML is the format recommended for configuring services because it's friendly to
 newcomers and concise, but Symfony also supports XML and PHP configuration.
 
 Use Attributes to Define the Doctrine Entity Mapping

lock.rst

@@ -239,7 +239,7 @@ processes asking for the same ``$version``::
 Naming Locks
 ------------
 
-If the application needs different kind of Stores alongside each other, Symfony
+If the application needs different kinds of stores alongside each other, Symfony
 provides :ref:`named lock <reference-lock-resources-name>`:
 
 .. configuration-block::

mercure.rst

@@ -4,7 +4,7 @@ Pushing Data to Clients Using the Mercure Protocol
 Being able to broadcast data in real-time from servers to clients is a
 requirement for many modern web and mobile applications.
 
-Creating a UI reacting in live to changes made by other users
+Creating a UI reacting live to changes made by other users
 (e.g. a user changes the data currently browsed by several other users,
 all UIs are instantly updated),
 notifying the user when :doc:`an asynchronous job </messenger>` has been
@@ -726,11 +726,11 @@ Async dispatching
     usually not necessary.
 
 Instead of calling the ``Publisher`` service directly, you can also let Symfony
-dispatching the updates asynchronously thanks to the provided integration with
+dispatch the updates asynchronously thanks to the provided integration with
 the Messenger component.
 
 First, be sure :doc:`to install the Messenger component </messenger>`
-and to configure properly a transport (if you don't, the handler will
+and to properly configure a transport (if you don't, the handler will
 be called synchronously).
 
 Then, dispatch the Mercure ``Update`` to the Messenger's Message Bus,

migration.rst

@@ -131,7 +131,7 @@ Additionally legacy code tends to be hard to write tests for, making the process
 slow and cumbersome.
 
 Instead of providing low level tests, that ensure each class works as expected, it
-might makes sense to write high level tests ensuring that at least anything user
+might make sense to write high level tests ensuring that at least anything user
 facing works on at least a superficial level. These kinds of tests are commonly
 called End-to-End tests, because they cover the whole application from what the
 user sees in the browser down to the very code that is being run and connected

page_creation.rst

@@ -237,7 +237,7 @@ Great news! You've already worked inside the most important directories in your
 project:
 
 ``config/``
-    Contains... configuration!. You will configure routes,
+    Contains configuration. You will configure routes,
     :doc:`services </service_container>` and packages.
 
 ``src/``

rate_limiter.rst

@@ -76,7 +76,7 @@ To achieve this, the rate limit is approximated based on the current window and
 the previous window.
 
 For example: the limit is 5,000 requests per hour; a user made 4,000 requests
-the previous hour and 500 requests this hour. 15 minutes in to the current hour
+the previous hour and 500 requests this hour. 15 minutes into the current hour
 (25% of the window) the hit count would be calculated as: 75% * 4,000 + 500 = 3,500.
 At this point in time the user can only do 1,500 more requests.