update streaming tenant creation steps

modules/functions/pages/index.adoc

@@ -3,8 +3,8 @@
 
 A {pulsar-short} *transform function* is a low-code implementation of xref:astra-streaming:developing:astream-functions.adoc[{pulsar-short} functions]. +
 Functions receive data from one or more input topics, apply user-supplied processing, and publish the results to another topic. +
-Custom functions are a powerful feature, but for common data transformations, we now include *Transform Functions*. +
-<<Drop-fields>>, <<Flatten>>, <<Compute>>, and more without coding or deep schema knowledge. +
+Custom functions are a powerful feature, but for common data transformations, we now include *Transform Functions*.
+Drop fields, flatten, compute, and more without coding or deep schema knowledge.
 {company} has created the following transform functions for common data transforms, but we're always experimenting with new ones.
 Check back as the list grows, or let us know some functions you'd find helpful in your deployment.
 

modules/pulsar-io/pages/connectors/index.adoc

@@ -260,7 +260,7 @@ curl::
 You need a {pulsar-short} token for REST API authentication.
 This is different from your {astra-db} application tokens.
 
-. In the {astra-ui-link} header, click icon:grip[name="Applications"], and then select *Streaming*.
+. In the {astra-ui-link}, click *Streaming tenants*.
 
 . Click your tenant's name, and then click the *Settings* tab.
 
@@ -310,7 +310,7 @@ curl::
 You need a {pulsar-short} token for REST API authentication.
 This is different from your {astra-db} application tokens.
 
-. In the {astra-ui-link} header, click icon:grip[name="Applications"], and then select *Streaming*.
+. In the {astra-ui-link}, click *Streaming tenants*.
 
 . Click your tenant's name, and then click the *Settings* tab.
 

modules/pulsar-io/partials/connectors/sinks/curl-tab-prereq.adoc

@@ -1,7 +1,7 @@
 You need a {pulsar-short} token for REST API authentication.
 This is different from your {astra-db} application tokens.
 
-. In the {astra-ui-link} header, click icon:grip[name="Applications"], and then select *Streaming*.
+. In the {astra-ui-link}, click *Streaming tenants*.
 
 . Click your tenant's name, and then click the *Settings* tab.
 

modules/pulsar-io/partials/connectors/sources/curl-tab-prereq.adoc

@@ -1,7 +1,7 @@
 You need a {pulsar-short} token for REST API authentication.
 This is different from your {astra-db} application tokens.
 
-. In the {astra-ui-link} header, click icon:grip[name="Applications"], and then select *Streaming*.
+. In the {astra-ui-link}, click *Streaming tenants*.
 
 . Click your tenant's name, and then click the *Settings* tab.
 

modules/pulsar-io/partials/connectors/sources/monitoring.adoc

@@ -23,7 +23,7 @@ curl::
 You need a {pulsar-short} token for REST API authentication.
 This is different from your {astra-db} application tokens.
 
-. In the {astra-ui-link} header, click icon:grip[name="Applications"], and then select *Streaming*.
+. In the {astra-ui-link}, click *Streaming tenants*.
 
 . Click your tenant's name, and then click the *Settings* tab.
 
@@ -85,7 +85,7 @@ curl::
 You need a {pulsar-short} token for REST API authentication.
 This is different from your {astra-db} application tokens.
 
-. In the {astra-ui-link} header, click icon:grip[name="Applications"], and then select *Streaming*.
+. In the {astra-ui-link}, click *Streaming tenants*.
 
 . Click your tenant's name, and then click the *Settings* tab.
 

modules/use-cases-architectures/pages/real-time-data-pipeline/01-create-astra-objects.adoc

@@ -8,7 +8,7 @@ This guide is part of a series that creates a real-time data pipeline with {prod
 
 == Creating message topics to capture the stream of click data
 
-. In the {astra-ui-link} header, click icon:grip[name="Applications"], select *Streaming*, and then click **Create Tenant**.
+. In the {astra-ui-link}, click *Create tenant*.
 
 . Name the new streaming tenant `webstore-clicks`, select any cloud provider and region, and then click **Create Tenant**.
 
@@ -27,7 +27,7 @@ You now have a `production` namespace with two topics, as well as the `default`
 
 == Storing the stream of click data
 
-. In the {astra-ui-link} header, click icon:grip[name="Applications"], and then select *{product-short}*.
+. From your tenant's page, click **Dashboard**, and then click **Serverless databases**.
 
 . Click **Create database**, and then complete the fields as follows:
 +
@@ -139,7 +139,8 @@ CREATE TABLE click_data.product_clicks (
 
 == Connecting the topics to the store
 
-. In the {astra-ui-link} header, click icon:grip[name="Applications"], and then select *Streaming*.
+. To return to the *Streaming tenants* dashboard from the CQL console, click your user name, and then select the org your `webstore-clicks` streaming tenant was created in.
+. In the {astra-ui-link}, click *Streaming tenants*.
 
 . Click your `webstore-clicks` streaming tenant.
 

modules/use-cases-architectures/pages/real-time-data-pipeline/02-create-decodable-objects.adoc

@@ -10,7 +10,7 @@ This guide is part of a series that creates a real-time data pipeline with {prod
 
 To connect {product} to Decodable, you need some information from your {product} tenant.
 
-. In the {astra-ui-link} header, click icon:grip[name="Applications"], select **Streaming**, and then click your `webstore-clicks` streaming tenant.
+. In the {astra-ui-link}, click *Streaming tenants*, and then click your `webstore-clicks` streaming tenant.
 +
 image:decodable-data-pipeline/02/image4.png[]
 

modules/use-cases-architectures/pages/real-time-data-pipeline/03-put-it-all-together.adoc

@@ -74,21 +74,20 @@ In “Input Metrics”, we see that 1 record has been received.
 +
 image:decodable-data-pipeline/03/image4.png[]
 
-. Return to your {product} tenant “webstore-clicks” and navigate to the “Namespace and Topics” area.
+. Return to your “webstore-clicks” tenant and navigate to the “Namespace and Topics” area.
 Expand the “production” namespace and select the “all-clicks” topic.
 Confirm that “Data In” has 1 message and “Data Out” has 1 message. This means the topic took the data in and a consumer acknowledged receipt of the message.
 +
 image:decodable-data-pipeline/03/image6.png[]
 
-. In the “Sinks” tab in {product}, select the “all-clicks” sink. In “Instance Stats” you see “Reads” has a value of 1 and “Writes” has a value of 1. This means the sink consumed a message from the topic and wrote the data to the store.
+. In the “Sinks” tab, select the “all-clicks” sink. In “Instance Stats” you see “Reads” has a value of 1 and “Writes” has a value of 1. This means the sink consumed a message from the topic and wrote the data to the store.
 +
 image:decodable-data-pipeline/03/image5.png[]
 
 . Inspect the data in your {astra-db} database.
 +
 In the {astra-ui}, go to your `webstore-clicks` database, click **CQL Console**, and then run the following CQL statement:
 +
---
 [source,sql,subs="attributes+"]
 ----
 select * from click_data.all_clicks;
@@ -128,13 +127,12 @@ Similar to how you followed the above flow of raw click data, follow this flow t
 
 . Go to your `Astra-Streaming-Product-Webclicks-Connection` connection, and then check that the **Input Metrics** have 1 record.
 
-. In {product}, go to your tenant, and then go to the `product-clicks` topic in the `production` namespace.
+Go to your `webstore-clicks` tenant, and then go to the `product-clicks` topic in the `production` namespace.
 
 . Make sure **Data In** and **Data Out** have 1 message each.
 
 . In the {astra-ui}, go to your `webstore-clicks` database, click **CQL Console**, and then query the `product_clicks` table to inspect the data in the database:
 +
---
 [source,sql,subs="attributes+"]
 ----
 select * from click_data.product_clicks;

modules/use-cases-architectures/pages/real-time-data-pipeline/04-debugging-and-clean-up.adoc

@@ -42,13 +42,13 @@ image:decodable-data-pipeline/04/image2.png["Delete decodable connection"]
 
 === Removing {product-short} objects
 
-. In the {astra-ui-link} header, click icon:grip[name="Applications"], and then select **Streaming**.
+. In the {astra-ui-link}, click *Streaming tenants*.
 
 . Find the `webstore-clicks` tenant, click icon:ellipsis-vertical[name="More"], and then select **Delete**.
 +
 This removes the tenant and all associated sinks, topics, messages, and namespaces.
 
-. In the {astra-ui-link} header, click icon:grip[name="Applications"], and then select **{product-short}**.
+. Click **Serverless databases** to switch to the Serverless databases dashboard.
 
 . Find the `webstore-clicks` database, click icon:ellipsis-vertical[name="More"], and then select **Terminate**.
 +