From 4a7157c204f1e902dfc916c7b05cebff7cf59089 Mon Sep 17 00:00:00 2001
From: April M <36110273+aimurphy@users.noreply.github.com>
Date: Tue, 10 Feb 2026 08:05:40 -0800
Subject: [PATCH] Stargate for Astra EOL

---
 modules/ROOT/pages/feasibility-checklists.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/feasibility-checklists.adoc b/modules/ROOT/pages/feasibility-checklists.adoc
index d09d8cdf..2b68874f 100644
--- a/modules/ROOT/pages/feasibility-checklists.adoc
+++ b/modules/ROOT/pages/feasibility-checklists.adoc
@@ -325,7 +325,7 @@ However, the xref:astra-db-serverless:databases:database-limits.adoc#cassandra-c
 You must adapt your client application to use a consistency level that is supported by both clusters to ensure that the migration is seamless and error-free.
 
 {astra} doesn't support the Stargate APIs::
-The Stargate APIs (Document, REST, GraphQL, gRPC) are deprecated for {astra}.
+The Stargate APIs (Document, REST, GraphQL, gRPC) don't support {astra}.
 If you are migrating to {astra} from an origin cluster that uses any of these APIs, your client applications won't work with {astra}.
 Before you migrate, you must change your applications to use other programmatic access, such as {cass-short} drivers or the {data-api}.
 For more information, see xref:astra-db-serverless:api-reference:compare-dataapi-to-stargate.adoc[].