From 93e02bf88dec81de2249581d5e982edb6d5d84f6 Mon Sep 17 00:00:00 2001
From: April M <36110273+aimurphy@users.noreply.github.com>
Date: Fri, 24 Oct 2025 05:56:07 -0700
Subject: [PATCH] subscription plan updates

---
 modules/ROOT/pages/create-target.adoc            |  2 +-
 .../ROOT/pages/troubleshooting-scenarios.adoc    | 16 +---------------
 2 files changed, 2 insertions(+), 16 deletions(-)

diff --git a/modules/ROOT/pages/create-target.adoc b/modules/ROOT/pages/create-target.adoc
index 2baf9e7a..c04e57af 100644
--- a/modules/ROOT/pages/create-target.adoc
+++ b/modules/ROOT/pages/create-target.adoc
@@ -18,7 +18,7 @@ To migrate data to an {astra-db} database, do the following:
 . Sign in to your {astra-url}[{astra} account^].
 +
 You can use any subscription plan tier.
-However, the Pay As You Go and Enterprise plans offer premium features that can facilitate your migration, including support for {sstable-sideloader}, more databases, and no automatic database hibernation.
+However, paid subscription plans offer premium features that can facilitate your migration, including support for {sstable-sideloader}, more databases, and no automatic database hibernation.
 These plans also support advanced features like customer-managed encryption keys and metrics exports.
 For more information, see xref:astra-db-serverless:administration:subscription-plans.adoc[].
 
diff --git a/modules/ROOT/pages/troubleshooting-scenarios.adoc b/modules/ROOT/pages/troubleshooting-scenarios.adoc
index fc595ddf..9595f7ad 100644
--- a/modules/ROOT/pages/troubleshooting-scenarios.adoc
+++ b/modules/ROOT/pages/troubleshooting-scenarios.adoc
@@ -84,10 +84,6 @@ These protocol version downgrades happen when either {product-proxy} or at least
 V5 downgrades are enforced by {product-proxy} but any other downgrade is requested by one of the clusters when they don't support the version that the client requested.
 The proxy supports V3, V4, DSE_V1 and DSE_V2.
 
-////
-ZDM-71 tracks a request to support v2.
-////
-
 === Solution or Workaround
 
 These log messages are informative only (log level `DEBUG`).
@@ -98,9 +94,7 @@ This log message with a log level of `ERROR` means that the protocol error occur
 
 == Error during proxy startup: `Invalid or unsupported protocol version: 3`
 
-=== Symptoms
-
-{product-proxy} logs contain:
+If the {product-proxy} logs contain the following type of output, it indicates that one of the origin clusters doesn't support at least V3 (e.g. {cass-short} 2.0, {dse-short} 4.6), and {product-short} cannot be used for that migration.
 
 [source,log]
 ----
@@ -130,15 +124,7 @@ time="2022-10-01T19:58:15+01:00" level=info msg="Proxy shutdown complete."
 time="2022-10-01T19:58:15+01:00" level=error msg="Couldn't start proxy, retrying in 2.229151525s: failed to initialize origin control connection: could not open control connection to ORIGIN, tried endpoints: [127.0.0.1:9042]."
 ----
 
-=== Cause
-
 The control connections of {product-proxy} don't perform protocol version negotiation, they only attempt to use protocol version 3.
-If one of the origin clusters doesn't support at least V3 (e.g. {cass-short} 2.0, {dse-short} 4.6), then {product-short} cannot be used for that migration at the moment.
-We plan to introduce support for {cass-short} 2.0 and {dse-short} 4.6 very soon.
-
-=== Solution or Workaround
-
-None.
 
 == Authentication errors