Edits to MTK 55.10 release branch #6186

EnterpriseDB · Nov 25, 2024 · deae0d7 · deae0d7
1 parent 82aa7ee
commit deae0d7
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx
@@ -490,21 +490,21 @@ Specify each entry in the file on a separate line in a key=value pair. The left
 
 ### `-mapVirtualToRegular`
 
-Include the `-mapVirtualToRegular` option to migrate virtual, computed or generated columns in the source database to regular columns in the target database. 
+Include the `-mapVirtualToRegular` option to migrate virtual, computed, or generated columns in the source database to regular columns in the target database. 
 
-Turning virtual columns to regular columns is helpful when the expression used to compute the values in the source database column is not supported in the target database or cannot be translated into an expression supported by the target database. With this option, you can still migrate the column's values to the target, but the values will no longer be computed dynamically, as they are stored in a regular column.
+Turning virtual columns to regular columns is helpful when the expression used to compute the values in the source database column isn't supported in the target database or can't be translated into an expression supported by the target database. With this option, you can still migrate the column's values to the target, but the values will no longer be computed dynamically, as they're stored in a regular column.
 
 For schema migrations, including the option results in all virtual columns in the source database being migrated to regular columns in the target database.
 
 For data migrations, including the option extracts the computed values from all computed columns in the source database and inserts those values into regular columns in the target database.
 
-For example, in: 
+In the following example, a column `FullName` is computed from other two columns called `FirstName` and `LastName` in the source database. This column is migrated as a regular column called `FullName` in the target database.
 
 ```
 ./runMTK.sh -sourcedbtype sqlserver -targetdbtype enterprisedb -mapVirtualToRegular -allTables <schema_scope>
 ```
 
-A column called `FullName` that is computed from other two columns called `FirstName` and `LastName` in the source database, is migrated as a regular column called `FullName` in the target database. In the target, this column is no longer dynamically generated, but displays the `FullName` value the source database had at the time the migration was performed.
+In the target, this column is no longer dynamically generated, but displays the `FullName` value the source database had at the time the migration was performed.
 
 ## Connection retry options
 

diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_55100_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_55100_rel_notes.mdx
@@ -12,6 +12,6 @@ New features, enhancements, bug fixes, and other changes in Migration Toolkit 55
 | Enhancement  | Migration Toolkit now supports PostgreSQL version 17 and EDB Postgres Advanced Server version 17 both as a source and target database.                                                                                                                                                                                                                               |        |
 | Enhancement  | Improved the handling and consistency in migrating virtual columns across different source and target database combinations. <br/> You can now choose whether to migrate virtual columns as virtual columns or map them to regular columns in the target. See [mapVirtualToRegular](../07_invoking_mtk/08_mtk_command_options/#-mapvirtualtoregular) for more information. | #38897 |
 | Bug&nbsp;fix | Fixed an issue that caused synonyms from all source schemas to be migrated even when only one schema was selected for migration.                                                                                                                                                                                                                                     | #41178 |
-| Bug&nbsp;fix | Fixed an issue where the MySQL column type `BIGINT AUTO_INCREMENT` is not mapped to the `BIGSERIAL` column type in the target PostgreSQL/EDB Postgres Advanced Server table.                                                                                                                                                                                         |        |
+| Bug&nbsp;fix | Fixed an issue where the MySQL column type `BIGINT AUTO_INCREMENT` isn't mapped to the `BIGSERIAL` column type in the target PostgreSQL/EDB Postgres Advanced Server table.                                                                                                                                                                                         |        |
 | Bug&nbsp;fix | Fixed the issue where migration fails in parallel mode for a table with a primary key based on the float data type.                                                                                                                                                                                                                                                  |        |
 | Bug&nbsp;fix | Fixed an issue where the indexes are skipped from migration when multiple tables are selected for a source MySQL database.                                                                                                                                                                                                                                           |        |