@@ -84,7 +84,8 @@ name as the environment:
84
84
├─ vendor/
85
85
└─ web/
86
86
87
- To make it work, change the code of the ``registerContainerConfiguration() ``
87
+ To make this work, change the code of the
88
+ :method: `Symfony\\ Component\\ HttpKernel\\ KernelInterface::registerContainerConfiguration `
88
89
method::
89
90
90
91
// app/AppKernel.php
@@ -107,7 +108,7 @@ files, including the common files:
107
108
108
109
# app/config/dev/config.yml
109
110
imports :
110
- - { resource: '../common/config.yml' }
111
+ - { resource: '../common/config.yml' }
111
112
- { resource: 'parameters.yml' }
112
113
- { resource: 'security.yml' }
113
114
@@ -222,7 +223,7 @@ Semantic Configuration Files
222
223
223
224
A different organization strategy may be needed for complex applications with
224
225
large configuration files. For instance, you could create one file per bundle
225
- and several files to define all the application services:
226
+ and several files to define all application services:
226
227
227
228
.. code-block :: text
228
229
@@ -473,5 +474,5 @@ doesn't exist:
473
474
474
475
As you've seen, there are lots of ways to organize your configuration files. You
475
476
can choose one of these or even create your own custom way of organizing the
476
- files. Don't feel limited by the standard edition that comes with Symfony. For even
477
+ files. Don't feel limited by the Standard Edition that comes with Symfony. For even
477
478
more customization, see ":doc: `dir_structure `".
0 commit comments