Merge pull request #6297 from EnterpriseDB/docs/edits_to_migport_pr6259

Edits to Mig Portal: DDL Extractor note and reorg of extraction secti…

product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/edb_ddl_extractor.mdx

@@ -7,7 +7,7 @@ navTitle: Using EDB DDL Extractor
 Download the latest EDB DDL Extractor script from the Migration Portal Projects page.
 
 !!! Note
-    Migration Portal might become unresponsive for very large SQL files, depending on your system and browser resource availability. To resolve this, try extracting fewer schemas at a time to reduce the SQL file size.
+    Migration Portal might become unresponsive for very large SQL files, depending on your system and browser resource availability. To resolve this issue, try extracting fewer schemas at a time to reduce the SQL file size.
 
 ## Prerequisites
 
@@ -24,18 +24,20 @@ You can run the EDB DDL Extractor script in SQL Developer or SQL\*Plus. It uses
     @edb_ddl_extractor.sql
     ```
 
-1.  When prompted, if the Oracle user that is running the script has the required privileges, press **Enter** to continue running the script. 
+    The script prompts you to provide the details described in the steps that follow.
 
-1.  When prompted, provide the schema name. When extracting multiple schemas, use a comma (`‘,’`) as a delimiter.
+1.  If the Oracle user that's running the script has the required privileges, press **Enter** to continue running the script. 
+
+1.  Provide the schema name. When extracting multiple schemas, use a comma (`‘,’`) as a delimiter.
 
  !!! Note
      If you want to extract all the user schemas from the current database, don't mention any schema names while extracting. However, we recommend mentioning the schema names that you want to extract.
 
-1.  When prompted, enter the path or directory for the extractor to store the extracted DDL. If you don't specify a path, the extracted DDL is output to the directory where you ran the SQL\*Plus command.
+1.  Enter the path or directory for the extractor to store the extracted DDL. If you don't specify a path, the extracted DDL is output to the directory where you ran the SQL\*Plus command.
 
-1.  When prompted, enter `yes`or `no` depending on whether you want to extract dependent objects from other schemas.
+1.  Enter `yes` to extract dependent objects from other schemas or `no` if you don't want to extract them.
 
-1.  When prompted, enter `yes`or `no` depending on whether you want to extract grant statements from other schemas.
+1.  Enter `yes` to extract grant statements from other schemas or `no` if you don't want to want to extract them.
 
 ## Example
 
@@ -91,21 +93,19 @@ After loading the `edb_ddl_extractor.sql` script into SQL Developer and connecti
 
 1.  If the user for the database connection has the required privileges as listed in the **Script Output** tab, select **Yes** to continue running the script.
 
-2.  Enter a comma-separated list of schemas, and select **OK**. 
+2.  Enter a comma-separated list of schemas, and select **OK**.
 
 3.  Enter the path for the output file, and select **OK**. The default is the location of the DDL Extractor script.
 
-4.  Enter `yes` or `no` to extract dependent objects, and select **OK**. The default is to not extract dependent objects. 
+4.  Enter `yes` or `no` to extract dependent objects, and select **OK**. The default is not to extract dependent objects. 
 
-5. Enter `yes` or `no` to extract grant statements, and select **OK**. The default setting is not to extract grant statements.
+5. Enter `yes` or `no` to extract grant statements, and select **OK**. The default is not to extract grant statements.
 
 Output of the DDL Extractor run appears in the Script Output tab. The name of the output file appears after the `Extraction Completed` message in the script output.
 
 !!! Note
     You can also enter single schema name in both SQL\*Plus and SQL Developer.
 
-The script then iterates through the object types in the source database. Once the task is completed, the `.SQL` output is stored at the location you entered (e.g., `c:\Users\Example\Desktop\`).
-
-See [file encoding](/migration_portal/latest/known_issues_notes/#file-encoding) for information about the file encoding format expected by Migration Portal.
-
+The script then iterates through the object types in the source database. After the task is completed, the `.SQL` output is stored at the location you entered (for example, `c:\Users\Example\Desktop\`).
 
+See [File encoding](/migration_portal/latest/known_issues_notes/#file-encoding) for information about the file encoding format Migration Portal expects.

product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx

@@ -15,7 +15,7 @@ navigation:
 
 ## Schema extraction methods
 
-You can perform a schema extraction using the EDB or Oracle extraction tools.Select one of the following for instructions and examples:
+You can perform a schema extraction using the EDB or Oracle extraction tools. For instructions and examples, see:
 
  -  [EDB DDL Extractor](edb_ddl_extractor) (recommended method)
  -  [Oracle Data Pump utilities](01_data_pump_utility/)