tweaks thanks to review

weaverryan · weaverryan · commit cd066cc0b752 · 2020-01-26T12:34:18.000-05:00
diff --git a/configuration/secrets.rst b/configuration/secrets.rst
@@ -28,7 +28,7 @@ store them by using Symfony's secrets management system - sometimes called a
 Generate Cryptographic Keys
 ---------------------------
 
-In order to encrypt and decrypt **secrets**, symfony needs **cryptographic keys**.
+In order to encrypt and decrypt **secrets**, Symfony needs **cryptographic keys**.
 A pair of keys can be generated by running:
 
 .. code-block:: terminal
@@ -199,7 +199,7 @@ If you entered ``root``, you will now see this in your ``.env.dev.local`` file:
     DATABASE_PASSWORD=root
 
 This will *override* the ``DATABASE_PASSWORD`` secret because environment variables
-always "win" over secrets.
+always take precedence over secrets.
 
 Listing the secrets will now also display the local variable:
 
@@ -229,11 +229,11 @@ values via the ``.env.test`` file:
     # .env.test
     DATABASE_PASSWORD="testing"
 
-Deploy secrets to production
+Deploy Secrets to Production
 ----------------------------
 
-Because the **decryption key** is not committed, you'll need to manually
-store this file somewhere and deploy it. There are 2 ways to do that:
+Due to the fact that decryption keys should never be committed, you will need to
+manually store this file somewhere and deploy it. There are 2 ways to do that:
 
 1) Uploading the file:
 
@@ -317,5 +317,4 @@ The secrets system is enabled by default and some of its behavior can be configu
 
 
 .. _`libsodium`: https://pecl.php.net/package/libsodium
-.. _`sodium_compatparagonie/sodium_compat`: https://packagist.org/packages/paragonie/sodium_compat
 .. _`paragonie/sodium_compat`: https://github.com/paragonie/sodium_compat
