diff --git a/website/versioned_docs/version-v3.6.x/audit.md b/website/versioned_docs/version-v3.6.x/audit.md
index 1d6b73a792e..38e54fb1175 100644
--- a/website/versioned_docs/version-v3.6.x/audit.md
+++ b/website/versioned_docs/version-v3.6.x/audit.md
@@ -13,7 +13,7 @@ There are three ways to gather audit results, depending on the level of detail n
 
 Prometheus metrics provide an aggregated look at the number of audit violations:
 
-* `gatekeeper_audit_last_run_time` provides the timestamp of the most recently completed audit run
+* `gatekeeper_audit_last_run_time` provides the timestamp of the most recently started audit run
 * `gatekeeper_violations` provides the total number of audited violations for the last audit run, broken down by violation severity
 
 ### Constraint Status
diff --git a/website/versioned_docs/version-v3.7.x/audit.md b/website/versioned_docs/version-v3.7.x/audit.md
index f8b520c38a0..799f7c6f1f9 100644
--- a/website/versioned_docs/version-v3.7.x/audit.md
+++ b/website/versioned_docs/version-v3.7.x/audit.md
@@ -13,7 +13,7 @@ There are three ways to gather audit results, depending on the level of detail n
 
 Prometheus metrics provide an aggregated look at the number of audit violations:
 
-* `gatekeeper_audit_last_run_time` provides the timestamp of the most recently completed audit run
+* `gatekeeper_audit_last_run_time` provides the timestamp of the most recently started audit run
 * `gatekeeper_violations` provides the total number of audited violations for the last audit run, broken down by violation severity
 
 ### Constraint Status
diff --git a/website/versioned_docs/version-v3.8.x/audit.md b/website/versioned_docs/version-v3.8.x/audit.md
index f8b520c38a0..799f7c6f1f9 100644
--- a/website/versioned_docs/version-v3.8.x/audit.md
+++ b/website/versioned_docs/version-v3.8.x/audit.md
@@ -13,7 +13,7 @@ There are three ways to gather audit results, depending on the level of detail n
 
 Prometheus metrics provide an aggregated look at the number of audit violations:
 
-* `gatekeeper_audit_last_run_time` provides the timestamp of the most recently completed audit run
+* `gatekeeper_audit_last_run_time` provides the timestamp of the most recently started audit run
 * `gatekeeper_violations` provides the total number of audited violations for the last audit run, broken down by violation severity
 
 ### Constraint Status
diff --git a/website/versioned_docs/version-v3.9.x/audit.md b/website/versioned_docs/version-v3.9.x/audit.md
index 9802324ea42..b561c8fe111 100644
--- a/website/versioned_docs/version-v3.9.x/audit.md
+++ b/website/versioned_docs/version-v3.9.x/audit.md
@@ -13,7 +13,7 @@ There are three ways to gather audit results, depending on the level of detail n
 
 Prometheus metrics provide an aggregated look at the number of audit violations:
 
-* `gatekeeper_audit_last_run_time` provides the timestamp of the most recently completed audit run
+* `gatekeeper_audit_last_run_time` provides the timestamp of the most recently started audit run
 * `gatekeeper_violations` provides the total number of audited violations for the last audit run, broken down by violation severity
 
 ### Constraint Status