diff --git a/content/code-security/concepts/vulnerability-reporting-and-management/repository-security-advisories.md b/content/code-security/concepts/vulnerability-reporting-and-management/repository-security-advisories.md
index bec280be2da4..6ee6a5b16b54 100644
--- a/content/code-security/concepts/vulnerability-reporting-and-management/repository-security-advisories.md
+++ b/content/code-security/concepts/vulnerability-reporting-and-management/repository-security-advisories.md
@@ -81,6 +81,6 @@ Whenever possible, you should **add a fix version to a security advisory prior t
 
 Depending on the vulnerability, you may need to adjust your approach. If a fix version is:
 
-* **Imminently available**, and you are able to, wait to disclose the issue when the fix is ready.
+* **Imminently available**, and you are able to wait to disclose the issue when the fix is ready.
 * **In development but not yet available**, mention this in the advisory, and edit the advisory later, after publication.
 * **Not planned**, be clear about it in the advisory so that your users don't contact you to ask when a fix will be made. In this case, it is helpful to include steps users can take to mitigate the issue.