Merge branch 'release-sqlseattle' of https://github.com/MicrosoftDocs/sql-docs-pr into vnext

Author: negust-microsoft

docs/azure-data-studio/release-notes.md

@@ -1,6 +1,6 @@
 ---
-title: Microsoft SQL Operations Studio (preview) release notes| Microsoft Docs
-description: 'Microsoft SQL Operations Studio (preview) release notes'
+title: Azure Data Studio (preview) release notes| Microsoft Docs
+description: 'Azure Data Studio (preview) release notes'
 ms.custom: "tools|sos"
 ms.date: "08/30/2018"
 ms.prod: sql
@@ -14,7 +14,7 @@ author: "stevestein"
 ms.author: "sstein"
 manager: craigg
 ---
-# SQL Operations Studio (preview) release notes
+# Azure Data Studio (preview) release notes
 
 **[Download the August Public Preview](download.md)**
 

docs/azure-data-studio/toc.yml

@@ -59,7 +59,7 @@
   items:
   - name: Transact-SQL Reference
     href: ../t-sql/language-reference.md
-  - name: SQL Operations Studio (preview) GitHub repo
+  - name: Azure Data Studio (preview) GitHub repo
     href: https://www.github.com/Microsoft/SqlOpsStudio
   - name: SQL Server Blog
     href: https://blogs.technet.microsoft.com/dataplatforminsider/

docs/relational-databases/security/encryption/configure-always-encrypted-enclaves.md

@@ -93,7 +93,7 @@ On the client/development computer:
 2. To verify Always Encrypted with secure enclaves is supported in your instance, run the following query:
 
    ```sql
-   SELECT * FROM sys.configurations
+   SELECT [name], [value], [value_in_use] FROM sys.configurations
    WHERE [name] = 'column encryption enclave type'
    ```
 
@@ -115,7 +115,7 @@ On the client/development computer:
 5. Confirm the secure enclave is now loaded by running the following query:
 
    ```sql
-   SELECT * FROM sys.configurations
+   SELECT [name], [value], [value_in_use] FROM sys.configurations
    WHERE [name] = 'column encryption enclave type'
    ```