Merge pull request #25677 from MicrosoftDocs/FromPublicRepo

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

Author: huypub

azure-sql/database/service-tiers-sql-database-vcore.md

@@ -41,7 +41,7 @@ The vCore purchasing model used by Azure SQL Database provides several benefits
 
 ## Service tiers
 
-Service tier options in the vCore purchasing model include General Purpose, Business Critical, and Hyperscale. The service tier generally service tier defines hardware, storage type and IOPS, high availability and disaster recovery options, and other features like memory optimized object types.
+Service tier options in the vCore purchasing model include General Purpose, Business Critical, and Hyperscale. The service tier generally defines hardware, storage type and IOPS, high availability and disaster recovery options, and other features like memory optimized object types.
 
 For greater details, review resource limits for [logical server](resource-limits-logical-server.md), [single databases](resource-limits-vcore-single-databases.md), and [pooled databases](resource-limits-vcore-elastic-pools.md). 
 

azure-sql/managed-instance/log-replay-service-overview.md

@@ -125,7 +125,7 @@ You start the migration by starting LRS. You can start the service in either aut
 
   We recommend using autocomplete mode for passive workloads for which data catch-up isn't required.
 
-* **Autocomplete mode**. When you use continuous mode, the service continuously scans the Azure Blob Storage folder and restores any new backup files that are added while the migration is in progress. 
+* **Continuous mode**. When you use continuous mode, the service continuously scans the Azure Blob Storage folder and restores any new backup files that are added while the migration is in progress. 
 
   The migration finishes only after the manual cutover has been requested. 
 

docs/relational-databases/security/encryption/transparent-data-encryption.md

@@ -101,9 +101,9 @@ The following example shows encryption and decryption of the `AdventureWorks2012
 USE master;
 GO
 CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<UseStrongPasswordHere>';
-go
+GO
 CREATE CERTIFICATE MyServerCert WITH SUBJECT = 'My DEK Certificate';
-go
+GO
 USE AdventureWorks2012;
 GO
 CREATE DATABASE ENCRYPTION KEY
@@ -348,4 +348,4 @@ If the column `pvt_key_last_backup_date` is NULL, the database corresponding to
 - [Security Center for SQL Server Database Engine and Azure SQL Database](../../../relational-databases/security/security-center-for-sql-server-database-engine-and-azure-sql-database.md)
 - [FILESTREAM (SQL Server)](../../../relational-databases/blob/filestream-sql-server.md)
 - [SQL Server Encryption](../../../relational-databases/security/encryption/sql-server-encryption.md)
-- [SQL Server and Database Encryption Keys (Database Engine)](../../../relational-databases/security/encryption/sql-server-and-database-encryption-keys-database-engine.md)
+- [SQL Server and Database Encryption Keys (Database Engine)](../../../relational-databases/security/encryption/sql-server-and-database-encryption-keys-database-engine.md)

docs/relational-databases/security/ledger/ledger-how-to-configure-ledger-database.md

@@ -30,6 +30,9 @@ This article provides information on configuring a [ledger database](ledger-over
 
 ## Enable ledger database
 
+> [!NOTE]
+> Enabling the ledger functionality at the database level will make all tables in this database updatable ledger tables. This option cannot be changed after the database is created. Creating a table with the option `LEDGER = OFF` will throw an error message.
+
 # [Portal](#tab/Portal)
 
 1. Open the [Azure portal](https://portal.azure.com/) and [create an Azure SQL Database](/azure/azure-sql/database/single-database-create-quickstart?tabs=azure-portal) .

docs/relational-databases/security/ledger/ledger-verify-database.md

@@ -118,6 +118,8 @@ In this article, you'll verify the integrity of the data in your ledger tables.
 
    > [!TIP]
    > Running ledger verification with the latest digest will only verify the database from the time the digest was generated until the time the verification was run. To verify that the historical data in your database wasn't tampered with, run verification by using multiple database digest files. Start with the point in time for which you want to verify the database. An example of a verification passing multiple digests would look similar to the following query.
+   >
+   > **SNAPSHOT ISOLATION** should be enabled before running the verification procedure `sp_verify_database_ledger`.
 
    ```sql
    EXECUTE sp_verify_database_ledger N'
@@ -150,4 +152,4 @@ In this article, you'll verify the integrity of the data in your ledger tables.
 - [sys.database_ledger_digest_locations](../../system-catalog-views/sys-database-ledger-digest-locations-transact-sql.md)
 - [sp_verify_database_ledger_from_digest_storage](../../system-stored-procedures/sys-sp-verify-database-ledger-from-digest-storage-transact-sql.md)
 - [sp_verify_database_ledger](../../system-stored-procedures/sys-sp-verify-database-ledger-transact-sql.md)
-- [sp_generate_database_ledger_digest](../../system-stored-procedures/sys-sp-generate-database-ledger-digest-transact-sql.md)
+- [sp_generate_database_ledger_digest](../../system-stored-procedures/sys-sp-generate-database-ledger-digest-transact-sql.md)

docs/t-sql/functions/cryptographic-functions-transact-sql.md

@@ -102,15 +102,15 @@ These functions support digital signing, digital signature validation, encryptio
         [SIGNBYASYMKEY](../../t-sql/functions/signbyasymkey-transact-sql.md)
     :::column-end:::
     :::column:::
-        [VERIFYSIGNEDBYASMKEY](../../t-sql/functions/verifysignedbyasymkey-transact-sql.md)
+        [VERIFYSIGNEDBYASYMKEY](../../t-sql/functions/verifysignedbyasymkey-transact-sql.md)
     :::column-end:::
 :::row-end:::
 :::row:::
     :::column:::
         [SIGNBYCERT](../../t-sql/functions/signbycert-transact-sql.md)
     :::column-end:::
     :::column:::
-        [VERIGYSIGNEDBYCERT](../../t-sql/functions/verifysignedbycert-transact-sql.md)
+        [VERIFYSIGNEDBYCERT](../../t-sql/functions/verifysignedbycert-transact-sql.md)
     :::column-end:::
 :::row-end:::
 :::row:::