update metadata- fix issue 2

Author: TobyTu

articles/cloud-services/cloud-services-configuration-and-management-faq.md

@@ -201,7 +201,7 @@ These steps could be automated via a startup task, so that whenever a new PaaS i
 Once this has been done, you can verify whether the HTTP/2 has been enabled or not by using one of the following methods:
 
 - Enable Protocol version in IIS logs and look into the IIS logs. It will show HTTP/2 in the logs. 
-- Enable F12 Developer Tool in Internet Explorer/Microsoft Edge and switch to the Network tab to verify the protocol. 
+- Enable F12 Developer Tool in Internet Explorer or Microsoft Edge and switch to the Network tab to verify the protocol. 
 
 For more information, see [HTTP/2 on IIS](https://blogs.iis.net/davidso/http2).
 

articles/cloud-services/cloud-services-connectivity-and-networking-faq.md

@@ -97,7 +97,7 @@ To make sure the public-facing IP address of your cloud service (also known as a
 - [Reserve the IP address of an existing cloud service](../virtual-network/virtual-networks-reserved-public-ip.md#reserve-the-ip-address-of-an-existing-cloud-service)
 - [Associate a reserved IP to a cloud service by using a service configuration file](../virtual-network/virtual-networks-reserved-public-ip.md#associate-a-reserved-ip-to-a-cloud-service-by-using-a-service-configuration-file)
 
-If you have more than one instance for your roles, associating RIP with your cloud service shouldn't cause any downtime.Alternatively, you can whitelist the IP range of your Azure datacenter.You can find all Azure IP ranges at the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=41653).
+If you have more than one instance for your roles, associating RIP with your cloud service shouldn't cause any downtime. Alternatively, you can whitelist the IP range of your Azure datacenter. You can find all Azure IP ranges at the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=41653).
 
 This file contains the IP address ranges (including compute, SQL, and storage ranges) used in Azure datacenters. An updated file is posted weekly that reflects the currently deployed ranges and any upcoming changes to the IP ranges. New ranges that appear in the file aren't used in the datacenters for at least one week. Download the new .xml file every week, and perform the necessary changes on your site to correctly identify services running in Azure. Azure ExpressRoute users might note that this file used to update the BGP advertisement of Azure space in the first week of each month.
 

articles/cloud-services/cloud-services-workflow-process.md

@@ -37,7 +37,7 @@ The following diagram presents the architecture of Azure resources.
 
 **D**.  WindowsAzureGuestAgent is responsible for the following:
 
-1. Configuring the Guest OS including firewall, ACLs, LocalStorage resources, service package and configuration, and certificates.Setting up the SID for the user account that the role will run under.
+1. Configuring the Guest OS including firewall, ACLs, LocalStorage resources, service package and configuration, and certificates. Setting up the SID for the user account that the role will run under.
 2. Communicating the role status to the fabric.
 3. Starting WaHostBootstrapper and monitoring it to make sure that the role is in goal state.
 
@@ -54,7 +54,7 @@ The following diagram presents the architecture of Azure resources.
 3. Setting up the AppPool for the configured role in the service model
 4. Setting up IIS logging to point to the DiagnosticStore LocalStorage folder
 5. Configuring permissions and ACLs
-6. The website resides in %roleroot%:\sitesroot\0, and the apppool points to this location to run IIS. 
+6. The website resides in %roleroot%:\sitesroot\0, and the AppPool points to this location to run IIS. 
 
 **G**. Startup tasks are defined by the role model and started by WaHostBootstrapper. Startup tasks can be configured to run in the background asynchronously, and the host bootstrapper will start the startup task and then continue on to other startup tasks. Startup tasks can also be configured to run in Simple (default) mode in which the host bootstrapper will wait for the startup task to finish running and return a success (0) exit code before continuing to the next startup task.
 
@@ -70,7 +70,7 @@ The following diagram presents the architecture of Azure resources.
 
 ## Workflow processes
 
-1. A user makes a request, such as uploading .cspkg and .cscfg files, telling a resource to stop or making a configuration change, and so on. This can be done through the Azure portal or a tool that uses the Service Management API, such as the Visual Studio Publish feature. This request goes to RDFE to do all the subscription-related work and then communicate the request to FFE. The rest of these workflow steps are to deploy a new package and start it.
+1. A user makes a request, such as uploading ".cspkg" and ".cscfg" files, telling a resource to stop or making a configuration change, and so on. This can be done through the Azure portal or a tool that uses the Service Management API, such as the Visual Studio Publish feature. This request goes to RDFE to do all the subscription-related work and then communicate the request to FFE. The rest of these workflow steps are to deploy a new package and start it.
 2. FFE finds the correct machine pool (based on customer input such, as affinity group or geographical location plus input from the fabric, such as machine availability) and communicates with the master fabric controller in that machine pool.
 3. The fabric controller finds a host that has available CPU cores (or spins up a new host). The service package and configuration is copied to the host, and the fabric controller communicates with the host agent on the host OS to deploy the package (configure DIPs, ports, guest OS, and so on).
 4. The host agent starts the Guest OS and communicates with the guest agent (WindowsAzureGuestAgent). The host sends heartbeats to the guest to make sure that the role is working towards its goal state.
@@ -79,7 +79,7 @@ The following diagram presents the architecture of Azure resources.
 7. WaHostBootstrapper reads the **Startup** tasks from E:\RoleModel.xml and begins executing startup tasks. WaHostBootstrapper waits until all Simple startup tasks have finished and returned a “success” message.
 8. For Full IIS web roles, WaHostBootstrapper tells IISConfigurator to configure the IIS AppPool and points the site to `E:\Sitesroot\<index>`, where `<index>` is a 0 based index into the number of `<Sites>` elements defined for the service.
 9. WaHostBootstrapper will start the host process depending on the role type:
-    1. **Worker Role**: WaWorkerHost.exe is started. WaHostBootstrapper executes the OnStart() method.After it returns,  WaHostBootstrapper starts to execute the Run() method, and then simultaneously marks the role as Ready and puts it into the load balancer rotation (if InputEndpoints are defined). WaHostBootsrapper then goes into a loop of checking the role status.
+    1. **Worker Role**: WaWorkerHost.exe is started. WaHostBootstrapper executes the OnStart() method. After it returns,  WaHostBootstrapper starts to execute the Run() method, and then simultaneously marks the role as Ready and puts it into the load balancer rotation (if InputEndpoints are defined). WaHostBootsrapper then goes into a loop of checking the role status.
     1. **SDK 1.2 HWC Web Role**: WaWebHost is started. WaHostBootstrapper executes the OnStart() method. After it returns,  WaHostBootstrapper starts to execute the Run() method, and then simultaneously marks the role as Ready and puts it into the load balancer rotation. WaWebHost issues a warmup request (GET /do.rd_runtime_init). All web requests are sent to WaWebHost.exe. WaHostBootsrapper then goes into a loop of checking the role status.
     1. **Full IIS Web Role**: aIISHost is started. WaHostBootstrapper executes the OnStart() method. After it returns, it starts to execute the Run() method, and then simultaneously marks the role as Ready and puts it into the load balancer rotation. WaHostBootsrapper then goes into a loop of checking the role status.
 10. Incoming web requests to a Full IIS web role triggers IIS to start the W3WP process and serve the request, the same as it would in an on-premises IIS environment.