Merge branch 'main' into DOC-9362

src/current/_data/releases.yml

@@ -6888,41 +6888,6 @@
     docker_arm_limited_access: false
   source: true
   previous_release: v23.1.27
-  cloud_only: true
-  cloud_only_message_short: 'Available only for select CockroachDB Cloud clusters'
-  cloud_only_message: >
-    This version is currently available only for select
-    CockroachDB Cloud clusters. To request to upgrade
-    a CockroachDB self-hosted cluster to this version,
-    [contact support](https://support.cockroachlabs.com/hc/requests/new).
-
-- release_name: v24.3.0-alpha.2
-  major_version: v24.3
-  release_date: '2024-10-14'
-  release_type: Testing
-  go_version: go1.22.5
-  sha: 58c475d67e32b75284b4fe293bff82807c3d129d
-  has_sql_only: true
-  has_sha256sum: true
-  mac:
-    mac_arm: true
-    mac_arm_experimental: true
-    mac_arm_limited_access: false
-  windows: true
-  linux:
-    linux_arm: true
-    linux_arm_experimental: false
-    linux_arm_limited_access: false
-    linux_intel_fips: true
-    linux_arm_fips: false
-  docker:
-    docker_image: cockroachdb/cockroach-unstable
-    docker_arm: true
-    docker_arm_experimental: false
-    docker_arm_limited_access: false
-  source: true
-  previous_release: v24.3.0-alpha.1
-
 
 - release_name: v24.3.0-alpha.2
   major_version: v24.3
@@ -6949,4 +6914,4 @@
     docker_arm_experimental: false
     docker_arm_limited_access: false
   source: true
-  previous_release: v24.3.0-alpha.1-218-g58c475d67e3
+  previous_release: v24.3.0-alpha.1

src/current/_includes/releases/v24.3/v24.3.0-alpha.2.md

@@ -38,7 +38,7 @@ Release Date: October 14, 2024
 
     [#131857][#131857]
 
-- The following ({% link v24.3/metrics.md %}) have been renamed:
+- The following [metrics]({% link v24.3/metrics.md %}) have been renamed:
 
       Previous name                                    | New name-
       -------------------------------------------------|-----------

src/current/advisories/a131639.md

@@ -91,6 +91,7 @@ BEGIN AS OF SYSTEM TIME '-10s';
 SELECT count(*) FROM my_table@my_table_pkey WHERE pk = 1;
 SELECT count(*) FROM my_table@my_table_a_idx WHERE pk = 1 AND a=2;
 SELECT count(*) FROM my_table@my_table_b_idx WHERE pk = 1 AND b=3;
+COMMIT;
 ~~~
 
 If any of these queries return different values for `count`, that likely indicates a lost write.

src/current/cockroachcloud/aws-privatelink.md

@@ -163,17 +163,15 @@ Complete these steps once for each private endpoint in your AWS account that wil
 
 1. Copy the **Service Name** shown in the connection dialog.
 
-   Make a note of the availability zones where your cluster is deployed in this region.
+    Make a note of the availability zones where your cluster is deployed in this region.
 
 1. On the [Amazon VPC Console](https://console.aws.amazon.com/vpc/) in your AWS account, click **Your VPCs** in the sidebar.
 
-1. <a name="step-4"></a>Locate the VPC ID of the VPC you want to create your endpoint in.
+    Locate the VPC ID of the VPC you want to create your endpoint in, and make a note of its IPv4 CIDR.
 
     Cockroach Labs recommends that you use a VPC that has subnets in the availability zones where your cluster is deployed, and that your application or service is also deployed in the same availability zones. You can choose a different VPC for the private endpoint as long as it is peered to the VPC your application is running in and the private endpoint is configured to be DNS-accessible across the peered VPCs.
 
-1. On the **Your VPCs** page, locate the IPv4 CIDR corresponding to the VPC you chose in [step 4](#step-4).
-1. Click **Subnets** in the sidebar.
-1. Locate the subnet IDs corresponding to the VPC you chose in [step 4](#step-4).
+1. Click **Subnets** in the sidebar. Make a note of the subnet ID of each subnet that corresponds to your chosen VPC.
 1. Click **Security Groups** in the sidebar.
 1. <a name="step-8"></a>Click **Create security group** to create a security group within your VPC. The security group allows inbound access from your application or source program on Port 26257: {{ security_group_substeps }}
 
@@ -189,11 +187,11 @@ Use either the Amazon VPC Console or the [AWS Command Line Interface (CLI)](http
 1. Click **Endpoints** in the sidebar.
 1. Click **Create Endpoint**.
 1. On the **Create Endpoint** page, for the **Service Category** field, select **Find service by name**.
-1. In the **Service Name** field, enter the **Service Name** copied from the connection dialog in [Step 1](#step-1).
+1. In the **Service Name** field, enter the **Service Name** you copied from the connection dialog in [Step 3. Create an AWS endpoint](#step-3-create-an-aws-endpoint).
 1. Click **Verify**.
 1. In the **VPC** field, enter the ID of the VPC you want to create your endpoint in.
 1. Verify that the subnets are pre-populated.
-1. In the **Security group** section, select the security group you created in [Step 8](#step-8) and uncheck the box for **default** security group.
+1. In the **Security group** section, select the security group you created in [Step 3. Create an AWS endpoint](#step-3-create-an-aws-endpoint) and uncheck the box for **default** security group.
 1. Click **Create Endpoint**.
 
     The VPC Endpoint ID displays.