From a1a919c378b7a1c2cd8c5115484a31e5e0c69921 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Wed, 4 Sep 2024 16:03:26 +0200 Subject: [PATCH] Applied suggestion from Matt --- .../executing_migration_with_txt.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/mtk_command_options_in_file/executing_migration_with_txt.mdx b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/mtk_command_options_in_file/executing_migration_with_txt.mdx index f08916ddedc..0c9d94eb0b2 100644 --- a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/mtk_command_options_in_file/executing_migration_with_txt.mdx +++ b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/mtk_command_options_in_file/executing_migration_with_txt.mdx @@ -22,7 +22,7 @@ Specify the scope of the schemas to migrate: - If you want to migrate all schemas, add the `-allSchemas` option at the command line or add `allSchemas` in your options file. For both methods, this option must be the last parameter. -- If you want to specify one or several schemas, specify the schemas you want to migrate at the command line with no preceding option. Schema specifications must be the last parameter at the command line. +- If you want to specify a subset of schemas, specify the schemas you want to migrate at the command line with no preceding option and as a comma-separated list. Schema specifications must be the last parameter at the command line. Here are some examples for specifying all options in the file.