From e7d4b1935492b60b45015497608d0c659427f351 Mon Sep 17 00:00:00 2001
From: Greg <miernicki_gregory@bah.com>
Date: Tue, 11 Mar 2025 17:20:18 -0500
Subject: [PATCH] =?UTF-8?q?=20=E2=9B=B5?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/guides/using-bigbang/migrating-istio-in-bb3.0.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/guides/using-bigbang/migrating-istio-in-bb3.0.md b/docs/guides/using-bigbang/migrating-istio-in-bb3.0.md
index b42a00cbba..a79e507c94 100644
--- a/docs/guides/using-bigbang/migrating-istio-in-bb3.0.md
+++ b/docs/guides/using-bigbang/migrating-istio-in-bb3.0.md
@@ -1,6 +1,6 @@
 # Upgrading from the Istio Operator to Helm based Istio 
 
-### *The new service mesh is BETA in Big Bang 2.x and is planned to be completely stable in 3.0!*
+### *The new Istio Helm packages are BETA in Big Bang 2.x and will be stable in 3.0*
 
 ### Step 1 : Remove Istio from your deployment
 Before upgrading to version 3.0 of Big Bang with the new Helm-based Istio packages, we first need to disable Istio and Istio's Operator packages in our 2.x deployment of Big Bang. We do this by disabling the two obsolete [Istio packages in our Gitops configuration](https://repo1.dso.mil/kipten/template/-/blob/main/package-strategy/configmap.yaml?ref_type=heads#L18-22).
-- 
GitLab