Calling out that schemas must be specified for the migration

Author: gvasquezvargas

product_docs/docs/migration_toolkit/55/07_invoking_mtk/mtk_command_options_in_file/creating_txt_file.mdx

@@ -87,7 +87,7 @@ Where the content of the `example.options` file is:
 ```
 tables=TAB1
 dataOnly
-]```
+```
 
 Or you can place the options flag (-dataOnly in this case) in the command line after specifying the `-optionsFile`:
 

product_docs/docs/migration_toolkit/55/07_invoking_mtk/mtk_command_options_in_file/executing_migration_with_txt.mdx

@@ -16,6 +16,14 @@ After you have created the options file, execute the migration command by refere
 
 You can specify all options in the file, or use a mix of command line and options file to specify the migration parameters.
 
+## Provide the scope for the schema migration 
+
+You must specify the scope of the schemas to be migrated.
+
+-   If you want to migrate all schemas: Add the `-allSchemas` option in the command line or add `allSchemas` in your options file.
+
+-   If you want to specify one or several schemas: Specify the schemas you want to migrate in the command line with no preceding option. They have to be the last parameter in the command line.
+
 Here are some examples for specifying all options in the file:
 
 ## Migrate a schema with specific tables
@@ -40,7 +48,7 @@ Command line equivalent:
 
 ## Use Options File to exclude tables and include functions
 
-Options File can be used to separate table names from configuration options.
+The options file can be used to separate table names from configuration options.
 It may also contain comments to clarify why parameters are used.
 
 In this example we are excluding tables and including functions.
@@ -74,7 +82,7 @@ Command line equivalent:
 
 ## Offline migration
 
-Run offline migration with all schemas
+Run an offline migration with all schemas.
 
 Content of the `<example.options>` text file: