Updating subnet limit

Author: SnehaGunda

articles/cosmos-db/vnet-service-endpoint.md

@@ -30,7 +30,7 @@ There are two steps required to limit access to Azure Cosmos account from a subn
 
 ### Will virtual network ACLs and IP Firewall reject requests or connections? 
 
-When IP firewall or virtual network access rules are added, only requests from allowed sources get valid responses. Other requests are rejected with a 403 (Forbidden). It is important to distinguish Azure Cosmos account's firewall from a connection level firewall. The source can still connect to the service and the connections themselves aren’t rejected.
+When IP firewall or virtual network access rules are added, only requests from allowed sources get valid responses. Other requests are rejected with a 403 (Forbidden). It is important to distinguish Azure Cosmos account's firewall from a connection level firewall. The source can still connect to the service and the connections themselves aren't rejected.
 
 ### My requests started getting blocked when I enabled service endpoint to Azure Cosmos DB on the subnet. What happened?
 
@@ -46,7 +46,7 @@ The authorization validates permission for VNet resource action even if the user
 Only virtual network and their subnets added to Azure Cosmos account have access. Their peered VNets cannot access the account until the subnets within peered virtual networks are added to the account.
 
 ### What is the maximum number of subnets allowed to access a single Cosmos account? 
-Currently, you can have at most 64 subnets allowed for an Azure Cosmos account.
+Currently, you can have at most 256 subnets allowed for an Azure Cosmos account.
 
 ### Can I enable access from VPN and Express Route? 
 For accessing Azure Cosmos account over Express route from on premises, you would need to enable Microsoft peering. Once you put IP firewall or virtual network access rules, you can add the public IP addresses used for Microsoft peering on your Azure Cosmos account IP firewall to allow on premises services access to Azure Cosmos account. 
@@ -55,7 +55,7 @@ For accessing Azure Cosmos account over Express route from on premises, you woul
 NSG rules are used to limit connectivity to and from a subnet with virtual network. When you add service endpoint for Azure Cosmos DB to the subnet, there is no need to open outbound connectivity in NSG for your Azure Cosmos account. 
 
 ### Are service endpoints available for all VNets?
-No, Only Azure Resource Manager virtual networks can have service endpoint enabled. Classic virtual networks don’t support service endpoints.
+No, Only Azure Resource Manager virtual networks can have service endpoint enabled. Classic virtual networks don't support service endpoints.
 
 ### Can I "Accept connections from within public Azure datacenters" when service endpoint access is enabled for Azure Cosmos DB?  
 This is required only when you want your Azure Cosmos DB account to be accessed by other Azure first party services like Azure Data factory, Azure Cognitive Search or any service that is deployed in given Azure region.