From 80e1e9852cca2ff3be371ce2256e97bf33793bcc Mon Sep 17 00:00:00 2001
From: Pallavi <96553709+pallsama@users.noreply.github.com>
Date: Wed, 23 Oct 2024 04:44:03 -0700
Subject: [PATCH] Remove a resolved known issue from 3.13.4 release notes
 (#52474)

Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>
---
 data/release-notes/enterprise-server/3-13/4.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/data/release-notes/enterprise-server/3-13/4.yml b/data/release-notes/enterprise-server/3-13/4.yml
index 37c95aeaa719..5b87c637d477 100644
--- a/data/release-notes/enterprise-server/3-13/4.yml
+++ b/data/release-notes/enterprise-server/3-13/4.yml
@@ -72,7 +72,7 @@ sections:
       When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
     - |
       Services may respond with a `503` status due to an out of date `haproxy` configuration. This can usually be resolved with a `ghe-config-apply` run.
-    - |
-      Instance setup in AWS with IMDSv2 enforced fails if no public IP is present.
     - |
       For customers using Secret Scanning, internal jobs were created and not worked that could contribute to performance issues.
+  errata:
+    - 'The "[Known issues](/admin/release-notes#3.13.4-known-issues)" section previously indicated that `Instance setup in AWS with IMDSv2 enforced fails if no public IP is present` is still an issue. The issue is resolved and is documented in the "[Bug fixes](/admin/release-notes#3.13.4-bugs)" section. [Updated: 2024-09-30]'