diff --git a/docs/en-US/about-password-encryption.xml b/docs/en-US/about-password-encryption.xml
index 3cd84d19508..6c11c579ed2 100644
--- a/docs/en-US/about-password-encryption.xml
+++ b/docs/en-US/about-password-encryption.xml
@@ -52,7 +52,7 @@
   <para>Of course, the database secret key itself can not be stored in the open – it must be
     encrypted. How then does &PRODUCT; read it? A second secret key must be provided from an
     external source during Management Server startup. This key can be provided in one of two ways:
-    loaded from a file or provided by the &PRODUCT; administrator. The &PRODUCT; database has a new
+    loaded from a file or provided by the &PRODUCT; administrator. The &PRODUCT; database has a
     configuration setting that lets it know which of these methods will be used. If the encryption
     type is set to "file," the key must be in a file in a known location. If the encryption type is
     set to "web," the administrator runs the utility