Minor fixes (#28518)

ddhodge · web-flow · commit bdadd6bc0f31 · 2025-09-07T23:44:37.000-04:00
diff --git a/docs/content/preview/develop/learn/transactions/acid-transactions-ycql.md b/docs/content/preview/develop/learn/transactions/acid-transactions-ycql.md
@@ -15,7 +15,7 @@ type: docs
 
 {{<api-tabs>}}
 
-A transaction is a sequence of operations performed as a single logical unit of work. YugabyteDB provides [ACID](../../../../architecture/key-concepts#acid) guarantees for all transactions:
+A transaction is a sequence of operations performed as a single logical unit of work. YugabyteDB provides [ACID](../../../../architecture/key-concepts#acid) guarantees for all transactions.
 
 {{<note title="Note">}}
 Although YugabyteDB supports only *Snapshot* isolation level in the YCQL API, it supports three levels of isolation in the [YSQL](../../../../explore/transactions/isolation-levels/) API: *Snapshot*, *Serializable*, and *Read Committed*.
diff --git a/docs/content/preview/develop/learn/transactions/transactions-global-apps.md b/docs/content/preview/develop/learn/transactions/transactions-global-apps.md
@@ -19,7 +19,7 @@ In a multi-region setup, a transaction would have to reach out to the tablet lea
 
 Cross-region trips can be avoided by placing all the tablet leaders in one region using the [set_preferred_zones](../../../../admin/yb-admin/#set-preferred-zones) command in [yb-admin](../../../../admin/yb-admin/).
 
-You can also do this by [marking the zones as Preferred](../../../../yugabyte-platform/manage-deployments/edit-universe/) on the **Edit Universe** page in [YugabyteDB Anywhere](../../../../yugabyte-platform/), or [setting the region as preferred](../../../../yugabyte-cloud/cloud-basics/create-clusters/create-clusters-multisync/#preferred-region) in YugabyteDB Aeon.
+You can also do this by [marking the zones as Preferred](../../../../yugabyte-platform/manage-deployments/edit-universe/) on the **Edit Universe** page in [YugabyteDB Anywhere](../../../../yugabyte-platform/), or [setting the region as preferred](/preview/yugabyte-cloud/cloud-basics/create-clusters/create-clusters-multisync/#preferred-region) in YugabyteDB Aeon.
 
 ## Read from followers
 
diff --git a/docs/content/preview/drivers-orms/c/ysql.md b/docs/content/preview/drivers-orms/c/ysql.md
@@ -34,7 +34,7 @@ type: docs
 
 [libpq](https://www.postgresql.org/docs/15/libpq.html) is the C client library for connecting to and interacting with PostgreSQL databases. libpq is also the underlying engine used in other PostgreSQL application interfaces. The libpq client library supports the [SCRAM-SHA-256 authentication method](../../../secure/authentication/password-authentication/#scram-sha-256).
 
-For details and documentation, refer to [libpq - C Library](https://www.postgresql.org/docs/15/libpq.html) for PostgreSQL 11 (on which YugabyteDB is based).
+For details and documentation, refer to [libpq - C Library](https://www.postgresql.org/docs/15/libpq.html) for PostgreSQL 15 (on which YugabyteDB is based).
 
 ## Prerequisites
 
diff --git a/docs/content/preview/drivers-orms/csharp/postgres-npgsql.md b/docs/content/preview/drivers-orms/csharp/postgres-npgsql.md
@@ -111,7 +111,7 @@ var connStringBuilder = new NpgsqlConnectionStringBuilder();
     CRUD(connStringBuilder.ConnectionString);
 ```
 
-YugabyteDB Aeon clusters require SSL. Refer to [Connect applications](../../../yugabyte-cloud/cloud-connect/connect-applications/) for instructions on how to obtain the cluster connection parameters and download the CA certificate.
+YugabyteDB Aeon clusters require SSL. Refer to [Connect applications](/preview/yugabyte-cloud/cloud-connect/connect-applications/) for instructions on how to obtain the cluster connection parameters and download the CA certificate.
 
 Refer to [Configure SSL/TLS](../postgres-npgsql-reference/#configure-ssl-tls) for more information on Npgsql default and supported SSL modes, and examples for setting up your connection strings when using SSL.
 
diff --git a/docs/content/preview/drivers-orms/nodejs/prisma.md b/docs/content/preview/drivers-orms/nodejs/prisma.md
@@ -129,7 +129,7 @@ npm install -g prisma
 
 If you have a YugabyteDB Aeon cluster, modify the `DATABASE_URL` using the following steps:
 
-1. Download your [cluster certificate](../../../yugabyte-cloud/cloud-secure-clusters/cloud-authentication).
+1. Download your [cluster certificate](/preview/yugabyte-cloud/cloud-secure-clusters/cloud-authentication).
 
 1. Install OpenSSL, if not present.
 
diff --git a/docs/content/preview/drivers-orms/smart-drivers-ycql.md b/docs/content/preview/drivers-orms/smart-drivers-ycql.md
@@ -90,11 +90,11 @@ You can configure the size of the connection pool. For example, in the Java driv
 
 ## Using YCQL drivers with YugabyteDB Aeon
 
-[YugabyteDB Aeon](../../yugabyte-cloud/) clusters automatically use load balancing provided by the cloud provider where the cluster is provisioned. The nodes are not directly accessible to the outside world. This is in contrast to the desired setup of YCQL drivers, which need direct access to all the nodes in a cluster.
+[YugabyteDB Aeon](/preview/yugabyte-cloud/) clusters automatically use load balancing provided by the cloud provider where the cluster is provisioned. The nodes are not directly accessible to the outside world. This is in contrast to the desired setup of YCQL drivers, which need direct access to all the nodes in a cluster.
 
 The drivers still work in this situation, but the client applications lose some of the benefits of the driver, including [partition-aware query routing](#partition-aware-load-balance-policy) and the default [retry policy](#retry-policy).
 
-To take advantage of the driver's partition-aware load balancing feature when connecting to clusters in YugabyteDB Aeon, the applications must be deployed in a VPC that has been peered with the cluster VPC; VPC peering enables the client application to access all nodes of the cluster. For information on VPC peering in YugabyteDB Aeon, refer to [VPC network](../../yugabyte-cloud/cloud-basics/cloud-vpcs/).
+To take advantage of the driver's partition-aware load balancing feature when connecting to clusters in YugabyteDB Aeon, the applications must be deployed in a VPC that has been peered with the cluster VPC; VPC peering enables the client application to access all nodes of the cluster. For information on VPC peering in YugabyteDB Aeon, refer to [VPC network](/preview/yugabyte-cloud/cloud-basics/cloud-vpcs/).
 
 If VPC peering is not possible, you can attempt to restore the retry capability by increasing the size of the connection pool (the Java driver default size is 1) and providing a custom retry policy to retry the failed operation on the same node.
 
diff --git a/docs/content/preview/drivers-orms/smart-drivers.md b/docs/content/preview/drivers-orms/smart-drivers.md
@@ -314,7 +314,7 @@ YugabyteDB Aeon requires TLS/SSL. Depending on the smart driver, using load bala
 | Go | Yes | |
 | Node.js | Yes | In the ssl object, set `rejectUnauthorized` to true, `ca` to point to your cluster CA certificate, and `servername` to the cluster host name. |
 
-For more information on using TLS/SSL in YugabyteDB Aeon, refer to [Encryption in transit](../../yugabyte-cloud/cloud-secure-clusters/cloud-authentication/).
+For more information on using TLS/SSL in YugabyteDB Aeon, refer to [Encryption in transit](/preview/yugabyte-cloud/cloud-secure-clusters/cloud-authentication/).
 
 ## Learn more
 
