updates

Author: v-albemi

articles/app-service/app-service-web-configure-tls-mutual-auth.md

@@ -143,11 +143,11 @@ Client certificate configurations that use TLS renegotiation can't support incom
 
 To address the 100-KB limit, consider these solutions:
 
-1. Disable TLS renegotiation. Take the following actions in your app's client certificate configurations:
+- Disable TLS renegotiation. Take the following actions in your app's client certificate configurations:
     - Set the client certificate mode to **Required** or **Optional**.
     - Remove all client certificate exclusion paths.
-1. Send a HEAD request before the PUT/POST request. The HEAD request handles the client certificate.
-1. Add the header `Expect: 100-Continue` to your request. This header causes the client to wait until the server responds with a `100 Continue` before sending the request body, and the buffers are bypassed.
+- Send a HEAD request before the PUT/POST request. The HEAD request handles the client certificate.
+- Add the header `Expect: 100-Continue` to your request. This header causes the client to wait until the server responds with a `100 Continue` before sending the request body, and the buffers are bypassed.
 
 ## Access the client certificate
 

includes/app-service-ssl-prepare-app.md

@@ -12,7 +12,7 @@ ms.custom: "include file"
 
 If you want to create custom TLS/SSL bindings or to enable client certificates for your App Service app, your [App Service plan](https://azure.microsoft.com/pricing/details/app-service/) must be in the Basic, Standard, Premium, or Isolated tiers.
 
-To make sure that your web app is in the supported pricing tier:
+To make sure that your web app is in a supported pricing tier:
 
 ### Go to your web app