@@ -5,7 +5,7 @@ How to Organize Configuration Files
55===================================
66
77The Symfony skeleton defines three:doc: `execution environments </configuration/environments >`
8- called ``dev ``, ``prod `` and ``test ``. An environmentsimply represents a way
8+ called ``dev ``, ``prod `` and ``test ``. An environment represents a way
99to execute the same codebase with different configurations.
1010
1111In order to select the configuration file to load for each environment, Symfony
@@ -129,9 +129,9 @@ Global Configuration Files
129129
130130Some system administrators may prefer to store sensitive parameters in files
131131outside the project directory. Imagine that the database credentials for your
132- website are stored in the ``/etc/sites/mysite.com/parameters.yaml `` file.Loading
133- this file is as simple as indicating the full file path when importing it from
134- any other configuration file:
132+ website are stored in the ``/etc/sites/mysite.com/parameters.yaml `` file.You
133+ can load files from outside the project folder by indicating the full file path
134+ when importing it from any other configuration file:
135135
136136..configuration-block ::
137137