minor formatting fixes

Author: rao-shwe

modules/install/pages/install-linux.adoc

@@ -8,16 +8,16 @@
 
 Couchbase Server can be installed and run on Red Hat-based distributions, Oracle Enterprise, Amazon Linux, Ubuntu, Debian, and SUSE Enterprise.
 
-The following procedures use Couchbase packages, and require the user who performs the install to have _root_ or _sudo_ privileges:
+The following procedures use Couchbase packages, and require the user who performs the install to have root or sudo privileges:
 
 * xref:install:rhel-suse-install-intro.adoc[Install on Red Hat-based distributions, Oracle Linux, or Amazon Linux].
 
 * xref:install:ubuntu-debian-install.adoc[Install on Ubuntu and Debian].
 
 * xref:install:install_suse.adoc[Install on SUSE Enterprise].
 
-Additionally, a _non-package-based_ install is performed on all the above platforms.
-Unlike the package-based install, this does _not_ require root or sudo privileges.
+Additionally, a non-package-based install is performed on all the above platforms.
+Unlike the package-based install, this does not require root or sudo privileges.
 After the non-package-based install, the same user can stop, start, and get status on the server; and can also perform upgrade.
 
-The non-package-based procedure is the same for all the above platforms: see xref:install:non-root.adoc[Non-Root Install and Upgrade] for detailed information.
+The non-package-based procedure is the same for all the above platforms: see xref:install:non-root.adoc[Non-Root Install and Upgrade] for detailed information.

modules/install/pages/migration.adoc

@@ -26,7 +26,7 @@ Cluster 1 (Bucket A) and Cluster 2 (Bucket A’) replicate data into each other.
 
 == Migration during Unidirectional Replication
 
-Follow these steps to migrate your data to a new cluster during unidirectional replication:
+Follow these steps to migrate your data to a new bucket during unidirectional replication:
 
 . Stop application traffic coming into Cluster 1 (Bucket A).
 +
@@ -38,31 +38,31 @@ For more information, see xref:manage:monitor/monitor-intro.html#monitoring-with
 For instructions, see
 xref:manage:manage-xdcr/xdcr-management-overview.adoc[XDCR Management Overview].
 
-. Run the `cbbackupmgr` tool to back up the entire bucket’s (Bucket A) data.
+. Run the `cbbackupmgr` tool to back up the bucket’s (Bucket A) data.
 For instructions, see xref:backup-restore:enterprise-backup-restore.adoc[Backup].
 
 . Delete Bucket A from Cluster 1.
 For instructions, see
 xref:manage:manage-buckets/delete-bucket.adoc[Delete a Bucket].
 
-. Create Bucket B and select the Timestamp-based Conflict Resolution type.
+. Create Bucket B on Cluster 1 and select the Timestamp-based Conflict Resolution type.
 For instructions, see
 xref:manage:manage-buckets/create-bucket.adoc[Create a Bucket].
 
-. Run the `cbbackupmgr` tool to restore data.
-When restoring data from a backup, disable the Conflict Resolution setting on the destination cluster and then use the `--force-updates` option.
+. Run the `cbbackupmgr` tool on Cluster 1 to restore data to Bucket B.
+Turn off the Conflict Resolution setting on the destination cluster and then use the `--force-updates` option to restore data from backup.
 Do this because the source and destination clusters have different conflict resolution types.
 
-. After the restore operation is complete on Cluster 1, delete Bucket A’ from Cluster 2.
+. After the data restore operation is complete on Cluster 1, delete Bucket A’ from Cluster 2.
 
-. Create Bucket B’ and select the Timestamp-based Conflict Resolution type.
+. Create Bucket B’ on Cluster 2 and select the Timestamp-based Conflict Resolution type.
 
 . Create a new unidirectional replication for Bucket B.
 See xref:manage:manage-xdcr/xdcr-management-overview.adoc[XDCR Management Overview].
 
 == Migration during Bidirectional Replication
 
-Follow these steps to migrate your data to a new cluster during bidirectional replication:
+Follow these steps to migrate your data to a new bucket during bidirectional replication:
 
 . Stop application traffic coming into Cluster 1 (Bucket A) and Cluster 2 (Bucket A’).
 +
@@ -74,7 +74,7 @@ For more information, see xref:manage:monitor/monitor-intro.html#monitoring-with
 For instructions, see
 xref:manage:manage-xdcr/xdcr-management-overview.adoc[XDCR Management Overview].
 
-. Run the `cbbackupmgr` tool on both clusters to backup the entire bucket data.
+. Run the `cbbackupmgr` tool on both clusters to backup the bucket data.
 For instructions, see
 xref:backup-restore:enterprise-backup-restore.adoc[Backup].
 
@@ -86,7 +86,7 @@ xref:manage:manage-buckets/delete-bucket.adoc[Delete a Bucket].
 For instructions, see xref:manage:manage-buckets/create-bucket.adoc[Create a Bucket].
 
 . Run the `cbbackupmgr` tool to restore data.
-When restoring data from a backup, disable the Conflict Resolution setting on the destination cluster and then use the `--force-updates` option.
+Turn off the Conflict Resolution setting on the destination cluster and then use the `--force-updates` option to restore data from backup.
 Do this because the source and destination clusters have different conflict resolution types.
 
 . After the restore operation is complete on both clusters, create replication streams both ways between Cluster 1 and Cluster 2.

modules/install/pages/rhel-suse-install-intro.adoc

@@ -63,6 +63,9 @@ Enterprise::
 +
 --
 .To install the latest release
+
+Run the following command:
+
 [source,console]
 ----
 sudo yum install couchbase-server
@@ -71,6 +74,7 @@ You'll be prompted to start the download of Couchbase Server (plus any dependenc
 For each of these prompts, type `y` to accept and continue.
 
 .To install a specific release
+
 . List the available releases.
 +
 [source,console]
@@ -86,6 +90,7 @@ couchbase-server.x86_64 <version_number>-<build_number>
 ----
 +
 The following is an example of the listing:
++
 [subs=+quotes]
 ----
 couchbase-server.x86_64 *8.0.0-3777*
@@ -113,6 +118,9 @@ Community::
 +
 --
 .To install the latest release
+
+Run the following command:
+
 [source,console]
 ----
 sudo yum install couchbase-server-community
@@ -121,6 +129,7 @@ You'll be prompted to start the download of Couchbase Server and its dependencie
 For each of these prompts, type `y` to accept and continue.
 
 .To install a specific release
+
 . List the available releases.
 +
 [source,console]
@@ -136,6 +145,7 @@ couchbase-server-community.x86_64 <version_number>-<build_number>
 ----
 +
 The following is an example of the listing:
++
 [subs=+quotes]
 ----
 couchbase-server-community.x86_64 *8.0.0-3777*
@@ -164,7 +174,7 @@ After the installation is complete, Couchbase Server starts automatically.
 Couchbase Server continues to start automatically at run levels 2, 3, 4, and 5, and explicitly shuts down at run levels 0, 1, and 6.
 You can use the `systemctl` command, a `service` on older operating systems, to start and stop the Couchbase Server service, and to verify the current status.
 For more information, see xref:startup-shutdown.adoc[Couchbase Server Startup and Shutdown].
-+
+
 . Open the Couchbase Web Console in a browser to xref:testing.adoc[verify] that the installation was successful and that the node is available.
 
 === Install Using RPM Package