diff --git a/docs/content/preview/yugabyte-platform/administer-yugabyte-platform/anywhere-rbac.md b/docs/content/preview/yugabyte-platform/administer-yugabyte-platform/anywhere-rbac.md
index c60638dcef79..a05a89422b59 100644
--- a/docs/content/preview/yugabyte-platform/administer-yugabyte-platform/anywhere-rbac.md
+++ b/docs/content/preview/yugabyte-platform/administer-yugabyte-platform/anywhere-rbac.md
@@ -34,7 +34,7 @@ The following built-in roles are available:
 
 - **Super Admin** is the first user that is created during installation. This role has the highest level of privilege and allows all read and write actions on all YugabyteDB Anywhere resources. There can be only one Super Admin. Super Admin can perform the following:
 
-  - Manage all resources, including universes, nodes, backup, restore, and cloud providers.
+  - Manage all resources, including universes, nodes, backup, restore, and provider configurations.
   - Manage the user access control by creating and managing users.
 
   For more information, see [Create admin user](../../install-yugabyte-platform/create-admin-user/).
diff --git a/docs/content/preview/yugabyte-platform/administer-yugabyte-platform/high-availability.md b/docs/content/preview/yugabyte-platform/administer-yugabyte-platform/high-availability.md
index d45a289b1381..4f9daf59f355 100644
--- a/docs/content/preview/yugabyte-platform/administer-yugabyte-platform/high-availability.md
+++ b/docs/content/preview/yugabyte-platform/administer-yugabyte-platform/high-availability.md
@@ -214,7 +214,7 @@ In cases of failover, the previous active instance may be unavailable or unreach
 
 Afterwards, follow the steps in [Failover](#failover) to ensure that the old active does not come back up or that it goes into standby mode when it does come up.
 
-You should be able to see that all of the data has been restored into the instance, including universes, users, metrics, alerts, task history, cloud providers, and so on.
+You should be able to see that all of the data has been restored into the instance, including universes, users, metrics, alerts, task history, provider configurations, and so on.
 
 ### Verify promotion
 
diff --git a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/aws.md b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/aws.md
index 09418fbbe8d0..97c8e4322d6b 100644
--- a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/aws.md
+++ b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/aws.md
@@ -1,5 +1,5 @@
 ---
-title: Configure the AWS cloud provider
+title: Configure the AWS provider configuration
 headerTitle: Create cloud provider configuration
 linkTitle: Cloud providers
 description: Configure the Amazon Web Services (AWS) provider configuration.
diff --git a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/azure.md b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/azure.md
index 0f154b5b4c63..aa136b8df4d7 100644
--- a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/azure.md
+++ b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/azure.md
@@ -1,5 +1,5 @@
 ---
-title: Configure the Microsoft Azure cloud provider
+title: Configure the Microsoft Azure provider configuration
 headerTitle: Create cloud provider configuration
 linkTitle: Cloud providers
 description: Configure the Microsoft Azure provider configuration
diff --git a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/gcp.md b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/gcp.md
index 2d12ad53b2e9..f72fe0d84649 100644
--- a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/gcp.md
+++ b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/gcp.md
@@ -1,5 +1,5 @@
 ---
-title: Configure the GCP cloud provider
+title: Configure the GCP provider configuration
 headerTitle: Create cloud provider configuration
 linkTitle: Cloud providers
 description: Configure the Google Cloud Platform (GCP) cloud provider.
diff --git a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/kubernetes.md b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/kubernetes.md
index 8d988aa25e6c..104a96063274 100644
--- a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/kubernetes.md
+++ b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/kubernetes.md
@@ -1,5 +1,5 @@
 ---
-title: Configure the Kubernetes cloud provider
+title: Configure the Kubernetes provider configuration
 headerTitle: Create Kubernetes provider configuration
 linkTitle: Kubernetes
 description: Configure the Kubernetes provider configuration
@@ -425,9 +425,9 @@ spec:
 
 Refer to [Multi-Region YugabyteDB Deployments on Kubernetes with Istio](https://www.yugabyte.com/blog/multi-region-yugabytedb-deployments-on-kubernetes-with-istio/) for a step-by-step guide and an explanation of the options being used.
 
-### Configure the cloud provider for MCS
+### Configure the provider configuration for MCS
 
-After you have the cluster set up, follow the instructions in [Configure the Kubernetes cloud provider](#provider-settings), and refer to this section for region and zone configuration required for multi-region universes.
+After you have the cluster set up, follow the instructions in [Create a provider](#create-a-provider), and refer to this section for region and zone configuration required for multi-region universes.
 
 #### Configure region and zone for GKE MCS
 
@@ -452,7 +452,7 @@ For example, if your cluster membership name is `yb-asia-south1`, then the **Add
 
 #### Configure region and zones for OpenShift MCS
 
-Follow the instructions in [Configure the OpenShift cloud provider](../openshift/) and [Create a provider](#create-a-provider). For all the zones from your OpenShift clusters connected via MCS (Submariner), add a region as follows:
+Follow the instructions in [Create OpenShift provider configuration](../openshift/) and [Create a provider](#create-a-provider). For all the zones from your OpenShift clusters connected via MCS (Submariner), add a region as follows:
 
 1. Specify fields such as Region, Zone, and so on as you would normally.
 1. Set the **Cluster DNS Domain** to `clusterset.local`.
diff --git a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/on-premises-nodes.md b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/on-premises-nodes.md
index 0450b70d61ff..ad7d1129bd3d 100644
--- a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/on-premises-nodes.md
+++ b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/on-premises-nodes.md
@@ -115,4 +115,4 @@ After the instances are available in the **Instances** list, validate them by pe
 
 YugabyteDB Anywhere runs the check and displays the status in the **Preflight Check** column. Click in the column to view details; you can also view the results under **Tasks**.
 
-If all your instances successfully pass the preflight check, your on-premises cloud provider configuration is ready, and you can begin [deploying universes](../../create-deployments/).
+If all your instances successfully pass the preflight check, your on-premises provider configuration is ready, and you can begin [deploying universes](../../create-deployments/).
diff --git a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/openshift.md b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/openshift.md
index 23f134eee4a8..31062dc88234 100644
--- a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/openshift.md
+++ b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/openshift.md
@@ -1,9 +1,9 @@
 ---
-title: Configure the OpenShift cloud provider
+title: Configure the OpenShift provider configuration
 headerTitle: Create Kubernetes provider configuration
 linkTitle: Kubernetes
 description: Configure the OpenShift provider configuration
-headContent: For deploying universes on OpenShift
+headContent: For deploying universes on Kubernetes
 aliases:
   - /preview/deploy/enterprise-edition/configure-cloud-providers/openshift
 menu:
diff --git a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/vmware-tanzu.md b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/vmware-tanzu.md
index 02f8eee83966..1fafa996432d 100644
--- a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/vmware-tanzu.md
+++ b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/vmware-tanzu.md
@@ -1,9 +1,9 @@
 ---
-title: Configure the VMware Tanzu cloud provider
+title: Configure the VMware Tanzu provider configuration
 headerTitle: Create Kubernetes provider configuration
 linkTitle: Kubernetes
 description: Configure the VMware Tanzu provider configuration
-headContent: For deploying universes on VMware Tanzu
+headContent: For deploying universes on Kubernetes
 aliases:
   - /deploy/pivotal-cloud-foundry/
   - /preview/deploy/pivotal-cloud-foundry/
diff --git a/docs/content/preview/yugabyte-platform/create-deployments/create-universe-multi-cloud.md b/docs/content/preview/yugabyte-platform/create-deployments/create-universe-multi-cloud.md
index 96c84e57fd87..3f1336137cd5 100644
--- a/docs/content/preview/yugabyte-platform/create-deployments/create-universe-multi-cloud.md
+++ b/docs/content/preview/yugabyte-platform/create-deployments/create-universe-multi-cloud.md
@@ -23,7 +23,7 @@ To create a multi-cloud universe, you would need to do the following:
 * [Set up node instance virtual machines](#set-up-instance-vms) in each cloud (AWS, GCP, and Azure)
 * [Set up VPC peering](#set-up-vpc-peering) through a VPN tunnel across these 3 clouds
 * [Install YugabyteDB Anywhere](#install-yugabytedb-anywhere) on one of the nodes
-* [Configure the on-premises cloud provider](#configure-the-on-premises-cloud-provider)
+* [Configure the on-premises provider configuration](#configure-the-on-premises-provider-configuration)
 * [Create a universe](#create-a-universe) using the provider
 * [Run the TPC-C benchmark](#run-the-tpc-c-benchmark)
 
@@ -59,7 +59,7 @@ All public cloud providers enable VPN tunneling across VPCs and their subnet to
 
 Follow steps provided in [Install YugabyteDB Anywhere](../../install-yugabyte-platform/) to deploy YugabyteDB Anywhere on a new VM on one of your cloud providers. You will use this node to manage your YugabyteDB universe.
 
-## Configure the on-premises cloud provider
+## Configure the on-premises provider configuration
 
 To deploy a multi-cloud universe, you first need to create an on-premises provider configuration. Refer to [Create provider configuration](../../configure-yugabyte-platform/on-premises/) for more information.
 
diff --git a/docs/content/preview/yugabyte-platform/create-deployments/create-universe-multi-region.md b/docs/content/preview/yugabyte-platform/create-deployments/create-universe-multi-region.md
index c96df80b59d2..374ec28435cf 100644
--- a/docs/content/preview/yugabyte-platform/create-deployments/create-universe-multi-region.md
+++ b/docs/content/preview/yugabyte-platform/create-deployments/create-universe-multi-region.md
@@ -21,11 +21,11 @@ Before you start creating a universe, ensure that you have created a provider co
 
 ## Create a universe
 
-After you have configured a cloud provider, such as, for example [Google Cloud Provider](../../configure-yugabyte-platform/gcp/) (GCP), navigate to **Universes**, click **Create Universe**, and enter the following sample values:
+After you have created a provider configuration, such as, for example [Google Cloud Provider](../../configure-yugabyte-platform/gcp/) (GCP), navigate to **Universes**, click **Create Universe**, and enter the following sample values:
 
 - In the **Name** field, enter **helloworld2**.
 
-- In the **Provider** field, select the cloud provider you configured.
+- In the **Provider** field, select the provider you configured.
 
 - Use the **Regions** field to select the regions where you want to deploy nodes.
 
diff --git a/docs/content/preview/yugabyte-platform/install-yugabyte-platform/prerequisites-include.md b/docs/content/preview/yugabyte-platform/install-yugabyte-platform/prerequisites-include.md
index ca21bd603697..1fa24283f474 100644
--- a/docs/content/preview/yugabyte-platform/install-yugabyte-platform/prerequisites-include.md
+++ b/docs/content/preview/yugabyte-platform/install-yugabyte-platform/prerequisites-include.md
@@ -32,17 +32,17 @@ A Kubernetes-based installation of YugabyteDB Anywhere requires you to address c
 
 The core dump collection in Kubernetes requires special care due to the fact that `core_pattern` is not isolated in cgroup drivers.
 
-You need to ensure that core dumps are enabled on the underlying Kubernetes node. Running the `ulimit -c` command within a Kubernetes pod or node must produce a large non-zero value or the `unlimited` value as an output. For more information, see [How to enable core dumps](https://www.ibm.com/support/pages/how-do-i-enable-core-dumps).
+You need to ensure that core dumps are enabled on the underlying Kubernetes node. Running the `ulimit -c` command in a Kubernetes pod or node must produce a large non-zero value or the `unlimited` value as an output. For more information, see [How to enable core dumps](https://www.ibm.com/support/pages/how-do-i-enable-core-dumps).
 
 To be able to locate your core dumps, you should be aware of the fact that the location to which core dumps are written depends on the sysctl `kernel.core_pattern` setting. For more information, see [Linux manual: core(5)](https://man7.org/linux/man-pages/man5/core.5.html#:~:text=Naming%20of%20core%20dump%20files).
 
-To inspect the value of the sysctl within a Kubernetes pod or node, execute the following:
+To inspect the value of the sysctl in a Kubernetes pod or node, execute the following:
 
 ```sh
 cat /proc/sys/kernel/core_pattern
 ```
 
-If the value of `core_pattern` contains a `|` pipe symbol (for example, `|/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E`), the core dump is being redirected to a specific collector on the underlying Kubernetes node, with the location depending on the exact collector. To be able to retrieve core dump files in case of a crash within the Kubernetes pod, it is important that you understand where these files are written.
+If the value of `core_pattern` contains a `|` pipe symbol (for example, `|/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E`), the core dump is being redirected to a specific collector on the underlying Kubernetes node, with the location depending on the exact collector. To be able to retrieve core dump files in case of a crash in the Kubernetes pod, it is important that you understand where these files are written.
 
 If the value of `core_pattern` is a literal path of the form `/var/tmp/core.%p`, no action is required on your part, as core dumps will be copied by the YugabyteDB node to the persistent volume directory `/mnt/disk0/cores` for future analysis.
 
diff --git a/docs/content/preview/yugabyte-platform/manage-deployments/edit-universe.md b/docs/content/preview/yugabyte-platform/manage-deployments/edit-universe.md
index daf9763e5372..d0053995d023 100644
--- a/docs/content/preview/yugabyte-platform/manage-deployments/edit-universe.md
+++ b/docs/content/preview/yugabyte-platform/manage-deployments/edit-universe.md
@@ -52,7 +52,7 @@ To change the configuration of a universe, do the following:
 
 YugabyteDB automatically ensures that new nodes start hosting the tablet leaders for a set of tablets in such a way that the tablet leader count remains evenly balanced across all the available nodes.
 
-To change the number of nodes of universes created with an on-premises cloud provider and secured with third-party certificates obtained from external certification authorities, you must first add the certificates to the nodes you will add to the universe. Refer to [Add certificates](../../security/enable-encryption-in-transit/add-certificate-ca/). Ensure that the certificates are signed by the same external CA and have the same root certificate. In addition, ensure that you copy the certificates to the same locations that you originally used when creating the universe.
+To change the number of nodes of universes created with an on-premises provider and secured with third-party certificates obtained from external certification authorities, you must first add the certificates to the nodes you will add to the universe. Refer to [Add certificates](../../security/enable-encryption-in-transit/add-certificate-ca/). Ensure that the certificates are signed by the same external CA and have the same root certificate. In addition, ensure that you copy the certificates to the same locations that you originally used when creating the universe.
 
 ## Smart resize
 
diff --git a/docs/content/preview/yugabyte-platform/prepare/networking-kubernetes.md b/docs/content/preview/yugabyte-platform/prepare/networking-kubernetes.md
index 061e5d491770..c890f1d8c6cf 100644
--- a/docs/content/preview/yugabyte-platform/prepare/networking-kubernetes.md
+++ b/docs/content/preview/yugabyte-platform/prepare/networking-kubernetes.md
@@ -44,7 +44,7 @@ To achieve network connectivity across multiple Kubernetes clusters, you can set
 
 GKE MCS allows clusters to be combined as a fleet on Google Cloud. These fleet clusters can export services, which enables you to do cross-cluster communication. For more information, see [Multi-cluster Services](https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-services) in the Google Cloud documentation.
 
-To enable MCS on your GKE clusters, see [Configuring multi-cluster Services](https://cloud.google.com/kubernetes-engine/docs/how-to/multi-cluster-services). Note down the unique membership name of each cluster in the fleet, it will be used during the cloud provider setup in YBA.
+To enable MCS on your GKE clusters, see [Configuring multi-cluster Services](https://cloud.google.com/kubernetes-engine/docs/how-to/multi-cluster-services). Note down the unique membership name of each cluster in the fleet, it will be used during the provider setup in YBA.
 
 ### Prepare OpenShift clusters for MCS
 
diff --git a/docs/content/preview/yugabyte-platform/prepare/server-nodes-software/_index.md b/docs/content/preview/yugabyte-platform/prepare/server-nodes-software/_index.md
index b40ef2120537..1c2fd906bf48 100644
--- a/docs/content/preview/yugabyte-platform/prepare/server-nodes-software/_index.md
+++ b/docs/content/preview/yugabyte-platform/prepare/server-nodes-software/_index.md
@@ -13,6 +13,7 @@ aliases:
   - /preview/yugabyte-platform/configure-yugabyte-platform/supported-os-and-arch/
   - /preview/yugabyte-platform/install-yugabyte-platform/prepare-on-prem-nodes/
 type: indexpage
+showRightNav: true
 ---
 
 The Linux OS and other software components on each database cluster node must meet the following minimum software requirements.
@@ -20,7 +21,7 @@ The Linux OS and other software components on each database cluster node must me
 Depending on the [provider type](../../yba-overview/#provider-configurations) and permissions you grant, you may have to install all of these requirements manually, or YugabyteDB Anywhere will install it all automatically.
 
 {{< warning title="Using disk encryption software with YugabyteDB" >}}
-If you are using third party disk encryption software, such as Vormetric or CipherTrust, the disk encryption service must be up and running on the node before starting any YugabyteDB services. If YugabyteDB processes start _before_ the encryption service, restarting an already encrypted node can result in data corruption.
+If you are using third party disk encryption software (such as Vormetric or CipherTrust), the disk encryption service must be up and running on the node before starting any YugabyteDB services. If YugabyteDB processes start _before_ the encryption service, restarting an already encrypted node can result in data corruption.
 
 To avoid problems, [pause the universe](../../manage-deployments/delete-universe/#pause-a-universe) _before_ enabling or disabling the disk encryption service on universe nodes.
 {{< /warning >}}
diff --git a/docs/content/preview/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md b/docs/content/preview/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md
index adf1d0f4f983..a6686d51d0e1 100644
--- a/docs/content/preview/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md
+++ b/docs/content/preview/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md
@@ -41,9 +41,9 @@ Take the time now to prepare the Linux disk image.
 
 | Save for later | To configure |
 | :--- | :--- |
-| SSH-enabled, root-privileged user name | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| Disk image IDs | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged user name | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| Disk image IDs | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
 
 ## Custom Linux version without Internet connectivity
 
@@ -60,6 +60,6 @@ Take the time now to prepare the Linux disk image.
 
 | Save for later | To configure |
 | :--- | :--- |
-| SSH-enabled, root-privileged user name | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| Disk image IDs | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged user name | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| Disk image IDs | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
diff --git a/docs/content/preview/yugabyte-platform/troubleshoot/_index.md b/docs/content/preview/yugabyte-platform/troubleshoot/_index.md
index 6bfff742425d..ce5df01ea7a8 100644
--- a/docs/content/preview/yugabyte-platform/troubleshoot/_index.md
+++ b/docs/content/preview/yugabyte-platform/troubleshoot/_index.md
@@ -32,7 +32,7 @@ type: indexpage
 
   {{<index/item
     title="Cloud provider configuration issues"
-    body="Troubleshoot issues encountered when configuring cloud providers."
+    body="Troubleshoot issues encountered when creating provider configurations."
     href="cloud-provider-config-issues/"
     icon="/images/section_icons/quick_start/create_cluster.png">}}
 
diff --git a/docs/content/preview/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md b/docs/content/preview/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md
index 731f4f84384e..10a5285d9cd7 100644
--- a/docs/content/preview/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md
+++ b/docs/content/preview/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md
@@ -1,8 +1,8 @@
 ---
-title: Troubleshoot cloud provider configuration issues
+title: Troubleshoot provider configuration issues
 headerTitle:
-linkTitle: Cloud provider configuration issues
-description: Troubleshoot issues encountered when configuring cloud providers for YugabyteDB Anywhere.
+linkTitle: Provider configuration issues
+description: Troubleshoot issues encountered when creating provider configurations for YugabyteDB Anywhere.
 menu:
   preview_yugabyte-platform:
     identifier: cloud-provider-config-issues
@@ -11,13 +11,13 @@ menu:
 type: docs
 ---
 
-You might encounter issues during configuration of cloud providers for YugabyteDB Anywhere.
+You might encounter issues when creating provider configurations for YugabyteDB Anywhere.
 
 If you have problems while troubleshooting, contact {{% support-platform %}}.
 
 ## Azure cloud provider configuration problems
 
-You can diagnose and remedy a failure that occurred when [configuring Azure cloud provider](../../configure-yugabyte-platform/azure/) as follows:
+You can diagnose and remedy a failure that occurred when [creating an Azure provider configuration](../../configure-yugabyte-platform/azure/) as follows:
 
 - Navigate to **Tasks** on the left-side menu.
 
diff --git a/docs/content/stable/yugabyte-platform/administer-yugabyte-platform/anywhere-rbac.md b/docs/content/stable/yugabyte-platform/administer-yugabyte-platform/anywhere-rbac.md
index 9d4f20a99005..180f44cf9468 100644
--- a/docs/content/stable/yugabyte-platform/administer-yugabyte-platform/anywhere-rbac.md
+++ b/docs/content/stable/yugabyte-platform/administer-yugabyte-platform/anywhere-rbac.md
@@ -34,7 +34,7 @@ The following built-in roles are available:
 
 - **Super Admin** is the first user that is created during installation. This role has the highest level of privilege and allows all read and write actions on all YugabyteDB Anywhere resources. There can be only one Super Admin. Super Admin can perform the following:
 
-  - Manage all resources, including universes, nodes, backup, restore, and cloud providers.
+  - Manage all resources, including universes, nodes, backup, restore, and provider configurations.
   - Manage the user access control by creating and managing users.
 
   For more information, see [Create admin user](../../install-yugabyte-platform/create-admin-user/).
diff --git a/docs/content/stable/yugabyte-platform/administer-yugabyte-platform/high-availability.md b/docs/content/stable/yugabyte-platform/administer-yugabyte-platform/high-availability.md
index b67f387892df..62cd9b9a4bc5 100644
--- a/docs/content/stable/yugabyte-platform/administer-yugabyte-platform/high-availability.md
+++ b/docs/content/stable/yugabyte-platform/administer-yugabyte-platform/high-availability.md
@@ -211,7 +211,7 @@ In cases of failover, the previous active instance may be unavailable or unreach
 
 Afterwards, follow the steps in [Failover](#failover) to ensure that the old active does not come back up or that it goes into standby mode when it does come up.
 
-You should be able to see that all of the data has been restored into the instance, including universes, users, metrics, alerts, task history, cloud providers, and so on.
+You should be able to see that all of the data has been restored into the instance, including universes, users, metrics, alerts, task history, provider configurations, and so on.
 
 ### Verify promotion
 
diff --git a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/aws.md b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/aws.md
index 0ba0e034199c..707c71f87810 100644
--- a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/aws.md
+++ b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/aws.md
@@ -1,5 +1,5 @@
 ---
-title: Configure the AWS cloud provider
+title: Configure the AWS provider configuration
 headerTitle: Create cloud provider configuration
 linkTitle: Cloud providers
 description: Configure the Amazon Web Services (AWS) provider configuration.
diff --git a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/azure.md b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/azure.md
index b9df098b9d57..5e7d0cee1380 100644
--- a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/azure.md
+++ b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/azure.md
@@ -1,5 +1,5 @@
 ---
-title: Configure the Microsoft Azure cloud provider
+title: Configure the Microsoft Azure provider configuration
 headerTitle: Create cloud provider configuration
 linkTitle: Cloud providers
 description: Configure the Microsoft Azure provider configuration
diff --git a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/gcp.md b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/gcp.md
index b45e057f243f..efc5118ed68f 100644
--- a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/gcp.md
+++ b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/gcp.md
@@ -1,5 +1,5 @@
 ---
-title: Configure the GCP cloud provider
+title: Configure the GCP provider configuration
 headerTitle: Create cloud provider configuration
 linkTitle: Cloud providers
 description: Configure the Google Cloud Platform (GCP) cloud provider.
diff --git a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/kubernetes.md b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/kubernetes.md
index f6c8eea105d3..2fc50d39ffa9 100644
--- a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/kubernetes.md
+++ b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/kubernetes.md
@@ -1,5 +1,5 @@
 ---
-title: Configure the Kubernetes cloud provider
+title: Configure the Kubernetes provider configuration
 headerTitle: Create Kubernetes provider configuration
 linkTitle: Kubernetes
 description: Configure the Kubernetes provider configuration
@@ -423,9 +423,9 @@ spec:
 
 Refer to [Multi-Region YugabyteDB Deployments on Kubernetes with Istio](https://www.yugabyte.com/blog/multi-region-yugabytedb-deployments-on-kubernetes-with-istio/) for a step-by-step guide and an explanation of the options being used.
 
-### Configure the cloud provider for MCS
+### Configure the provider configuration for MCS
 
-After you have the cluster set up, follow the instructions in [Configure the Kubernetes cloud provider](#provider-settings), and refer to this section for region and zone configuration required for multi-region universes.
+After you have the cluster set up, follow the instructions in [Create a provider](#create-a-provider), and refer to this section for region and zone configuration required for multi-region universes.
 
 #### Configure region and zone for GKE MCS
 
@@ -450,7 +450,7 @@ For example, if your cluster membership name is `yb-asia-south1`, then the **Add
 
 #### Configure region and zones for OpenShift MCS
 
-Follow the instructions in [Configure the OpenShift cloud provider](../openshift/) and [Create a provider](#create-a-provider). For all the zones from your OpenShift clusters connected via MCS (Submariner), add a region as follows:
+Follow the instructions in [Create OpenShift provider configuration](../openshift/) and [Create a provider](#create-a-provider). For all the zones from your OpenShift clusters connected via MCS (Submariner), add a region as follows:
 
 1. Specify fields such as Region, Zone, and so on as you would normally.
 1. Set the **Cluster DNS Domain** to `clusterset.local`.
diff --git a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/openshift.md b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/openshift.md
index 239de7cf5ee9..138a3892f61c 100644
--- a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/openshift.md
+++ b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/openshift.md
@@ -1,9 +1,9 @@
 ---
-title: Configure the OpenShift cloud provider
+title: Configure the OpenShift provider configuration
 headerTitle: Create Kubernetes provider configuration
 linkTitle: Kubernetes
 description: Configure the OpenShift provider configuration
-headContent: For deploying universes on OpenShift
+headContent: For deploying universes on Kubernetes
 menu:
   stable_yugabyte-platform:
     identifier: set-up-kubernetes-provider-3
diff --git a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/vmware-tanzu.md b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/vmware-tanzu.md
index a1bd72d36108..5c38d9e721da 100644
--- a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/vmware-tanzu.md
+++ b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/vmware-tanzu.md
@@ -1,9 +1,9 @@
 ---
-title: Configure the VMware Tanzu cloud provider
+title: Configure the VMware Tanzu provider configuration
 headerTitle: Create Kubernetes provider configuration
 linkTitle: Kubernetes
 description: Configure the VMware Tanzu provider configuration
-headContent: For deploying universes on VMware Tanzu
+headContent: For deploying universes on Kubernetes
 menu:
   stable_yugabyte-platform:
     identifier: set-up-kubernetes-provider-2
diff --git a/docs/content/stable/yugabyte-platform/create-deployments/create-universe-multi-cloud.md b/docs/content/stable/yugabyte-platform/create-deployments/create-universe-multi-cloud.md
index 3451ed0ad82c..b45ae2d2a484 100644
--- a/docs/content/stable/yugabyte-platform/create-deployments/create-universe-multi-cloud.md
+++ b/docs/content/stable/yugabyte-platform/create-deployments/create-universe-multi-cloud.md
@@ -23,7 +23,7 @@ To create a multi-cloud universe, you would need to do the following:
 * [Set up node instance virtual machines](#set-up-instance-vms) in each cloud (AWS, GCP, and Azure)
 * [Set up VPC peering](#set-up-vpc-peering) through a VPN tunnel across these 3 clouds
 * [Install YugabyteDB Anywhere](#install-yugabytedb-anywhere) on one of the nodes
-* [Configure the on-premises cloud provider](#configure-the-on-premises-cloud-provider)
+* [Configure the on-premises provider configuration](#configure-the-on-premises-provider-configuration)
 * [Create a universe](#create-a-universe) using the provider
 * [Run the TPC-C benchmark](#run-the-tpc-c-benchmark)
 
@@ -59,7 +59,7 @@ All public cloud providers enable VPN tunneling across VPCs and their subnet to
 
 Follow steps provided in [Install YugabyteDB Anywhere](../../install-yugabyte-platform/) to deploy YugabyteDB Anywhere on a new VM on one of your cloud providers. You will use this node to manage your YugabyteDB universe.
 
-## Configure the on-premises cloud provider
+## Configure the on-premises provider configuration
 
 To deploy a multi-cloud universe, you first need to create an on-premises provider configuration. Refer to [Create provider configuration](../../configure-yugabyte-platform/on-premises/) for more information.
 
diff --git a/docs/content/stable/yugabyte-platform/create-deployments/create-universe-multi-region.md b/docs/content/stable/yugabyte-platform/create-deployments/create-universe-multi-region.md
index 7408c9a65452..6da07c91ee3d 100644
--- a/docs/content/stable/yugabyte-platform/create-deployments/create-universe-multi-region.md
+++ b/docs/content/stable/yugabyte-platform/create-deployments/create-universe-multi-region.md
@@ -21,7 +21,7 @@ Before you start creating a universe, ensure that you have created a provider co
 
 ## Create a universe
 
-After you have configured a cloud provider, such as, for example [Google Cloud Provider](../../configure-yugabyte-platform/gcp/) (GCP), navigate to **Universes**, click **Create Universe**, and enter the following sample values:
+After you have created a provider configuration, such as, for example [Google Cloud Provider](../../configure-yugabyte-platform/gcp/) (GCP), navigate to **Universes**, click **Create Universe**, and enter the following sample values:
 
 - In the **Name** field, enter **helloworld2**.
 
diff --git a/docs/content/stable/yugabyte-platform/manage-deployments/edit-universe.md b/docs/content/stable/yugabyte-platform/manage-deployments/edit-universe.md
index a5da6e40413d..b2f3b60d23ec 100644
--- a/docs/content/stable/yugabyte-platform/manage-deployments/edit-universe.md
+++ b/docs/content/stable/yugabyte-platform/manage-deployments/edit-universe.md
@@ -50,7 +50,7 @@ To change the configuration of a universe, do the following:
 
 YugabyteDB automatically ensures that new nodes start hosting the tablet leaders for a set of tablets in such a way that the tablet leader count remains evenly balanced across all the available nodes.
 
-To change the number of nodes of universes created with an on-premises cloud provider and secured with third-party certificates obtained from external certification authorities, you must first add the certificates to the nodes you will add to the universe. Refer to [Add certificates](../../security/enable-encryption-in-transit/add-certificate-ca/). Ensure that the certificates are signed by the same external CA and have the same root certificate. In addition, ensure that you copy the certificates to the same locations that you originally used when creating the universe.
+To change the number of nodes of universes created with an on-premises provider and secured with third-party certificates obtained from external certification authorities, you must first add the certificates to the nodes you will add to the universe. Refer to [Add certificates](../../security/enable-encryption-in-transit/add-certificate-ca/). Ensure that the certificates are signed by the same external CA and have the same root certificate. In addition, ensure that you copy the certificates to the same locations that you originally used when creating the universe.
 
 ### Edit connection pooling
 
diff --git a/docs/content/stable/yugabyte-platform/prepare/cloud-permissions/cloud-permissions-nodes-aws.md b/docs/content/stable/yugabyte-platform/prepare/cloud-permissions/cloud-permissions-nodes-aws.md
index c66935dc4710..9e35697cf111 100644
--- a/docs/content/stable/yugabyte-platform/prepare/cloud-permissions/cloud-permissions-nodes-aws.md
+++ b/docs/content/stable/yugabyte-platform/prepare/cloud-permissions/cloud-permissions-nodes-aws.md
@@ -174,7 +174,7 @@ When creating VMs on the public cloud, YugabyteDB requires SSH keys to access th
 - YBA managed keys. When YBA creates VMs, it will generate and manage the SSH key pair.
 - Provide a custom key pair. Create your own custom SSH keys and upload the SSH keys when you create the provider.
 
-If you will be using your own custom SSH keys, then ensure that you have them when installing YBA and creating your public cloud provider.
+If you will be using your own custom SSH keys, then ensure that you have them when installing YBA and creating your public cloud provider configuration.
 
 | Save for later | To configure |
 | :--- | :--- |
diff --git a/docs/content/stable/yugabyte-platform/prepare/cloud-permissions/cloud-permissions-nodes-azure.md b/docs/content/stable/yugabyte-platform/prepare/cloud-permissions/cloud-permissions-nodes-azure.md
index b5e25b35d80d..b370f84bb41a 100644
--- a/docs/content/stable/yugabyte-platform/prepare/cloud-permissions/cloud-permissions-nodes-azure.md
+++ b/docs/content/stable/yugabyte-platform/prepare/cloud-permissions/cloud-permissions-nodes-azure.md
@@ -101,7 +101,7 @@ When creating VMs on the public cloud, YugabyteDB requires SSH keys to access th
 - YBA managed keys. When YBA creates VMs, it will generate and manage the SSH key pair.
 - Provide a custom key pair. Create your own custom SSH keys and upload the SSH keys when you create the provider.
 
-If you will be using your own custom SSH keys, then ensure that you have them when installing YBA and creating your public cloud provider.
+If you will be using your own custom SSH keys, then ensure that you have them when installing YBA and creating your public cloud provider configuration.
 
 | Save for later | To configure |
 | :--- | :--- |
diff --git a/docs/content/stable/yugabyte-platform/prepare/cloud-permissions/cloud-permissions-nodes-gcp.md b/docs/content/stable/yugabyte-platform/prepare/cloud-permissions/cloud-permissions-nodes-gcp.md
index 3ce2bbefaaec..4c8c7567f43c 100644
--- a/docs/content/stable/yugabyte-platform/prepare/cloud-permissions/cloud-permissions-nodes-gcp.md
+++ b/docs/content/stable/yugabyte-platform/prepare/cloud-permissions/cloud-permissions-nodes-gcp.md
@@ -79,7 +79,7 @@ When creating VMs on the public cloud, YugabyteDB requires SSH keys to access th
 - YBA managed keys. When YBA creates VMs, it will generate and manage the SSH key pair.
 - Provide a custom key pair. Create your own custom SSH keys and upload the SSH keys when you create the provider.
 
-If you will be using your own custom SSH keys, then ensure that you have them when installing YBA and creating your public cloud provider.
+If you will be using your own custom SSH keys, then ensure that you have them when installing YBA and creating your public cloud provider configuration.
 
 | Save for later | To configure |
 | :--- | :--- |
diff --git a/docs/content/stable/yugabyte-platform/prepare/server-nodes-software/_index.md b/docs/content/stable/yugabyte-platform/prepare/server-nodes-software/_index.md
index ae9dca7223cf..c8d5ace4e92e 100644
--- a/docs/content/stable/yugabyte-platform/prepare/server-nodes-software/_index.md
+++ b/docs/content/stable/yugabyte-platform/prepare/server-nodes-software/_index.md
@@ -10,6 +10,7 @@ menu:
     parent: server-nodes
     weight: 20
 type: indexpage
+showRightNav: true
 ---
 
 The Linux OS and other software components on each database cluster node must meet the following minimum software requirements.
@@ -17,7 +18,7 @@ The Linux OS and other software components on each database cluster node must me
 Depending on the [provider type](../../yba-overview/#provider-configurations) and permissions you grant, you may have to install all of these requirements manually, or YugabyteDB Anywhere will install it all automatically.
 
 {{< warning title="Using disk encryption software with YugabyteDB" >}}
-If you are using third party disk encryption software, such as Vormetric or CipherTrust, the disk encryption service must be up and running on the node before starting any YugabyteDB services. If YugabyteDB processes start _before_ the encryption service, restarting an already encrypted node can result in data corruption.
+If you are using third party disk encryption software (such as Vormetric or CipherTrust), the disk encryption service must be up and running on the node before starting any YugabyteDB services. If YugabyteDB processes start _before_ the encryption service, restarting an already encrypted node can result in data corruption.
 
 To avoid problems, [pause the universe](../../manage-deployments/delete-universe/#pause-a-universe) _before_ enabling or disabling the disk encryption service on universe nodes.
 {{< /warning >}}
diff --git a/docs/content/stable/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md b/docs/content/stable/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md
index 1fc6d79dbedf..1e03525660b1 100644
--- a/docs/content/stable/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md
+++ b/docs/content/stable/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md
@@ -41,9 +41,9 @@ Take the time now to prepare the Linux disk image.
 
 | Save for later | To configure |
 | :--- | :--- |
-| SSH-enabled, root-privileged user name | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| Disk image IDs | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged user name | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| Disk image IDs | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
 
 ## Custom Linux version without Internet connectivity
 
@@ -60,6 +60,6 @@ Take the time now to prepare the Linux disk image.
 
 | Save for later | To configure |
 | :--- | :--- |
-| SSH-enabled, root-privileged user name | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| Disk image IDs | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged user name | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| Disk image IDs | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
diff --git a/docs/content/stable/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md b/docs/content/stable/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md
index b95b0d3f2547..b95a2d40248c 100644
--- a/docs/content/stable/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md
+++ b/docs/content/stable/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md
@@ -17,7 +17,7 @@ If you have problems while troubleshooting, contact {{% support-platform %}}.
 
 ## Azure cloud provider configuration problems
 
-You can diagnose and remedy a failure that occurred when [configuring Azure cloud provider](../../configure-yugabyte-platform/azure/) as follows:
+You can diagnose and remedy a failure that occurred when [creating an Azure provider configuration](../../configure-yugabyte-platform/azure/) as follows:
 
 - Navigate to **Tasks** on the left-side menu.
 
diff --git a/docs/content/v2.14/yugabyte-platform/configure-yugabyte-platform/set-up-cloud-provider/on-premises.md b/docs/content/v2.14/yugabyte-platform/configure-yugabyte-platform/set-up-cloud-provider/on-premises.md
index 4ee784260207..d50bea8bd515 100644
--- a/docs/content/v2.14/yugabyte-platform/configure-yugabyte-platform/set-up-cloud-provider/on-premises.md
+++ b/docs/content/v2.14/yugabyte-platform/configure-yugabyte-platform/set-up-cloud-provider/on-premises.md
@@ -72,7 +72,7 @@ Configuring the on-premises provider consists of a number of steps.
 
 You need to navigate to **Configs > Infrastructure > On-Premises Datacenters**, click either **Add Configuration** or **Edit Provider**, and then complete the fields of the **Provider Info** form shown in the following illustration:
 
-![Configure On-Premises Cloud Provider](/images/ee/onprem/configure-onprem-1.png)
+![Configure On-Premises Provider Configuration](/images/ee/onprem/configure-onprem-1.png)
 
 - In the **Provider Name** field, supply the provider name, which is an internal tag that helps with organizing your providers, so you know where you want to deploy your YugabyteDB universes.
 
@@ -112,7 +112,7 @@ You need to navigate to **Configs > Infrastructure > On-Premises Datacenters**,
 
 Complete the **Instance Types** fields, as per the following illustration, to provide node hardware configuration (CPU, memory, and volume information):
 
-![Configure On-Premises Cloud Provider](/images/ee/onprem/configure-onprem-2.png)
+![Configure On-Premises Provider Configuration](/images/ee/onprem/configure-onprem-2.png)
 
 - Use the **Machine Type** field to define a value to be used internally as an identifier in the **Instance Type** universe field.
 - Use the **Num Cores** field to define the number of cores to be assigned to a node.
@@ -124,7 +124,7 @@ Complete the **Instance Types** fields, as per the following illustration, to pr
 
 Complete the **Regions and Zones** fields, as per the following illustration, to provide the location of YugabyteDB nodes:
 
-![Configure On-Premises Cloud Provider](/images/ee/onprem/configure-onprem-3.png)
+![Configure On-Premises Provider Configuration](/images/ee/onprem/configure-onprem-3.png)
 
 YugabyteDB Anywhere will use these values during the universe creation.
 
@@ -132,11 +132,11 @@ YugabyteDB Anywhere will use these values during the universe creation.
 
 After finishing the provider configuration, click **Manage Instances** to provision as many nodes as your application requires.
 
-![Configure On-Premises Cloud Provider](/images/ee/onprem/configure-onprem-4.png)
+![Configure On-Premises Provider Configuration](/images/ee/onprem/configure-onprem-4.png)
 
 For each node you want to add, click **Add Instances** to add a YugabyteDB node. You can use DNS names or IP addresses when adding instances (instance ID is an optional user-defined identifier).
 
-![Configure On-Premises Cloud Provider](/images/ee/onprem/configure-onprem-5.png)
+![Configure On-Premises Provider Configuration](/images/ee/onprem/configure-onprem-5.png)
 
 Note that if you provide a hostname, the universe might experience issues communicating. To resolve this, you need to delete the failed universe and then recreate it with the `use_node_hostname_for_local_tserver` flag enabled.
 
@@ -144,7 +144,7 @@ Note that if you provide a hostname, the universe might experience issues commun
 
 To provision your nodes manually, you have the following two options:
 
-1. If the SSH user you provided has sudo privileges but requires a password, you can [run the preprovisioning script](#running-the-preprovisioning-script).
+1. If the SSH user you provided has sudo privileges but requires a password, you can [run the pre-provisioning script](#running-the-preprovisioning-script).
 2. If the SSH user does not have any sudo privileges, you need to [set up the database nodes manually](#setting-up-database-nodes-manually).
 
 #### Running the preprovisioning script
diff --git a/docs/content/v2.20/yugabyte-platform/configure-yugabyte-platform/kubernetes.md b/docs/content/v2.20/yugabyte-platform/configure-yugabyte-platform/kubernetes.md
index d930792fa8b8..91cf8d5f8c50 100644
--- a/docs/content/v2.20/yugabyte-platform/configure-yugabyte-platform/kubernetes.md
+++ b/docs/content/v2.20/yugabyte-platform/configure-yugabyte-platform/kubernetes.md
@@ -425,7 +425,7 @@ Refer to [Multi-Region YugabyteDB Deployments on Kubernetes with Istio](https://
 
 ### Configure the cloud provider for MCS
 
-After you have the cluster set up, follow the instructions in [Configure the Kubernetes cloud provider](#provider-settings), and refer to this section for region and zone configuration required for multi-region universes.
+After you have the cluster set up, follow the instructions in [Create a provider](#create-a-provider), and refer to this section for region and zone configuration required for multi-region universes.
 
 #### Configure region and zone for GKE MCS
 
@@ -450,7 +450,7 @@ For example, if your cluster membership name is `yb-asia-south1`, then the **Add
 
 #### Configure region and zones for OpenShift MCS
 
-Follow the instructions in [Configure the OpenShift cloud provider](../openshift/) and [Create a provider in YugabyteDB Anywhere](../openshift/#create-a-provider-in-yugabytedb-anywhere). For all the zones from your OpenShift clusters connected via MCS (Submariner), add a region as follows:
+Follow the instructions in [Create OpenShift provider configuration](../openshift/) and [Create a provider](#create-a-provider). For all the zones from your OpenShift clusters connected via MCS (Submariner), add a region as follows:
 
 1. Specify fields such as Region, Zone, and so on as you would normally.
 1. Set the **Cluster DNS Domain** to `clusterset.local`.
diff --git a/docs/content/v2.20/yugabyte-platform/create-deployments/create-universe-multi-cloud.md b/docs/content/v2.20/yugabyte-platform/create-deployments/create-universe-multi-cloud.md
index c032238c0a56..eef585ee1583 100644
--- a/docs/content/v2.20/yugabyte-platform/create-deployments/create-universe-multi-cloud.md
+++ b/docs/content/v2.20/yugabyte-platform/create-deployments/create-universe-multi-cloud.md
@@ -23,7 +23,7 @@ To create a multi-cloud universe, you would need to do the following:
 * [Set up node instance virtual machines](#set-up-instance-vms) in each cloud (AWS, GCP, and Azure)
 * [Set up VPC peering](#set-up-vpc-peering) through a VPN tunnel across these 3 clouds
 * [Install YugabyteDB Anywhere](#install-yugabytedb-anywhere) on one of the nodes
-* [Configure the on-premises cloud provider](#configure-the-on-premises-cloud-provider)
+* [Configure the on-premises provider configuration](#configure-the-on-premises-provider-configuration)
 * [Create a universe](#create-a-universe) using the provider
 * [Run the TPC-C benchmark](#run-the-tpc-c-benchmark)
 
@@ -59,7 +59,7 @@ All public cloud providers enable VPN tunneling across VPCs and their subnet to
 
 Follow steps provided in [Install YugabyteDB Anywhere](../../install-yugabyte-platform/) to deploy YugabyteDB Anywhere on a new VM on one of your cloud providers. You will use this node to manage your YugabyteDB universe.
 
-## Configure the on-premises cloud provider
+## Configure the on-premises provider configuration
 
 To deploy a multi-cloud universe, you first need to create an on-premises provider configuration. Refer to [Create provider configuration](../../configure-yugabyte-platform/on-premises/) for more information.
 
diff --git a/docs/content/v2.20/yugabyte-platform/prepare/server-nodes-software/_index.md b/docs/content/v2.20/yugabyte-platform/prepare/server-nodes-software/_index.md
index ad4a2339f6c0..f3ed5cc17cea 100644
--- a/docs/content/v2.20/yugabyte-platform/prepare/server-nodes-software/_index.md
+++ b/docs/content/v2.20/yugabyte-platform/prepare/server-nodes-software/_index.md
@@ -10,6 +10,7 @@ menu:
     parent: server-nodes
     weight: 20
 type: indexpage
+showRightNav: true
 ---
 
 The Linux OS and other software components on each database cluster node must meet the following minimum software requirements.
diff --git a/docs/content/v2.20/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md b/docs/content/v2.20/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md
index 3d04f505e98e..d756ccc885c6 100644
--- a/docs/content/v2.20/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md
+++ b/docs/content/v2.20/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md
@@ -41,9 +41,9 @@ Take the time now to prepare the Linux disk image.
 
 | Save for later | To configure |
 | :--- | :--- |
-| SSH-enabled, root-privileged user name | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| Disk image IDs | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged user name | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| Disk image IDs | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
 
 ## Custom Linux version without Internet connectivity
 
@@ -60,6 +60,6 @@ Take the time now to prepare the Linux disk image.
 
 | Save for later | To configure |
 | :--- | :--- |
-| SSH-enabled, root-privileged user name | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| Disk image IDs | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged user name | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| Disk image IDs | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
diff --git a/docs/content/v2.20/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md b/docs/content/v2.20/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md
index 66ce62c56b2a..a4aa7ee61663 100644
--- a/docs/content/v2.20/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md
+++ b/docs/content/v2.20/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md
@@ -17,7 +17,7 @@ If you have problems while troubleshooting, contact {{% support-platform %}}.
 
 ## Azure cloud provider configuration problems
 
-You can diagnose and remedy a failure that occurred when [configuring Azure cloud provider](../../configure-yugabyte-platform/azure/) as follows:
+You can diagnose and remedy a failure that occurred when [creating an Azure provider configuration](../../configure-yugabyte-platform/azure/) as follows:
 
 - Navigate to **Tasks** on the left-side menu.
 
diff --git a/docs/content/v2024.1/yugabyte-platform/configure-yugabyte-platform/kubernetes.md b/docs/content/v2024.1/yugabyte-platform/configure-yugabyte-platform/kubernetes.md
index 8d76aa6da12d..51afadf4e20e 100644
--- a/docs/content/v2024.1/yugabyte-platform/configure-yugabyte-platform/kubernetes.md
+++ b/docs/content/v2024.1/yugabyte-platform/configure-yugabyte-platform/kubernetes.md
@@ -425,7 +425,7 @@ Refer to [Multi-Region YugabyteDB Deployments on Kubernetes with Istio](https://
 
 ### Configure the cloud provider for MCS
 
-After you have the cluster set up, follow the instructions in [Configure the Kubernetes cloud provider](#provider-settings), and refer to this section for region and zone configuration required for multi-region universes.
+After you have the cluster set up, follow the instructions in [Create a provider](#create-a-provider), and refer to this section for region and zone configuration required for multi-region universes.
 
 #### Configure region and zone for GKE MCS
 
@@ -450,7 +450,7 @@ For example, if your cluster membership name is `yb-asia-south1`, then the **Add
 
 #### Configure region and zones for OpenShift MCS
 
-Follow the instructions in [Configure the OpenShift cloud provider](../openshift/) and [Create a provider](#create-a-provider). For all the zones from your OpenShift clusters connected via MCS (Submariner), add a region as follows:
+Follow the instructions in [Create OpenShift provider configuration](../openshift/) and [Create a provider](#create-a-provider). For all the zones from your OpenShift clusters connected via MCS (Submariner), add a region as follows:
 
 1. Specify fields such as Region, Zone, and so on as you would normally.
 1. Set the **Cluster DNS Domain** to `clusterset.local`.
diff --git a/docs/content/v2024.1/yugabyte-platform/create-deployments/create-universe-multi-cloud.md b/docs/content/v2024.1/yugabyte-platform/create-deployments/create-universe-multi-cloud.md
index 846e8632c035..eaa05245c596 100644
--- a/docs/content/v2024.1/yugabyte-platform/create-deployments/create-universe-multi-cloud.md
+++ b/docs/content/v2024.1/yugabyte-platform/create-deployments/create-universe-multi-cloud.md
@@ -23,7 +23,7 @@ To create a multi-cloud universe, you would need to do the following:
 * [Set up node instance virtual machines](#set-up-instance-vms) in each cloud (AWS, GCP, and Azure)
 * [Set up VPC peering](#set-up-vpc-peering) through a VPN tunnel across these 3 clouds
 * [Install YugabyteDB Anywhere](#install-yugabytedb-anywhere) on one of the nodes
-* [Configure the on-premises cloud provider](#configure-the-on-premises-cloud-provider)
+* [Configure the on-premises provider configuration](#configure-the-on-premises-provider-configuration)
 * [Create a universe](#create-a-universe) using the provider
 * [Run the TPC-C benchmark](#run-the-tpc-c-benchmark)
 
@@ -59,7 +59,7 @@ All public cloud providers enable VPN tunneling across VPCs and their subnet to
 
 Follow steps provided in [Install YugabyteDB Anywhere](../../install-yugabyte-platform/) to deploy YugabyteDB Anywhere on a new VM on one of your cloud providers. You will use this node to manage your YugabyteDB universe.
 
-## Configure the on-premises cloud provider
+## Configure the on-premises provider configuration
 
 To deploy a multi-cloud universe, you first need to create an on-premises provider configuration. Refer to [Create provider configuration](../../configure-yugabyte-platform/on-premises/) for more information.
 
diff --git a/docs/content/v2024.1/yugabyte-platform/prepare/server-nodes-software/_index.md b/docs/content/v2024.1/yugabyte-platform/prepare/server-nodes-software/_index.md
index 52af7252d809..ff9c0118f894 100644
--- a/docs/content/v2024.1/yugabyte-platform/prepare/server-nodes-software/_index.md
+++ b/docs/content/v2024.1/yugabyte-platform/prepare/server-nodes-software/_index.md
@@ -10,6 +10,7 @@ menu:
     parent: server-nodes
     weight: 20
 type: indexpage
+showRightNav: true
 ---
 
 The Linux OS and other software components on each database cluster node must meet the following minimum software requirements.
@@ -17,7 +18,7 @@ The Linux OS and other software components on each database cluster node must me
 Depending on the [provider type](../../yba-overview/#provider-configurations) and permissions you grant, you may have to install all of these requirements manually, or YugabyteDB Anywhere will install it all automatically.
 
 {{< warning title="Using disk encryption software with YugabyteDB" >}}
-If you are using third party disk encryption software, such as Vormetric or CipherTrust, the disk encryption service must be up and running on the node before starting any YugabyteDB services. If YugabyteDB processes start _before_ the encryption service, restarting an already encrypted node can result in data corruption.
+If you are using third party disk encryption software (such as Vormetric or CipherTrust), the disk encryption service must be up and running on the node before starting any YugabyteDB services. If YugabyteDB processes start _before_ the encryption service, restarting an already encrypted node can result in data corruption.
 
 To avoid problems, [pause the universe](../../manage-deployments/delete-universe/#pause-a-universe) _before_ enabling or disabling the disk encryption service on universe nodes.
 {{< /warning >}}
diff --git a/docs/content/v2024.1/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md b/docs/content/v2024.1/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md
index 29f4ca0cf92c..034930580eb0 100644
--- a/docs/content/v2024.1/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md
+++ b/docs/content/v2024.1/yugabyte-platform/prepare/server-nodes-software/software-cloud-provider.md
@@ -41,9 +41,9 @@ Take the time now to prepare the Linux disk image.
 
 | Save for later | To configure |
 | :--- | :--- |
-| SSH-enabled, root-privileged user name | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| Disk image IDs | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged user name | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| Disk image IDs | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
 
 ## Custom Linux version without Internet connectivity
 
@@ -60,6 +60,6 @@ Take the time now to prepare the Linux disk image.
 
 | Save for later | To configure |
 | :--- | :--- |
-| SSH-enabled, root-privileged user name | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
-| Disk image IDs | [Cloud provider](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged user name | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| SSH-enabled, root-privileged Private Key Content PEM file | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
+| Disk image IDs | [Cloud provider configuration](../../../configure-yugabyte-platform/aws/) |
diff --git a/docs/content/v2024.1/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md b/docs/content/v2024.1/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md
index 9e0dceb10cae..87a3e28cd0c0 100644
--- a/docs/content/v2024.1/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md
+++ b/docs/content/v2024.1/yugabyte-platform/troubleshoot/cloud-provider-config-issues.md
@@ -17,7 +17,7 @@ If you have problems while troubleshooting, contact {{% support-platform %}}.
 
 ## Azure cloud provider configuration problems
 
-You can diagnose and remedy a failure that occurred when [configuring Azure cloud provider](../../configure-yugabyte-platform/azure/) as follows:
+You can diagnose and remedy a failure that occurred when [creating an Azure provider configuration](../../configure-yugabyte-platform/azure/) as follows:
 
 - Navigate to **Tasks** on the left-side menu.