From 2dbfba9ac5cbb63a986f0b4d92daac7a7c667149 Mon Sep 17 00:00:00 2001
From: Seth Jackson <sethjackson@gmail.com>
Date: Tue, 23 May 2017 16:01:11 -0400
Subject: [PATCH] Fix wording.

---
 src/site/markdown/data/database.md.vm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/site/markdown/data/database.md.vm b/src/site/markdown/data/database.md.vm
index b5a6b514d..018a90284 100644
--- a/src/site/markdown/data/database.md.vm
+++ b/src/site/markdown/data/database.md.vm
@@ -20,8 +20,8 @@ To setup a centralized database the following generalized steps can be used:
 <ol><li>Create the database and tables using either <a href="https://github.com/jeremylong/DependencyCheck/blob/master/dependency-check-core/src/main/resources/data/initialize.sql">initialize.sql</a>
    or one of the other initialization scripts <a href="https://github.com/jeremylong/DependencyCheck/tree/master/dependency-check-core/src/main/resources/data">found here</a>.</li>
 <li>The account that the clients will connect using must have select granted on the tables.
-     <ul><li>Note, if the clients performing the scans should run with the noupdate setting. A single
-       instance of the dependency-check client should be setup with update enabled and the account
+     <ul><li>Note, the clients performing the scans should run with the noupdate setting. A single
+       instance of the dependency-check client should be setup with updates enabled and the account
        used during the update process will need to be granted update rights on the tables.
      </li></ul>
 </li><li>Dependency-check clients running scans will need to be configured to use the central database: