fix a term

Author: mumian

articles/azure-resource-manager/templates/templates-cloud-consistency.md

@@ -17,7 +17,7 @@ A key benefit of Azure is consistency. Development investments for one location
 Microsoft offers intelligent, enterprise-ready cloud services in many locations, including:
 
 * The global Azure platform supported by a growing network of Microsoft-managed datacenters in regions around the world.
-* Isolated sovereign clouds like Azure Germany, Azure Government, and Azure China (Azure operated by 21Vianet). Sovereign clouds provide a consistent platform with most of the same great features that global Azure customers have access to.
+* Isolated sovereign clouds like Azure Germany, Azure Government, and Azure China 21Vianet. Sovereign clouds provide a consistent platform with most of the same great features that global Azure customers have access to.
 * Azure Stack, a hybrid cloud platform that lets you deliver Azure services from your organization's datacenter. Enterprises can set up Azure Stack in their own datacenters, or consume Azure Services from service providers, running Azure Stack in their facilities (sometimes known as hosted regions).
 
 At the core of all these clouds, Azure Resource Manager provides an API that allows a wide variety of user interfaces to communicate with the Azure platform. This API gives you powerful infrastructure-as-code capabilities. Any type of resource that is available on the Azure cloud platform can be deployed and configured with Azure Resource Manager. With a single template, you can deploy and configure your complete application to an operational end state.
@@ -439,7 +439,7 @@ Endpoint namespaces can also be used in the output of a template as information
 In general, avoid hardcoded endpoints in a template. The best practice is to use the reference template function to retrieve the endpoints dynamically. For example, the endpoint most commonly hardcoded is the endpoint namespace for storage accounts. Each storage account has a unique FQDN that is constructed by concatenating the name of the storage account with the endpoint namespace. A blob storage account named mystorageaccount1 results in different FQDNs depending on the cloud:
 
 * **mystorageaccount1.blob.core.windows.net** when created on the global Azure cloud.
-* **mystorageaccount1.blob.core.chinacloudapi.cn** when created in the Azure China cloud.
+* **mystorageaccount1.blob.core.chinacloudapi.cn** when created in the Azure China 21Vianet cloud.
 
 The following reference template function retrieves the endpoint namespace from the storage resource provider: