From e662f2feaf30f48376fd2c5d077af2633467eec5 Mon Sep 17 00:00:00 2001
From: uma-kt <105046156+uma-kt@users.noreply.github.com>
Date: Fri, 28 Jul 2023 14:40:18 +0530
Subject: [PATCH] rephrased in the release notes

---
 .../release-notes/release-notes-for-kubeslice-oss-1.1.0.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/versioned_docs/version-1.1.0/release-notes/release-notes-for-kubeslice-oss-1.1.0.mdx b/versioned_docs/version-1.1.0/release-notes/release-notes-for-kubeslice-oss-1.1.0.mdx
index b96d3728..39c7973a 100644
--- a/versioned_docs/version-1.1.0/release-notes/release-notes-for-kubeslice-oss-1.1.0.mdx
+++ b/versioned_docs/version-1.1.0/release-notes/release-notes-for-kubeslice-oss-1.1.0.mdx
@@ -40,10 +40,10 @@ value can be set to AES_128_CBC. The default value is AES_256_CBC. This configur
   Key rotation before the gateways are in a healthy condition to ensure a successful rotation process.
 * After detaching a worker cluster from a slice, gateway pods are not deleted.
 * In the current version, the rebalancing feature of gateway redundancy is disabled.
-* We have identified a scenario where, during a Helm upgrade on kubeslice-worker, the NSM (Network Service Mesh) admission 
+* We have identified a scenario where, during a Helm upgrade on Kubeslice Worker, the NSM (Network Service Mesh) admission 
   webhook pod might not be automatically cleaned up in case of a failure. As a result, there could be potential issues 
-  with the old NSM webhook pod lingering from the previous release. Our team is actively working on a resolution for 
-  this problem. Until the fix is implemented, users are advised to manually delete the old NSM webhook pod if encountered
+  with the old NSM webhook pod lingering from the previous release. So users are advised to manually delete the 
+  old NSM webhook pod until the issue is resolved.
 
 ## Issues Fixed