Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into fix-headings

Author: eross-msft

articles/active-directory-domain-services/join-windows-vm.md

@@ -150,9 +150,11 @@ With the VM created and an RDP connection establish, now let's join the Windows
 1. To complete the process to join to the Azure AD DS managed domain, restart the VM.
 
 > [!TIP]
-> You can also domain-join a VM using PowerShell with the [Add-Computer][add-computer] cmdlet. The following example joins the *CONTOSO* domain and then restarts the VM. When prompted, enter the credentials for a user that belongs to the *Azure AD DC administrators* group:
+> You can domain-join a VM using PowerShell with the [Add-Computer][add-computer] cmdlet. The following example joins the *CONTOSO* domain and then restarts the VM. When prompted, enter the credentials for a user that belongs to the *Azure AD DC administrators* group:
 >
 > `Add-Computer -DomainName CONTOSO -Restart`
+>
+> To domain-join a VM without connecting to it and manually configuring the connection, you can also explore the use of the [Set-AzVmAdDomainExtension][set-azvmaddomainextension] Azure PowerShell cmdlet.
 
 Once the Windows Server VM has restarted, any policies applied in the Azure AD DS managed domain are be pushed to the VM. You can also now sign in to the Windows Server VM using appropriate domain credentials.
 
@@ -228,3 +230,4 @@ To administer your Azure AD DS managed domain, configure a management VM using t
 [add-computer]: /powershell/module/microsoft.powershell.management/add-computer
 [jit-access]: ../security-center/security-center-just-in-time.md
 [azure-bastion]: ../bastion/bastion-create-host-portal.md
+[set-azvmaddomainextension]: /powershell/module/az.compute/set-azvmaddomainextension

articles/cosmos-db/faq.md

@@ -26,6 +26,12 @@ Key/value (table), columnar, document, and graph data models are all natively su
 
 Azure Cosmos DB has a schema agnostic indexing engine capable of automatically indexing all the data it ingests without requiring any schema or secondary indexes from the developer. The engine relies on a set of logical index layouts (inverted, columnar, tree) which decouple the storage layout from the index and query processing subsystems. Cosmos DB also has the ability to support a set of wire protocols and APIs in an extensible manner and translate them efficiently to the core data model (1) and the logical index layouts (2) making it uniquely capable of supporting more than one data model natively.
 
+### Can I use multiple APIs to access my data?
+
+Azure Cosmos DB is Microsoft's globally distributed, multi-model database service. Where multi-model means Azure Cosmos DB supports multiple APIs and multiple data models, different APIs use different data formats for storage and wire protocol. For example, SQL uses JSON, MongoDB uses BSON, Table uses EDM, Cassandra uses CQL, Gremlin uses GraphSON. As a result, we recommend using the same API for all access to the data in a given account.
+
+Each API operates independently, except the Gremlin and SQL API, which are interoperable.
+
 ### Is Azure Cosmos DB HIPAA compliant?
 
 Yes, Azure Cosmos DB is HIPAA-compliant. HIPAA establishes requirements for the use, disclosure, and safeguarding of individually identifiable health information. For more information, see the [Microsoft Trust Center](https://www.microsoft.com/en-us/TrustCenter/Compliance/HIPAA).

includes/virtual-machines-managed-disks-overview.md

@@ -72,7 +72,9 @@ Every VM contains a temporary disk, which is not a managed disk. The temporary d
 
 ## Managed disk snapshots
 
-A managed disk snapshot is a read-only crash-consistent full copy of a managed disk that is stored as a standard managed disk by default. With snapshots, you can back up your managed disks at any point in time. These snapshots exist independent of the source disk and can be used to create new managed disks. They are billed based on the used size. For example, if you create a snapshot of a managed disk with provisioned capacity of 64 GiB and actual used data size of 10 GiB, that snapshot is billed only for the used data size of 10 GiB.  
+A managed disk snapshot is a read-only crash-consistent full copy of a managed disk that is stored as a standard managed disk by default. With snapshots, you can back up your managed disks at any point in time. These snapshots exist independent of the source disk and can be used to create new managed disks. 
+
+Snapshots are billed based on the used size. For example, if you create a snapshot of a managed disk with provisioned capacity of 64 GiB and actual used data size of 10 GiB, that snapshot is billed only for the used data size of 10 GiB. You can see the used size of your snapshots by looking at the [Azure usage report](https://docs.microsoft.com/en-us/azure/billing/billing-understand-your-bill). For example, if the used data size of a snapshot is 10 GiB, the usage report will show 10 GiB/(31 days x 24 hours) = 0.013441 GiB as the consumed quantity.
 
 To learn more about how to create snapshots with managed disks, see the following resources: