Small improvements to OSSEC guide.

docs/admin/installation/install.rst

@@ -33,8 +33,6 @@ on network speed and computing power.
                **not** as root. Contact the SecureDrop team if the package
                installation encounters repeated errors.
 
-.. _configure_securedrop:
-
 Localization of the *Source Interface* and *Journalist Interface*
 -----------------------------------------------------------------
 
@@ -52,6 +50,8 @@ parentheses.
           French to be available to read the documents and follow up in that
           language.
 
+.. _configure_securedrop:
+
 Configure the Installation
 --------------------------
 

docs/admin/maintenance/ossec_alerts.rst

@@ -31,12 +31,11 @@ the destination address can be [email protected].
 
 What you need:
 
-- The *OSSEC Alert Public Key*
-- The fingerprint of the key used when encrypting OSSEC alerts
+- The *OSSEC Alert Public Key* and its fingerprint
 - The email address that will receive alerts from OSSEC
 - The reachable hostname of your SMTP relay
 - The secure SMTP port of your SMTP relay
-  (typically 25, 587, or 465. must support TLS encryption)
+  (typically 25, 587, or 465; must support TLS encryption)
 - An email username to authenticate to the SMTP relay
 - The domain name of the email used to send OSSEC alerts
 - The password of the email used to send OSSEC alerts
@@ -56,8 +55,11 @@ solutions should be able to meet those requirements.
 
 These values must be set in the 
 :ref:`configuration playbook<configure_securedrop>` by running the
-``securedrop-admin sdconfig`` command, which will prompt for each of the
-items listed above.
+``./securedrop-admin sdconfig`` command, which will prompt for each of the
+items listed above. Please note, this command updates the configuration,
+but does not apply it to the servers. Any time you make changes to
+the configuration it is necessary to deploy them with the
+``./securedrop-admin install`` command.
 
 If you don't know what value to enter for one of these, please ask your
 organization's email admin for the full configuration before
@@ -82,7 +84,7 @@ although we've described some common scenarios in the
 
 If you have your *OSSEC Alert Public Key* public key handy, copy it to
 ``install_files/ansible-base`` and then specify the filename, e.g.
-``ossec.pub``, when prompted by ``securedrop-admin sdconfig``.
+``ossec.pub``, when prompted by ``./securedrop-admin sdconfig``.
 
 If you don't have your GPG key ready, you can run GnuPG on the command line in
 order to find, import, and export your public key. It's best to copy the key