minor #13949 Update best_practices.rst (elghailani)

javiereguiluz · javiereguiluz · commit f0d7f1d8ed20 · 2020-09-25T17:42:46.000+02:00
This PR was submitted for the 5.0 branch but it was merged into the 4.4 branch instead. Discussion ---------- Update best_practices.rst Improve `Environment Variables`, `Secrets` & `Functional Test` wording Commits ------- 63edb18 Update best_practices.rst
diff --git a/best_practices.rst b/best_practices.rst
@@ -81,7 +81,7 @@ Configuration
 Use Environment Variables for Infrastructure Configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-These are the options that change from one machine to another (e.g. from your
+These are the options that their values changes from one machine to another (e.g. from your
 development machine to the production server) but which don't change the
 application behavior.
 
@@ -92,7 +92,7 @@ Use Secret for Sensitive Information
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 When your application has sensitive configuration - like an API key - you should
-store those securely via :doc:`secrets </configuration/secrets>`.
+store those securely via :doc:`Symfony’s secrets management system </configuration/secrets>`.
 
 Use Parameters for Application Configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -430,19 +430,19 @@ functional test that checks that all application URLs load successfully::
     }
 
 Add this test while creating your application because it requires little effort
-and checks that none of your pages returns an error. Later you'll add more
+and checks that none of your pages returns an error. Later, you'll add more
 specific tests for each page.
 
 Hardcode URLs in a Functional Test
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-In Symfony applications it's recommended to :ref:`generate URLs <routing-generating-urls>`
+In Symfony applications, it's recommended to :ref:`generate URLs <routing-generating-urls>`
 using routes to automatically update all links when a URL changes. However, if a
 public URL changes, users won't be able to browse it unless you set up a
 redirection to the new URL.
 
 That's why it's recommended to use raw URLs in tests instead of generating them
-from routes. Whenever a route changes, tests will break and you'll know that
+from routes. Whenever a route changes, tests will fail and you'll know that
 you must set up a redirection.
 
 .. _`Symfony Demo`: https://github.com/symfony/demo
