diff --git a/docs/plugins/plugin-directory-audit.md b/docs/plugins/plugin-directory-audit.md
index 69eb33da88..9e82cb6de5 100644
--- a/docs/plugins/plugin-directory-audit.md
+++ b/docs/plugins/plugin-directory-audit.md
@@ -9,9 +9,9 @@ description: Details about the process for auditing plugins in the directory
 We have a simple process in place to audit the plugins in the Plugin Directory:
 
 1. On a quarterly basis we run the following script: `node ./scripts/plugin-directory-audit.js --audit`
-2. This script will flag any plugin that has not been updated on NPM in more than 365 days as `archived` if it was `inactive`.
-3. It will also flag any plugin as `inactive` that has not been updated on NPM in more than 365 days if it was `active`.
-4. For any plugin flagged as `inactive` or `archived` and have been updated on NPM in less than 365 days they will be flagged as `active` again.
+2. This script will flag any plugin as `inactive` that has not been updated on NPM in more than 365 days if it was `active`.
+3. It will also flag any plugin that has not been updated on NPM in more than 365 days as `archived` if it was `inactive`.
+4. For any plugin flagged as `inactive` or `archived` and has been updated on NPM in less than 365 days they will be flagged as `active` again.
 5. These changes will then be submitted as a PR, approved and merged.
 
 The impact of a plugin being set to `inactive` means they will show in the inactive section at the bottom of the Plugin Directory. A plugin that is set to `archived` will **not** show up in the Plugin Directory at all.