Skip to content

Commit c7939d0

Browse files
committed
minor #16235 [Routing] Correct spelling & grammar in routing.rst (gnito-org)
This PR was merged into the 4.4 branch. Discussion ---------- [Routing] Correct spelling & grammar in routing.rst <!-- 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 `5.x` for features of unreleased versions). --> Commits ------- 1ab923e Correct spelling & grammar in routing.rst
2 parents 20b15c6 + 1ab923e commit c7939d0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

routing.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -583,7 +583,7 @@ URL Route Parameters
583583
Parameters also support `PCRE Unicode properties`_, which are escape
584584
sequences that match generic character types. For example, ``\p{Lu}``
585585
matches any uppercase character in any language, ``\p{Greek}`` matches any
586-
Greek character, etc.
586+
Greek characters, etc.
587587

588588
.. note::
589589

@@ -824,7 +824,7 @@ Parameter Conversion
824824

825825
A common routing need is to convert the value stored in some parameter (e.g. an
826826
integer acting as the user ID) into another value (e.g. the object that
827-
represents the user). This feature is called "param converter".
827+
represents the user). This feature is called a "param converter".
828828

829829
In case you didn't run this command before, run it now to add support for
830830
annotations and "param converters":

0 commit comments

Comments
 (0)