Apply suggestions from code review

Internal review feedback

Co-authored-by: Ashley Brown <[email protected]>

Author: nvillahermosa-mdb

source/includes/fact-data-prep-oracle-step1.rst

@@ -17,10 +17,10 @@ a. Create a service account:
 
       CREATE USER '<user>'@'localhost' IDENTIFIED BY '<password>';
 
-#. Check if the service account owns the tables in the migration job.
+#. Confirm that the service account owns the tables in the migration job.
 
    Required permissions depend on whether the service account owns the tables
-   used in the migration job. To check table ownership run the following query:
+   used in the migration job. To check table ownership, run the following query:
 
    .. code-block:: sql
       :copyable: true
@@ -35,7 +35,7 @@ a. Create a service account:
    .. important::
 
       If you're migrating a multi-tenant container database as a
-      common user, append ``CONTAINER=ALL`` when granting permissions, for
+      common user, append ``CONTAINER=ALL`` when granting permissions. For
       example:
 
       .. code-block:: sql

source/includes/fact-short-sync-job-desc.rst

@@ -1,3 +1,3 @@
-- Snapshot migration jobs migrate all data, then stop.
-- Continuous migration job run a snapshot and then enter a CDC stage to 
-  continuously replicate data changes.
+- Snapshot migration jobs migrate all data once, and then stop.
+- Continuous migration jobs run a snapshot migration and then enter a CDC stage, which 
+  continuously replicates data changes.

source/jobs/prerequisites/oracle.txt

@@ -10,11 +10,11 @@ Configure Migration Prerequisites for Oracle
    :depth: 1
    :class: singlecol
 
-When migrating data from an Oracle source database, the database may require 
+When you migrate data from an Oracle source database, that database may require 
 configuration changes. If Relational Migrator determines the 
 database needs configuration changes, it automatically generates a 
 SQL script with the required changes. Have a Database Administrator (DBA)
-review the script, then have them run the commands on the database server. 
+review the script and run the commands on the database server. 
 
 Oracle configuration depends on the type of migration job:
 
@@ -28,15 +28,15 @@ About this Task
 
 - If you're migrating from an Oracle 12c instance, you must run commands as 
   the SYSDBA role.
-- Oracle 12c introduced the concept of a pluggable database. Some
+- Oracle 12c introduced the concept of a pluggable database (PDB). Some
   of these commands can be run on a PDB (pluggable database), while commands 
-  such as enabling ``ARCHIVELOG`` must be run on the
-  CDB (container/master database). For details on each architecture, 
+  like enabling ``ARCHIVELOG`` must be run on the
+  container/master database (CDB). For details on each architecture, 
   see `Overview of Container Databases and Pluggable Databases
   <https://oracle-base.com/articles/12c/multitenant-overview-container-database-cdb-12cr1>`__.
 - Some commands differ based on whether the database is single or
   multi-tenant. In a multi-tenant database, permissions must
-  include the suffix ``CONTAINER=ALL``
+  include the suffix ``CONTAINER=ALL``.
 - Oracle Express editions don't support logging the necessary information for
   continuous migration jobs, so you can't run continuous migration against an
   Oracle XE database.
@@ -98,7 +98,7 @@ Steps
 
          .. step:: Turn on archive logging
 
-            a. To check if archive logging is already enabled, run the following query:
+            a. To see if archive logging is already enabled, run the following query:
 
                .. code-block:: sql
                   :copyable: true
@@ -108,10 +108,10 @@ Steps
                This outputs ``ARCHIVELOG`` if logging is enabled, or
                ``NOARCHIVELOG`` if it isn't.
 
-            #. Enable archive logging if it isn't already enabled.
+            #. If archive logging isn't already enabled,  enable it. 
 
                The following is an example of the code Relational Migrator
-               generates for enabling logging, which you can run manually by
+               The following code is an example. You can run it manually if you
                substituting your database name. If you're migrating a
                multi-tenant database, run these commands on the
                container/master database.
@@ -128,7 +128,7 @@ Steps
 
          .. step:: Enable supplemental logging
 
-            a. To run continuous migration jobs against Oracle, enable 
+            a. Enable 
                supplemental logging:
 
                .. code-block:: sql