Skip to content

Commit 279b2fe

Browse files
authored
Update secrets.rst
1 parent e4fd90c commit 279b2fe

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

configuration/secrets.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -66,15 +66,15 @@ This will generate ``config/secrets/prod/prod.encrypt.public.php`` and
6666
Create or Update Secrets
6767
------------------------
6868

69-
Suppose you want to store your database password a secret. By using the
69+
Suppose you want to store your database password as a secret. By using the
7070
``secrets:set`` command, you should add this secret to both the ``dev`` *and*
7171
``prod`` vaults:
7272

7373
.. code-block:: terminal
7474
75-
# the input is hidden as you type for security
75+
# the input is hidden as you type for security reason
7676
77-
# set your a default development value (can be overridden locally)
77+
# set your development value (default, can be overridden locally)
7878
$ php bin/console secrets:set DATABASE_PASSWORD
7979
8080
# set your production value
@@ -102,7 +102,7 @@ Secret values can be referenced in the same way as
102102
accidentally define a secret *and* an environment variable with the same name:
103103
**environment variables override secrets**.
104104

105-
If you stored a ``DATABASE_PASSWORD`` secret, you can reference by:
105+
If you stored a ``DATABASE_PASSWORD`` secret, you can reference it by:
106106

107107
.. configuration-block::
108108

@@ -256,7 +256,7 @@ your secrets during deployment to the "local" vault:
256256
$ php bin/console secrets:decrypt-to-local --force --env=prod
257257
258258
This will write all the decrypted secrets into the ``.env.prod.local`` file.
259-
After doing this, the decryption key does *not* need to remain on the server.
259+
After doing this, the decryption key does *not* need to remain on the server(s).
260260

261261
Rotating Secrets
262262
----------------

0 commit comments

Comments
 (0)