Merge pull request #14511 from MicrosoftDocs/FromPublicRepo

Confirm merge from FromPublicRepo to master to sync with https://github.com/MicrosoftDocs/sql-docs (branch live)

Author: huypub

docs/linux/sql-server-linux-setup-language-extensions.md

@@ -48,9 +48,9 @@ Commands for removing packages appear in the following table.
 
 | Platform	| Package removal command(s) | 
 |-----------|----------------------------|
-| RHEL	| `sudo yum remove msssql-server-extensibility-java` |
-| SLES	| `sudo zypper remove msssql-server-extensibility-java` |
-| Ubuntu	| `sudo apt-get remove msssql-server-extensibility-java`|
+| RHEL	| `sudo yum remove mssql-server-extensibility-java` |
+| SLES	| `sudo zypper remove mssql-server-extensibility-java` |
+| Ubuntu	| `sudo apt-get remove mssql-server-extensibility-java`|
 
 ### 3. Install SQL Server 2019
 
@@ -304,4 +304,4 @@ There is parity between Linux and Windows for [Resource governance](../t-sql/sta
 
 Java developers can get started with some simple examples, and learn the basics of how Java works with SQL Server. For your next step, see the following links:
 
-+ [Tutorial: Regular expressions with Java](../language-extensions/tutorials/search-for-string-using-regular-expressions-in-java.md)
++ [Tutorial: Regular expressions with Java](../language-extensions/tutorials/search-for-string-using-regular-expressions-in-java.md)

docs/relational-databases/tables/creating-a-system-versioned-temporal-table.md

@@ -128,7 +128,7 @@ For example, you may have a set of tables where versioning is implemented with t
 - Better DML performance
 - Minimal maintenance costs
 
- When converting an existing table, consider using the **HIDDEN** clause to hide the new **PERIOD** columns (the datetime2 columns **SysStartTime** and **SysEndTime**) to avoid impacting existing applications that are not designed to handle new columns.
+ When converting an existing table, consider using the **HIDDEN** clause to hide the new **PERIOD** columns (the datetime2 columns **SysStartTime** and **SysEndTime**) to avoid impacting existing applications that do not explicitly specify column names (e.g. SELECT * or INSERT without column list) are not designed to handle new columns.
 
 ### Adding versioning to non-temporal tables
 

docs/t-sql/statements/create-table-transact-sql.md

@@ -390,7 +390,7 @@ Indicates that the **text**, **ntext**, **image**, **xml**, **varchar(max)**, **
 `TEXTIMAGE_ON` is not allowed if there are no large value columns in the table. `TEXTIMAGE_ON` cannot be specified if *partition_scheme* is specified. If **"default"** is specified, or if `TEXTIMAGE_ON` is not specified at all, the large value columns are stored in the default filegroup. The storage of any large value column data specified in `CREATE TABLE` cannot be subsequently altered.
 
 > [!NOTE]
-> Varchar(max), nvarchar(max), varbinary(max), xml and large UDT values are stored directly in the data row, up to a limit of 8,000 bytes and as long as the value can fit the record. If the value does not fit in the record, a pointer is sorted in-row and the rest is stored out of row in the LOB storage space. 0 is the default value, which indicates that all values are stored directly in the data row.
+> Varchar(max), nvarchar(max), varbinary(max), xml and large UDT values are stored directly in the data row, up to a limit of 8,000 bytes and as long as the value can fit the record. If the value does not fit in the record, a pointer is stored in-row and the rest is stored out of row in the LOB storage space. 0 is the default value, which indicates that all values are stored directly in the data row.
 >
 > `TEXTIMAGE_ON` only changes the location of the "LOB storage space", it does not affect when data is stored in-row. Use large value types out of row option of sp_tableoption to store the entire LOB value out of the row.
 >