symfony
diff --git a/‎reference/configuration/framework.rst
Copy file name to clipboardExpand all lines: reference/configuration/framework.rst
+11-11Lines changed: 11 additions & 11 deletions b/‎reference/configuration/framework.rst
Copy file name to clipboardExpand all lines: reference/configuration/framework.rst
+11-11Lines changed: 11 additions & 11 deletions
diff --git a/‎reference/configuration/security.rst
Copy file name to clipboardExpand all lines: reference/configuration/security.rst
+3-3Lines changed: 3 additions & 3 deletions b/‎reference/configuration/security.rst
Copy file name to clipboardExpand all lines: reference/configuration/security.rst
+3-3Lines changed: 3 additions & 3 deletions
diff --git a/‎reference/configuration/swiftmailer.rst
Copy file name to clipboardExpand all lines: reference/configuration/swiftmailer.rst
+2-2Lines changed: 2 additions & 2 deletions b/‎reference/configuration/swiftmailer.rst
Copy file name to clipboardExpand all lines: reference/configuration/swiftmailer.rst
+2-2Lines changed: 2 additions & 2 deletions
diff --git a/‎reference/configuration/twig.rst
Copy file name to clipboardExpand all lines: reference/configuration/twig.rst
+2-2Lines changed: 2 additions & 2 deletions b/‎reference/configuration/twig.rst
Copy file name to clipboardExpand all lines: reference/configuration/twig.rst
+2-2Lines changed: 2 additions & 2 deletions
diff --git a/‎reference/constraints/Callback.rst
Copy file name to clipboardExpand all lines: reference/constraints/Callback.rst
+1-1Lines changed: 1 addition & 1 deletion b/‎reference/constraints/Callback.rst
Copy file name to clipboardExpand all lines: reference/constraints/Callback.rst
+1-1Lines changed: 1 addition & 1 deletion
diff --git a/‎reference/constraints/DateTime.rst
Copy file name to clipboardExpand all lines: reference/constraints/DateTime.rst
+1-1Lines changed: 1 addition & 1 deletion b/‎reference/constraints/DateTime.rst
Copy file name to clipboardExpand all lines: reference/constraints/DateTime.rst
+1-1Lines changed: 1 addition & 1 deletion
diff --git a/‎reference/constraints/_comparison-value-option.rst.inc
Copy file name to clipboardExpand all lines: reference/constraints/_comparison-value-option.rst.inc
+1-1Lines changed: 1 addition & 1 deletion b/‎reference/constraints/_comparison-value-option.rst.inc
Copy file name to clipboardExpand all lines: reference/constraints/_comparison-value-option.rst.inc
+1-1Lines changed: 1 addition & 1 deletion
diff --git a/‎reference/constraints/_groups-option.rst.inc
Copy file name to clipboardExpand all lines: reference/constraints/_groups-option.rst.inc
+1-1Lines changed: 1 addition & 1 deletion b/‎reference/constraints/_groups-option.rst.inc
Copy file name to clipboardExpand all lines: reference/constraints/_groups-option.rst.inc
+1-1Lines changed: 1 addition & 1 deletion
diff --git a/‎reference/dic_tags.rst
Copy file name to clipboardExpand all lines: reference/dic_tags.rst
+3-3Lines changed: 3 additions & 3 deletions b/‎reference/dic_tags.rst
Copy file name to clipboardExpand all lines: reference/dic_tags.rst
+3-3Lines changed: 3 additions & 3 deletions
@@ -855,7 +855,7 @@ timeout
 
 **type**: ``float`` **default**: depends on your PHP config
 
-Time, in seconds, to wait for a response. If the response stales for longer, a
+Time, in seconds, to wait for a response. If the response takes longer, a
 :class:`Symfony\\Component\\HttpClient\\Exception\\TransportException` is thrown.
 Its default value is the same as the value of PHP's `default_socket_timeout`_
 config option.
@@ -1070,7 +1070,7 @@ when using ``.``, instead of matching only a single byte.
 
 If the charset of your application is UTF-8 (as defined in the
 :ref:`getCharset() method <configuration-kernel-charset>` of your kernel) it's
-recommended to set it to ``true``. This will make non-UTF8 URLs to generate 404
+recommended setting it to ``true``. This will make non-UTF8 URLs to generate 404
 errors.
 
 .. _config-framework-session:
@@ -1191,8 +1191,8 @@ cookie_samesite
 
 **type**: ``string`` or ``null`` **default**: ``null``
 
-It controls the way cookies are sent when the HTTP request was not originated
-from the same domain the cookies are associated to. Setting this option is
+It controls the way cookies are sent when the HTTP request did not originate
+from the same domain that is associated with the cookies. Setting this option is
 recommended to mitigate `CSRF security attacks`_.
 
 By default, browsers send all cookies related to the domain of the HTTP request.
@@ -1210,7 +1210,7 @@ The possible values for this option are:
   (previously this was the default behavior of null, but in newer browsers ``'lax'``
   would be applied when the header has not been set)
 * ``'strict'`` (or the ``Cookie::SAMESITE_STRICT`` constant), use it to never
-  send any cookie when the HTTP request is not originated from the same domain.
+  send any cookie when the HTTP request did not originate from the same domain.
 * ``'lax'`` (or the ``Cookie::SAMESITE_LAX`` constant), use it to allow sending
   cookies when the request originated from a different domain, but only when the
   user consciously made the request (by clicking a link or submitting a form
@@ -1282,7 +1282,7 @@ sid_bits_per_character
 
 **type**: ``integer`` **default**: ``4``
 
-This determines the number of bits in encoded session ID character. The possible
+This determines the number of bits in the encoded session ID character. The possible
 values are ``4`` (0-9, a-f), ``5`` (0-9, a-v), and ``6`` (0-9, a-z, A-Z, "-", ",").
 The more bits results in stronger session ID. ``5`` is recommended value for
 most environments.
@@ -2134,7 +2134,7 @@ The service that is used to persist class metadata in a cache. The service
 has to implement the :class:`Symfony\\Component\\Validator\\Mapping\\Cache\\CacheInterface`.
 
 Set this option to ``validator.mapping.cache.doctrine.apc`` to use the APC
-cache provide from the Doctrine project.
+cache provided by the Doctrine project.
 
 .. _reference-validation-enable_annotations:
 
@@ -2191,7 +2191,7 @@ By default, the :doc:`NotCompromisedPassword </reference/constraints/NotCompromi
 constraint uses the public API provided by `haveibeenpwned.com`_. This option
 allows to define a different, but compatible, API endpoint to make the password
 checks. It's useful for example when the Symfony application is run in an
-intranet without public access to Internet.
+intranet without public access to the internet.
 
 static_method
 .............
@@ -2547,7 +2547,7 @@ A list of cache pools to be created by the framework extension.
 
 .. seealso::
 
-    For more information about how pools works, see :ref:`cache pools <component-cache-cache-pools>`.
+    For more information about how pools work, see :ref:`cache pools <component-cache-cache-pools>`.
 
 To configure a Redis cache pool with a default lifetime of 1 hour, do the following:
 
@@ -2656,8 +2656,8 @@ provider
 
 Overwrite the default service name or DSN respectively, if you do not want to
 use what is configured as ``default_X_provider`` under ``cache``. See the
-description of the default provider setting above for the type of adapter
-you use for information on how to specify the provider.
+description of the default provider setting above for information on how to
+specify your specific provider.
 
 clearer
 """""""
 
@@ -51,7 +51,7 @@ access_denied_url
 **type**: ``string`` **default**: ``null``
 
 Defines the URL where the user is redirected after a ``403`` HTTP error (unless
-you define a custom access deny handler). Example: ``/no-permission``
+you define a custom access denial handler). Example: ``/no-permission``
 
 always_authenticate_before_granting
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -297,7 +297,7 @@ password) so you don't have to deal with it.
 Using the "auto" Password Encoder
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-It selects automatically the best possible encoder. Currently, it tries to use
+It automatically selects the best possible encoder. Currently, it tries to use
 Sodium by default and falls back to the `bcrypt password hashing function`_ if
 not possible. In the future, when PHP adds new hashing techniques, it may use
 different password hashers.
@@ -452,7 +452,7 @@ This is the route or path that the user will be redirected to (unless ``use_forw
 is set to ``true``) when they try to access a protected resource but isn't
 fully authenticated.
 
-This path **must** be accessible by a normal, un-authenticated user, else
+This path **must** be accessible by a normal, unauthenticated user, else
 you may create a redirect loop.
 
 check_path
 
@@ -106,7 +106,7 @@ local_domain
 
     The ``local_domain`` option was introduced in SwiftMailerBundle 2.4.0.
 
-The domain name to use in ``HELO`` command.
+The domain name to use in the ``HELO`` command.
 
 encryption
 ~~~~~~~~~~
@@ -172,7 +172,7 @@ sleep
 **type**: ``integer`` **default**: ``0``
 
 Used with ``Swift_Plugins_AntiFloodPlugin``. This is the number of seconds
-to sleep for during a transport restart.
+to sleep during a transport restart.
 
 .. _delivery-address:
 
 
@@ -129,7 +129,7 @@ format
 **type**: ``string`` **default**: ``F j, Y H:i``
 
 The format used by the ``date`` filter to display values when no specific format
-is passed as argument.
+is passed as an argument.
 
 interval_format
 ...............
@@ -145,7 +145,7 @@ timezone
 **type**: ``string`` **default**: (the value returned by ``date_default_timezone_get()``)
 
 The timezone used when formatting date values with the ``date`` filter and no
-specific timezone is passed as argument.
+specific timezone is passed as an argument.
 
 debug
 ~~~~~
 
@@ -222,7 +222,7 @@ You can then use the following configuration to invoke this validator:
 
     The Callback constraint does *not* support global callback functions
     nor is it possible to specify a global function or a service method
-    as callback. To validate using a service, you should
+    as a callback. To validate using a service, you should
     :doc:`create a custom validation constraint </validation/custom_constraint>`
     and add that new constraint to your class.
 
 
@@ -85,7 +85,7 @@ Options
 
 **type**: ``string`` **default**: ``Y-m-d H:i:s``
 
-This option allows to validate a custom date format. See
+This option allows you to validate a custom date format. See
 :phpmethod:`DateTime::createFromFormat` for formatting options.
 
 .. include:: /reference/constraints/_groups-option.rst.inc
 
@@ -3,5 +3,5 @@
 
 **type**: ``mixed`` [:ref:`default option <validation-default-option>`]
 
-This option is required. It defines the value to compare to. It can be a
+This option is required. It defines the comparison value. It can be a
 string, number or object.
@@ -3,5 +3,5 @@
 
 **type**: ``array`` | ``string``
 
-It defines the validation group or groups this constraint belongs to. Read more
+It defines the validation group or groups of this constraint. Read more
 about :doc:`validation groups </validation/groups>`.
@@ -166,7 +166,7 @@ are propagated to their related listeners.
 
 It will replace, in cache for generated service factories, the PHP autoload by
 plain inlined ``include_once``. The benefit is a complete bypass of the autoloader
-for services and their class hierarchy. The result is as significant performance improvement.
+for services and their class hierarchy. The result is a significant performance improvement.
 
 Use this tag with great caution, you have to be sure that the tagged service is always used.
 
@@ -246,7 +246,7 @@ kernel.cache_clearer
 process
 
 Cache clearing occurs whenever you call ``cache:clear`` command. If your
-bundle caches files, you should add custom cache clearer for clearing those
+bundle caches files, you should add a custom cache clearer for clearing those
 files during the cache clearing process.
 
 In order to register your custom cache clearer, first you must create a
@@ -1157,7 +1157,7 @@ twig.runtime
 **Purpose**: To register a custom Lazy-Loaded Twig Extension
 
 :ref:`Lazy-Loaded Twig Extensions <lazy-loaded-twig-extensions>` are defined as
-regular services but the need to be tagged with ``twig.runtime``. If you're using the
+regular services but they need to be tagged with ``twig.runtime``. If you're using the
 :ref:`default services.yaml configuration <service-container-services-load-example>`,
 the service is auto-registered and auto-tagged. But, you can also register it manually: