Fix broken step numbering (#23161)

jhlodin · web-flow · commit 2653112812c9 · 2026-04-06T21:24:12.000Z
diff --git a/src/current/cockroachcloud/create-an-advanced-cluster.md b/src/current/cockroachcloud/create-an-advanced-cluster.md
@@ -118,15 +118,11 @@ Advanced security features cannot be enabled or disabled after cluster creation.
       Remember to [delete your trial cluster]({% link cockroachcloud/cluster-management.md %}#delete-cluster) before the trial expires. Otherwise, your credit card will be charged after the trial ends. You can check the validity of the code on the [Billing]({% link cockroachcloud/billing-management.md %}) page.
       {{site.data.alerts.end}}
 
-<a id="step-7-name-the-cluster"></a>
-
 ## Step 8. Name the cluster
 
 The cluster is automatically given a randomly-generated name. If desired, change the cluster's name. The cluster name must be 6-20 characters in length, and can include lowercase letters, numbers, and dashes (but no leading or trailing dashes). A cluster's name cannot be edited after the cluster is created.
 
-<a id="step-8-select-the-cockroachdb-version"></a>
-
-## Step 8. Select the CockroachDB version
+## Step 9. Select the CockroachDB version
 
 When you create a new cluster, it uses the [latest CockroachDB {{ site.data.products.cloud }} production release](https://www.cockroachlabs.com/docs/releases/cloud) by default. All clusters are then upgraded automatically to each subsequent patch release of their major version as it becomes available. To learn more, refer to [Upgrade Policy]({% link cockroachcloud/upgrade-policy.md %}).
 
@@ -135,7 +131,7 @@ To select the cluster version:
 1. Under **Cluster version**, click the version selector.
 1. Select a CockroachDB version.
 
-## Step 9. Finish creating the cluster
+## Step 10. Finish creating the cluster
 
 Click **Create cluster**. Your cluster will be created in approximately 20-30 minutes.
 
diff --git a/src/current/cockroachcloud/create-your-cluster.md b/src/current/cockroachcloud/create-your-cluster.md
@@ -93,30 +93,12 @@ Click **Next: Finalize**.
       Make sure that you [delete your trial cluster]({% link cockroachcloud/cluster-management.md %}#delete-cluster) before the trial expires. Your credit card will be charged after the trial ends. You can check the validity of the code on the [Billing]({% link cockroachcloud/billing-management.md %}) page.
       {{site.data.alerts.end}}
 
-<a id="step-7-name-the-cluster"></a>
-
 ## Step 6. Name the cluster
 
 The cluster is automatically given a randomly-generated name. If desired, change the cluster's name. The cluster name must be 6-20 characters in length, and can include lowercase letters, numbers, and dashes (but no leading or trailing dashes). A cluster's name cannot be edited after it is created.
 
 Click **Create cluster**. Your cluster will be created in a few seconds.
 
-{% comment %}## Step 8. Select the CockroachDB version
-
-When you create a new CockroachDB {{ site.data.products.standard }} cluster, it defaults to using the [latest CockroachDB {{ site.data.products.cloud }} production release]({% link releases/cloud.md %}) unless you select a release explicitly. Releases are rolled out gradually to CockroachDB {{ site.data.products.cloud }}. At any given time, you may be able to choose among multiple releases. In the list:
-
-- **No label**: The latest patch of a Regular [Production release]({% link cockroachcloud/upgrade-policy.md %}) that is not the latest. A Regular release has full support for one year from the release date, at which a cluster must be [upgraded]({% link cockroachcloud/upgrade-policy.md %}) to maintain support.
-- **Latest**: The latest patch of the latest regular [Production release]({% link cockroachcloud/upgrade-policy.md %}). This is the default version for new clusters.
-- **Innovation Release**: The latest patch of an [Innovation release]({% link cockroachcloud/upgrade-policy.md %}). Innovation releases are optional releases that provide earlier access to new features, and are released between regular releases. An Innovation release has full support for six months from the release date, at which time a cluster must be [upgraded]({% link cockroachcloud/upgrade-policy.md %}) to the next Regular release to maintain support.
-- **Pre-Production Preview**: A [Pre-Production Preview]({% link cockroachcloud/upgrade-policy.md %}#pre-production-preview-upgrades). Leading up to a new CockroachDB Regular [Production release]({% link cockroachcloud/upgrade-policy.md %}), a series of Beta and Release Candidate (RC) patches may be made available for CockroachDB {{ site.data.products.standard }} as Pre-Production Preview releases. Pre-Production Preview releases are not suitable for production environments. They are no longer available in CockroachDB {{ site.data.products.cloud }} for new clusters or upgrades after the new version is GA. When the GA release is available, a cluster running a Pre-Production Preview is automatically upgraded to the GA release and subsequent patches and is eligible for support.
-
-1. To choose a version for your cluster, select the cluster version from the **Cluster version** list.
-
-After the cluster is created, patch releases within its major version are required and are applied automatically. If you install or upgrade to a Pre-Production Preview release, subsequent Pre-Production Preview patch releases, the GA release, and subsequent patches within the major version are applied automatically. To learn more, refer to the [CockroachDB Cloud Support and Upgrade Policy]({% link cockroachcloud/upgrade-policy.md %}).
-
-## Step 9{% endcomment %}
-
-<a id="step-9-finish-creating-the-cluster"></a>
 ## Step 7. Finish creating the cluster
 
 Click **Create cluster**. Your cluster will be created in approximately 20-30 minutes.
diff --git a/src/current/releases/cloud.md b/src/current/releases/cloud.md
@@ -179,7 +179,7 @@ In addition, this release includes the following features:
 
 <h3 id="2024-07-24-general-updates"> General updates </h3>
 
-- When creating a new CockroachDB {{ site.data.products.advanced }} cluster, you can now [select the cluster's major version]({% link cockroachcloud/create-an-advanced-cluster.md %}#step-8-select-the-cockroachdb-version). The default option is the latest stable version. At any given time, you may be able to choose from additional stable releases or experimental [Pre-Production Preview]({% link cockroachcloud/upgrade-policy.md %}#pre-production-preview-upgrades) releases. Patch releases within a major version are applied automatically.
+- When creating a new CockroachDB {{ site.data.products.advanced }} cluster, you can now [select the cluster's major version]({% link cockroachcloud/create-an-advanced-cluster.md %}#step-9-select-the-cockroachdb-version). The default option is the latest stable version. At any given time, you may be able to choose from additional stable releases or experimental [Pre-Production Preview]({% link cockroachcloud/upgrade-policy.md %}#pre-production-preview-upgrades) releases. Patch releases within a major version are applied automatically.
 
 ## July 19, 2024
 
diff --git a/src/current/v26.2/build-a-spring-app-with-cockroachdb-mybatis.md b/src/current/v26.2/build-a-spring-app-with-cockroachdb-mybatis.md
@@ -161,7 +161,7 @@ Exit the SQL shell:
 > \q
 ~~~
 
-## Step 6. Run the application
+## Step 5. Run the application
 
 To run the application:
 
diff --git a/src/current/v26.2/performance-benchmarking-with-tpcc-large.md b/src/current/v26.2/performance-benchmarking-with-tpcc-large.md
@@ -199,7 +199,7 @@ CockroachDB comes with a number of [built-in workloads]({% link {{ page.version.
 
     <img src="{{ 'images/v26.2/tpcc-large-replication-dashboard.png' | relative_url }}" alt="TPC-C 140k replication and partitioning dashboards" style="border:1px solid #eee;max-width:100%" />
 
-## Step 7. Allocate partitions
+## Step 6. Allocate partitions
 
 Before running the benchmark, it's important to allocate partitions to workload binaries properly to ensure that the cluster is balanced.
 
@@ -297,7 +297,7 @@ Before running the benchmark, it's important to allocate partitions to workload
     $(cat addrs)
     ~~~
 
-## Step 8. Run the benchmark
+## Step 7. Run the benchmark
 
 Once the allocations finish, run TPC-C for 30 minutes on each VM with `workload`:
 
@@ -365,7 +365,7 @@ ulimit -n 500000 && cockroach workload run tpcc \
 $(cat addrs)
 ~~~
 
-## Step 9. Interpret the results
+## Step 8. Interpret the results
 
 1. Collect the result files from each VM with `workload`:
 
diff --git a/src/current/v26.2/start-a-local-cluster-in-docker-windows.md b/src/current/v26.2/start-a-local-cluster-in-docker-windows.md
@@ -335,7 +335,7 @@ The CockroachDB [DB Console]({% link {{ page.version.version }}/ui-overview.md %
 
 1. Use the [**Databases**]({% link {{ page.version.version }}/ui-databases-page.md %}), [**Statements**]({% link {{ page.version.version }}/ui-statements-page.md %}), and [**Jobs**]({% link {{ page.version.version }}/ui-jobs-page.md %}) pages to view details about your databases and tables, to assess the performance of specific queries, and to monitor the status of long-running operations like schema changes, respectively.
 
-## Step 6.  Stop the cluster
+## Step 7. Stop the cluster
 
 1. Use the `docker stop` and `docker rm` commands to stop and remove the containers (and therefore the cluster). By default, `docker stop` sends a `SIGTERM` signal, waits for 10 seconds, and then sends a `SIGKILL` signal. Cockroach Labs recommends that you [allow between 5 and 10 minutes]({% link {{ page.version.version }}/node-shutdown.md %}#termination-grace-period) before forcibly stopping the `cockroach` process, so this example sets the grace period to 5 minutes. If you do not plan to restart the cluster, you can omit `-t`.
 
