diff --git a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/on-premises-provider.md b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/on-premises-provider.md index 9161101a79ba..2702b54d4ea1 100644 --- a/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/on-premises-provider.md +++ b/docs/content/preview/yugabyte-platform/configure-yugabyte-platform/on-premises-provider.md @@ -68,7 +68,7 @@ For on-premises deployments, consider racks as zones to treat them as fault doma ### SSH Key Pairs -In the **SSH User** field, enter the name of the user that has SSH privileges on your instances. This is required because YBA needs SSH access to the nodes to provision them with YugabyteDB. Unless you plan to provision the database nodes manually, the SSH user needs to have password-free sudo permissions to complete a few tasks. +In the **SSH User** field, enter the name of the user that has SSH privileges on your instances. This is required because YBA needs SSH access to the nodes to provision them with YugabyteDB. This SSH user cannot be named yugabyte. Unless you plan to provision the database nodes manually, the SSH user needs to have password-free sudo permissions to complete a few tasks. If the SSH user requires a password for sudo access or the SSH user does not have sudo access, you must enable the **Manually Provision Nodes** option (under **Advanced**) and [manually provision the instances](../on-premises-script/). diff --git a/docs/content/preview/yugabyte-platform/manage-deployments/xcluster-replication/xcluster-replication-ddl.md b/docs/content/preview/yugabyte-platform/manage-deployments/xcluster-replication/xcluster-replication-ddl.md index 2aeeefb9a1d6..9251b67ca2da 100644 --- a/docs/content/preview/yugabyte-platform/manage-deployments/xcluster-replication/xcluster-replication-ddl.md +++ b/docs/content/preview/yugabyte-platform/manage-deployments/xcluster-replication/xcluster-replication-ddl.md @@ -60,7 +60,7 @@ Perform DDL operations in the order as shown in the following table. The order v | :-- | :----- | :----- | :----- | | CREATE TABLE | Execute on Source | Execute on Target | [Add table to replication](#add-a-table-to-replication) | | DROP TABLE | [Remove table from replication](#remove-a-table-from-replication) | Execute on Target | Execute on Source | -| CREATE INDEX | Execute on Source | Execute on Target | [Reconcile configuration](#reconcile-configuration) | +| CREATE INDEX | Execute on Source | Execute on Target | [Add table to replication](#add-a-table-to-replication) | | DROP INDEX | [Remove index table from replication](#remove-a-table-from-replication) | Execute on Target | Execute on Source | | ALTER TABLE or INDEX | Execute on Target | Execute on Source | No changes needed | diff --git a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/on-premises-provider.md b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/on-premises-provider.md index 54d3b1978788..0f510bbffc22 100644 --- a/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/on-premises-provider.md +++ b/docs/content/stable/yugabyte-platform/configure-yugabyte-platform/on-premises-provider.md @@ -68,7 +68,7 @@ For on-premises deployments, consider racks as zones to treat them as fault doma ### SSH Key Pairs -In the **SSH User** field, enter the name of the user that has SSH privileges on your instances. This is required because YBA needs SSH access to the nodes to provision them with YugabyteDB. Unless you plan to provision the database nodes manually, the SSH user needs to have password-free sudo permissions to complete a few tasks. +In the **SSH User** field, enter the name of the user that has SSH privileges on your instances. This is required because YBA needs SSH access to the nodes to provision them with YugabyteDB. This SSH user cannot be named yugabyte. Unless you plan to provision the database nodes manually, the SSH user needs to have password-free sudo permissions to complete a few tasks. If the SSH user requires a password for sudo access or the SSH user does not have sudo access, you must enable the **Manually Provision Nodes** option (under **Advanced**) and [manually provision the instances](../on-premises-script/).