Internal and external review feedback

Author: nvillahermosa-mdb

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

@@ -6,9 +6,8 @@ the appropriate permissions.
 
 .. tip::
 
-   To migrate data from a multi-tenant container database, use a `Common
-   User
-   <https://oracle-base.com/articles/12c/multitenant-manage-users-and-privileges-for-cdb-and-pdb-12cr1>`__.
+   To migrate data from a multi-tenant container database, `create tablespaces
+   and a Common User <https://oracle-base.com/articles/12c/multitenant-manage-users-and-privileges-for-cdb-and-pdb-12cr1>`__.
 
 a. Create a service account:
 

source/jobs/prerequisites/oracle.txt

@@ -10,11 +10,10 @@ Configure Migration Prerequisites for Oracle
    :depth: 1
    :class: singlecol
 
-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 and run the commands on the database server. 
+When you migrate data from an Oracle source database, Relational Migrator 
+automatically checks your database for needed configuration changes and 
+generates a SQL script to implement them. Have a Database Administrator (DBA)
+review the script and run the commands on the database server.
 
 Oracle configuration depends on the type of migration job:
 
@@ -29,17 +28,14 @@ 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 (PDB). Some
-  of these commands can be run on a PDB (pluggable database), while commands 
-  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>`__.
+  commands can be run on a PDB, while commands 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``.
-- 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.
+- You can't run a continuous migration job against Oracle Database Express 
+  Edition (XE), because XE doesn't support the necessary logs.
 
 Steps
 -----
@@ -110,11 +106,10 @@ Steps
 
             #. If archive logging isn't already enabled,  enable it. 
 
-               The following is an example of the code Relational Migrator
-               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.
+               Relational Migrator can automatically generate code to enable
+               logging. The following code is an example. If you're migrating a
+               multi-tenant database, run these commands on the container/
+               master database.
 
                .. code-block:: sql
                   :copyable: true
@@ -128,16 +123,14 @@ Steps
 
          .. step:: Enable supplemental logging
 
-            a. Enable 
-               supplemental logging:
+            a. Enable supplemental logging:
 
                .. code-block:: sql
                   :copyable: true
 
                   ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; 
 
-            #. You must also enable supplemental logging for every 
-               table in the migration:
+            #. Enable supplemental logging for every table in the migration:
 
                .. code-block:: sql
                   :copyable: true