Merge pull request #234804 from hirenshah1/patch-42

Update faq.yml

Author: v-ccolin

articles/cloud-services-extended-support/faq.yml

@@ -1,7 +1,7 @@
 ### YamlMime:FAQ
 metadata:
-  title: Frequently asked questions for to Azure Cloud Services (extended support)
-  description: Frequently asked questions for to Azure Cloud Services (extended support)
+  title: Frequently asked questions for Azure Cloud Services (extended support)
+  description: Frequently asked questions for Azure Cloud Services (extended support)
   ms.topic: faq
   ms.service: cloud-services-extended-support
   author: gachandw
@@ -30,7 +30,7 @@ sections:
       - question: |
           How does my quota change? 
         answer: |
-          Customers will need to request quota using the same processes as any other Azure Resource Manager product.Quota in Azure Resource Manager is regional and a separate quota request will be needed for each region.
+          Customers will need to request quota using the same processes as any other Azure Resource Manager product. Quota in Azure Resource Manager is regional and a separate quota request will be needed for each region.
 
       - question: |
           Why don’t I see a production & staging slot anymore?
@@ -58,7 +58,7 @@ sections:
           There are no changes to the design, architecture or components of web and worker roles. 
 
       - question: |
-          Role Instance Scaling keeps failing, how to mitigate this ?
+          Role Instance Scaling keeps failing, how to mitigate this?
         answer: |
           When multiple Scale calls happen on the same Cloud Service (for different roles) at the same approximate time, due to a race condition, the Microsoft Platform components go out of sync leading to failures. Microsoft is actively working on resolving this issue. The workaround suggested for the interim is not to auto scale all roles simultaneously.
           
@@ -84,7 +84,7 @@ sections:
       - question: |
           How can I get the deployment ID for my Cloud Service (extended support)
         answer: |
-          Deployment ID aka Private ID can be accessed using the [CloudServiceInstanceView](/rest/api/compute/cloudservices/getinstanceview#cloudserviceinstanceview) API. It is also available on the Azure portal under the Role and Instances blade of the Cloud Service (extended support)
+          Deployment ID, also known as Private ID, can be accessed using the [CloudServiceInstanceView](/rest/api/compute/cloudservices/getinstanceview#cloudserviceinstanceview) API. It is also available on the Azure portal under the Role and Instances blade of the Cloud Service (extended support)
           
       - question: |
           Are there any pricing differences between Cloud Services (classic) and Cloud Services (extended support)?
@@ -171,7 +171,7 @@ sections:
       - question: |
           Can the reserved IP be updated after a successful deployment?
         answer: |
-          A reserved IP cannot be added, removed or changed during deployment update or upgrade. If the IP addresses needs to be changed, please use a swappable Cloud Service or deploy two Cloud Services with a CName in Azure DNS\Traffic Manager so that the IP can be pointed to either of them.
+          A reserved IP cannot be added, removed or changed during deployment update or upgrade. If the IP addresses need to be changed, please use a swappable Cloud Service or deploy two Cloud Services with a CName in Azure DNS\Traffic Manager so that the IP can be pointed to either of them.
 
       - question: |
           Can I use a DNS name with Cloud Services (extended support)? 
@@ -208,10 +208,15 @@ sections:
   - name: Known Issues
     questions:
       - question: |
-          Role Instance Scaling keeps failing, how to mitigate this ?
+          Role Instance Scaling keeps failing, how to mitigate this?
         answer: |
           When multiple Scale calls happen on the same Cloud Service (for different roles) at the same approximate time, due to a race condition, the Microsoft Platform components go out of sync leading to failures. Microsoft is actively working on resolving this issue. The workaround suggested for the interim is not to auto scale all roles simultaneously.
           
+      - question: |
+          Visual Studio/Tools doesn't support deployment of CS-ES when VNET is located in a different Resource Group. How to deploy? 
+        answer: |
+          This scenario is not supported via Visual Studio. Please deploy via PowerShell or Portal.
+          
 additionalContent: |
 
   ## Next steps