Update values for the project setting

Author: nahk-ivanov

docs/ssma/db2/messages/db22ss0028.md

@@ -69,7 +69,7 @@ When you try to convert this trigger in SSMA, the following T-SQL will be produc
 
 ## Additional information
 
-This behavior is controlled by the **Generate ROWID column** project setting, which can be found under **Tools** - **Project Settings** - **General** - **Conversion** - **ROWID generation**. If the setting is **Off**, but during trigger conversion SSMA identifies that it requires a `ROWID` column, then [DB22SS0239](db22ss0239.md) conversion error will be generated.
+This behavior is controlled by the **Generate ROWID column** project setting, which can be found under **Tools** - **Project Settings** - **General** - **Conversion** - **ROWID generation**. If the setting is **No**, but during trigger conversion SSMA identifies that it requires a `ROWID` column, then [DB22SS0239](db22ss0239.md) conversion error will be generated.
 
 ## Related conversion messages
 

docs/ssma/db2/messages/db22ss0239.md

@@ -18,7 +18,7 @@ This article describes the reason why SQL Server Migration Assistant (SSMA) for
 
 In DB2 you can create a trigger that will run `FOR EACH ROW`, rather than for the entire set of rows that is changing. In SQL Server triggers always execute for the entire set of modified rows. If row-level DB2 trigger accesses both - `OLD` and `NEW` correlation names, then SSMA needs a way to match rows from both row sets in order to identify what the value was for a given row before and after the update. To emulate such "for each row" functionality, SSMA adds special `ROWID` column to uniquely identify each modified row and uses it to establish a relationship between `inserted` and `deleted` row sets.
 
-This behavior is controlled by the **Generate ROWID column** project setting, which can be found under **Tools** - **Project Settings** - **General** - **Conversion** - **ROWID generation**. If the setting is **Off**, then `ROWID` column will not be added to the table and SSMA will not be able to convert such triggers.
+This behavior is controlled by the **Generate ROWID column** project setting, which can be found under **Tools** - **Project Settings** - **General** - **Conversion** - **ROWID generation**. If the setting is set to **No**, then `ROWID` column will not be added to the table and SSMA will not be able to convert such triggers.
 
 ## Example
 
@@ -37,13 +37,13 @@ BEGIN ATOMIC
 END
 ```
 
-When you try to convert this trigger in SSMA, if the **Generate ROWID column** project setting is **Off**, then SSMA will generate the following error message:
+When you try to convert this trigger in SSMA, if the **Generate ROWID column** project setting is set to **No**, then SSMA will generate the following error message:
 
 > DB22SS0239: ROWID column not accessible
 
 ## Possible remedies
 
-Change the **Generate ROWID column** project setting to **On**, this will allow SSMA to produce the following T-SQL within the SQL Server trigger when converting the above example:
+Change the **Generate ROWID column** project setting to **Add ROWID column for tables with triggers**, this will allow SSMA to produce the following T-SQL within the SQL Server trigger when converting the above example:
 
 1) Run a cursor over `inserted` row set, selecting `ROWID` and `DATA` columns into `@new$0` and `@new$DATA` variables:
 

docs/ssma/oracle/messages/o2ss0028.md

@@ -67,7 +67,7 @@ When you try to convert this trigger in SSMA, the following T-SQL will be produc
 
 ## Additional information
 
-This behavior is controlled by the **Generate ROWID column** project setting, which can be found under **Tools** - **Project Settings** - **General** - **Conversion** - **ROWID generation**. If the setting is **Off**, but during trigger conversion SSMA identifies that it requires a `ROWID` column, then [O2SS0239](o2ss0239.md) conversion error will be generated.
+This behavior is controlled by the **Generate ROWID column** project setting, which can be found under **Tools** - **Project Settings** - **General** - **Conversion** - **ROWID generation**. If the setting is set to **No**, but during trigger conversion SSMA identifies that it requires a `ROWID` column, then [O2SS0239](o2ss0239.md) conversion error will be generated.
 
 ## Related conversion messages
 

docs/ssma/oracle/messages/o2ss0239.md

@@ -18,7 +18,7 @@ This article describes the reason why SQL Server Migration Assistant (SSMA) for
 
 In Oracle you can create a trigger that will run `FOR EACH ROW`, rather than for the entire set of rows that is changing. In SQL Server triggers always execute for the entire set of modified rows. If row-level Oracle trigger accesses both - `:old` and `:new` special variables, then SSMA needs a way to match rows from both row sets in order to identify what the value was for a given row before and after the update. To emulate such "for each row" functionality, SSMA adds special `ROWID` column to uniquely identify each modified row and uses it to establish a relationship between `inserted` and `deleted` row sets.
 
-This behavior is controlled by the **Generate ROWID column** project setting, which can be found under **Tools** - **Project Settings** - **General** - **Conversion** - **ROWID generation**. If the setting is **Off**, then `ROWID` column will not be added to the table and SSMA will not be able to convert such triggers.
+This behavior is controlled by the **Generate ROWID column** project setting, which can be found under **Tools** - **Project Settings** - **General** - **Conversion** - **ROWID generation**. If the setting is set to **No**, then `ROWID` column will not be added to the table and SSMA will not be able to convert such triggers.
 
 ## Example
 
@@ -35,13 +35,13 @@ BEGIN
 END;
 ```
 
-When you try to convert this trigger in SSMA, if the **Generate ROWID column** project setting is **Off**, then SSMA will generate the following error message:
+When you try to convert this trigger in SSMA, if the **Generate ROWID column** project setting is set to **No**, then SSMA will generate the following error message:
 
 > O2SS0239: ROWID column not accessible
 
 ## Possible remedies
 
-Change the **Generate ROWID column** project setting to **On**, this will allow SSMA to produce the following T-SQL within the SQL Server trigger when converting the above example:
+Change the **Generate ROWID column** project setting to **Add ROWID column for tables with triggers**, this will allow SSMA to produce the following T-SQL within the SQL Server trigger when converting the above example:
 
 1) Run a cursor over `inserted` row set, selecting `ROWID` and `DATA` columns into `@new$0` and `@new$DATA` variables: