diff --git a/docs/relational-databases/security/encryption/transparent-data-encryption.md b/docs/relational-databases/security/encryption/transparent-data-encryption.md
index 99f0d95252c..38d29a6e592 100644
--- a/docs/relational-databases/security/encryption/transparent-data-encryption.md
+++ b/docs/relational-databases/security/encryption/transparent-data-encryption.md
@@ -236,7 +236,7 @@ ALTER DATABASE <db_name> SET ENCRYPTION SUSPEND;
 Similarly, the following syntax resumes the TDE encryption scan:
 
 ```sql
-ALTER DATABASE <db_name> SET ENCRYPTION RESUME;
+ALTER DATABASE <db_name> SET ENCRYPTION RESUME;
 ```
 
 To show the current state of the encryption scan, `encryption_scan_state` has been added to the `sys.dm_database_encryption_keys` dynamic management view. There is also a new column called `encryption_scan_modify_date` which will contain the date and time of the last encryption scan state change. Also note that if the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] instance is restarted while the encryption scan is in a suspended state, a message will be logged in the error log on startup indicating that there is an existing scan that has been paused.