minor #15328 Unifying wording to "configuration parameter" (ThomasLandauer)

This PR was squashed before being merged into the 4.4 branch.

Discussion
----------

Unifying wording to "configuration parameter"

Follow-up of #15326

Commits
-------

40f3f86 Unifying wording to "configuration parameter"

Author: javiereguiluz

best_practices.rst

@@ -130,7 +130,7 @@ Use Constants to Define Options that Rarely Change
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Configuration options like the number of items to display in some listing rarely
-change. Instead of defining them as :ref:`service container parameters <configuration-parameters>`,
+change. Instead of defining them as :ref:`configuration parameters <configuration-parameters>`,
 define them as PHP constants in the related classes. Example::
 
     // src/Entity/Post.php

routing.rst

@@ -269,7 +269,7 @@ arbitrary matching logic:
              *     condition="context.getMethod() in ['GET', 'HEAD'] and request.headers.get('User-Agent') matches '/firefox/i'"
              * )
              *
-             * expressions can also include config parameters:
+             * expressions can also include configuration parameters:
              * condition: "request.headers.get('User-Agent') matches '%app.allowed_browsers%'"
              */
             public function contact(): Response
@@ -285,7 +285,7 @@ arbitrary matching logic:
             path:       /contact
             controller: 'App\Controller\DefaultController::contact'
             condition:  "context.getMethod() in ['GET', 'HEAD'] and request.headers.get('User-Agent') matches '/firefox/i'"
-            # expressions can also include config parameters:
+            # expressions can also include configuration parameters:
             # condition: "request.headers.get('User-Agent') matches '%app.allowed_browsers%'"
 
     .. code-block:: xml
@@ -299,7 +299,7 @@ arbitrary matching logic:
 
             <route id="contact" path="/contact" controller="App\Controller\DefaultController::contact">
                 <condition>context.getMethod() in ['GET', 'HEAD'] and request.headers.get('User-Agent') matches '/firefox/i'</condition>
-                <!-- expressions can also include config parameters: -->
+                <!-- expressions can also include configuration parameters: -->
                 <!-- <condition>request.headers.get('User-Agent') matches '%app.allowed_browsers%'</condition> -->
             </route>
         </routes>
@@ -314,7 +314,7 @@ arbitrary matching logic:
             $routes->add('contact', '/contact')
                 ->controller([DefaultController::class, 'contact'])
                 ->condition('context.getMethod() in ["GET", "HEAD"] and request.headers.get("User-Agent") matches "/firefox/i"')
-                // expressions can also include config parameters:
+                // expressions can also include configuration parameters:
                 // 'request.headers.get("User-Agent") matches "%app.allowed_browsers%"'
             ;
         };
@@ -575,7 +575,7 @@ URL                       Route          Parameters
 .. tip::
 
     Route requirements (and route paths too) can include
-    :ref:`container parameters <configuration-parameters>`, which is useful to
+    :ref:`configuration parameters <configuration-parameters>`, which is useful to
     define complex regular expressions once and reuse them in multiple routes.
 
 .. tip::
@@ -1681,7 +1681,7 @@ these routes.
             [],
             [],
             ['HTTP_HOST' => 'm.example.com']
-            // or get the value from some container parameter:
+            // or get the value from some configuration parameter:
             // ['HTTP_HOST' => 'm.' . $client->getContainer()->getParameter('domain')]
         );