From 48763385cae89933333c27cc5981715c031bebe1 Mon Sep 17 00:00:00 2001 From: Aniruddha Adak Date: Thu, 24 Sep 2026 21:38:40 +0530 Subject: [PATCH] docs(code-security): fix advisory disclosure punctuation --- .../repository-security-advisories.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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.