risingwavelabs · xxchan · Nov 20, 2024 · Nov 20, 2024
diff --git a/cloud/check-status-and-metrics.mdx b/cloud/check-status-and-metrics.mdx
@@ -28,8 +28,5 @@ The project details page includes:
 * [Database users](/cloud/manage-database-users/)
 
 <Tip>
-**TIP**
-
 To specify the time range of the metrics, go to the **Metrics** tab, and click on **Last 30 minutes** in the top right corner to customize your time range.
-
 </Tip>
diff --git a/cloud/create-a-connection.mdx b/cloud/create-a-connection.mdx
@@ -51,8 +51,6 @@ You can find it in the [Azure Portal](https://portal.azure.com/) → **Private l
 5. Click **Confirm** to create the connection.
 
 <Tip>
-**TIP**
-
 For inquiries about PrivateLink for Confluent private Kafka clusters, please reach out to our [support team](mailto:cloud-support@risingwave-labs.com) first. We will handle these manual steps:
 
 * Before provisioning a RisingWave PrivateLink, ensure the cluster's Availability Zones (AZs) are a subset of the AZs offered by RisingWave.

diff --git a/cloud/export-metrics.mdx b/cloud/export-metrics.mdx
@@ -4,8 +4,6 @@ description: "This article describes how to use metrics API to export metrics fr
 ---
 
 <Tip>
-**TIP**
-
 By default, a newly created service account isn't given any permissions. To export metrics, you need to grant your service account the `ProjectAdmin` role. See [RBAC](/cloud/organization-rbac/#role-permissions-and-limitations) for more details.
 </Tip>
 

diff --git a/cloud/manage-sources.mdx b/cloud/manage-sources.mdx
@@ -34,7 +34,6 @@ Click on a source to view its details, including the connector settings, schema,
 <Tip>
 
 When checking throughput and errors, you can click **Last 30 minutes** on the right side to customize your time range.
-
 </Tip>
 
 ## Drop a source

diff --git a/cloud/project-byoc.mdx b/cloud/project-byoc.mdx
@@ -19,8 +19,6 @@ Follow the steps below to create your own cloud environment.
 3. Once you've redeemed the invitation code, select **BYOC** as the deployment type, and select your cloud platform as AWS or GCP (see [Resource and permission](#resource-and-permission) for more details), region, and ID as necessary.
 4. After configuring these settings, you'll see additional instructions on your screen. Follow these steps to establish your BYOC environment. Please be aware that the final command `rwc byoc apply --name xxx` may take 30 to 40 minutes to complete, and a progress bar will be shown to keep you updated. During this time, it's crucial to ensure a stable internet connection. If the command is interrupted or fails due to network instability, you can safely retry it.
 <Tip>
-**TIP**
-
 When you run the command `rwc byoc apply --name xxx`, it will deploy some resources in your AWS/GCP/Azure environment, such as AWS S3/Google Cloud Storage/Azure Blob Storage and EKS/GKE/AKS clusters. Please do not modify the configuration of these resources. If you encounter any issues during this process, please contact our [support team](mailto:cloud-support@risingwave-labs.com).
 </Tip>
 5. Click **Next** to continue the configuration of cluster size and nodes. To learn more about the nodes, see the [architecture of RisingWave](/docs/current/architecture/).

diff --git a/demos/real-time-ad-performance-analysis.mdx b/demos/real-time-ad-performance-analysis.mdx
@@ -105,8 +105,6 @@ CREATE SOURCE ad_click (
 ```
 
 <Tip>
-**TIP**
-
 `scan.startup.mode = 'earliest'` means the source will start streaming from the earliest entry in Kafka. Internally, RisingWave will record the consumed offset in the persistent state so that during a failure recovery, it will resume from the last consumed offset.
 </Tip>
 
@@ -209,8 +207,6 @@ FROM
 ```
 
 <Tip>
-**TIP**
-
 You can easily build a CTR live dashboard on top of `ad_ctr_5min`. The CTR value is dynamically changing and every ad CTR in a given window can be drawn as a plot in the line chart. Eventually, we are able to analyze how CTR changes over time.
 </Tip>
 

diff --git a/integrations/sources/kafka.mdx b/integrations/sources/kafka.mdx
@@ -14,7 +14,6 @@ RisingWave supports exactly-once semantics by reading transactional messages onl
 **GUIDED SETUP**
 
 [RisingWave Cloud](https://cloud.risingwave.com/auth/signup/) provides an intuitive guided setup for creating a Kafka source. For more information, see [Create a source using guided setup](/cloud/manage-sources/#using-guided-setup) in the RisingWave Cloud documentation.
-
 </Tip>
 
 ## Syntax

diff --git a/integrations/sources/mysql-cdc.mdx b/integrations/sources/mysql-cdc.mdx
@@ -363,7 +363,6 @@ CREATE TABLE {{ this }}  (
 **PREMIUM EDITION FEATURE**
 
 This feature is only available in the premium edition of RisingWave. The premium edition offers additional advanced features and capabilities beyond the free and community editions. If you have any questions about upgrading to the premium edition, please contact our sales team at [sales@risingwave-labs.com](mailto:sales@risingwave-labs.com).
-
 </Tip>
 <Note>
 PUBLIC PREVIEW
@@ -404,7 +403,6 @@ And this it the output of `DESCRIBE supplier;`
 **PREMIUM EDITION FEATURE**
 
 This feature is only available in the premium edition of RisingWave. The premium edition offers additional advanced features and capabilities beyond the free and community editions. If you have any questions about upgrading to the premium edition, please contact our sales team at [sales@risingwave-labs.com](mailto:sales@risingwave-labs.com).
-
 </Tip>
 <Note>
 **PUBLIC PREVIEW**

diff --git a/integrations/sources/postgresql-cdc.mdx b/integrations/sources/postgresql-cdc.mdx
@@ -378,7 +378,6 @@ CREATE TABLE {{ this }} (
 **PREMIUM EDITION FEATURE**
 
 This feature is only available in the premium edition of RisingWave. The premium edition offers additional advanced features and capabilities beyond the free and community editions. If you have any questions about upgrading to the premium edition, please contact our sales team at [sales@risingwave-labs.com](mailto:sales@risingwave-labs.com).
-
 </Tip>
 <Note>
 **PUBLIC PREVIEW**

diff --git a/processing/indexes.mdx b/processing/indexes.mdx
@@ -90,8 +90,6 @@ SELECT c_name, c_address FROM customers WHERE c_phone = '123456789';
 ```
 
 <Tip>
-**TIP**
-
 You can use the [EXPLAIN](/docs/current/sql-explain/) command to view the execution plan.
 </Tip>
 

diff --git a/sql/commands/sql-create-mv.mdx b/sql/commands/sql-create-mv.mdx
@@ -10,12 +10,9 @@ CREATE MATERIALIZED VIEW [IF NOT EXISTS] mv_name AS select_query;
 ```
 
 <Tip>
-**TIP**
-
 `CREATE MATERIALIZED VIEW` will first **backfill** historical data from the referenced relations, and completion time varies based on the volume of data to be backfilled.
 
 To perform the operations in the background, you can execute `SET BACKGROUND_DDL=true;` before running the `CREATE MATERIALIZED VIEW` statement. See details in [SET BACKGROUND\_DDL](/docs/current/sql-set-background-ddl/).
-
 </Tip>
 ## Parameters
 

diff --git a/sql/commands/sql-create-user.mdx b/sql/commands/sql-create-user.mdx
@@ -53,8 +53,6 @@ CREATE USER user1
 ```
 
 <Tip>
-**TIP**
-
 You can connect to RisingWave with the newly created user account.
 </Tip>
 

diff --git a/sql/commands/sql-describe.mdx b/sql/commands/sql-describe.mdx
@@ -6,8 +6,6 @@ description: "Use the `DESCRIBE` command to view columns in the specified table,
 `DESCRIBE` is a shortcut for [SHOW COLUMNS](/docs/current/sql-show-columns/).
 
 <Tip>
-**TIP**
-
 `DESCRIBE` also lists the indexes on a table or materialized view, whereas `SHOW COLUMNS` doesn't.
 </Tip>
 

diff --git a/sql/commands/sql-drop-function.mdx b/sql/commands/sql-drop-function.mdx
@@ -31,8 +31,6 @@ DROP FUNCTION function_name;
 You can run [SHOW FUNCTIONS;](/docs/current/sql-show-functions/) to list all existing UDFs to see if a function name is unique.
 
 <Tip>
-**TIP**
-
 `DROP FUNCTION function_name();` drops a function with zero arguments.
 
 `DROP FUNCTION function_name;` drops a function with any number of arguments, including zero, as long as the name is unique.
-Original file line number
+Diff line change
@@ Expand Up / @@ -28,8 +28,5 @@ The project details page includes: @@
     * [Database users](/cloud/manage-database-users/)
     <Tip>
-    **TIP**
     To specify the time range of the metrics, go to the **Metrics** tab, and click on **Last 30 minutes** in the top right corner to customize your time range.
     </Tip>