Fixed H2/H3 Headings

Author: TreMansdoerfer-Microsoft

articles/frontdoor/front-door-waf.md

@@ -19,7 +19,7 @@ Many web applications have experienced rapid increase of traffic in recent weeks
 
 We will be using Azure CLI to set up the WAF in this tutorial, but all these steps are also fully supported in Azure portal, Azure PowerShell, Azure ARM, and Azure REST APIs. 
 
-### Prerequisites
+## Prerequisites
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin. 
 
@@ -35,7 +35,7 @@ az extension add --name front-door
 
 Note: For more details of the commands listed below, refer to the [Azure CLI reference for Front Door](https://docs.microsoft.com/cli/azure/ext/front-door/?view=azure-cli-latest).
 
-### Step 1: Create an Azure Front Door (AFD) resource
+## Step 1: Create an Azure Front Door (AFD) resource
 
 
 ```azurecli-interactive 
@@ -52,7 +52,7 @@ az network front-door create --backend-address <>  --accepted-protocols <> --nam
 
 In the response you get from successfully executing this command, look for the key "hostName" and note down its value to be used in a later step. The hostName is the DNS name of the AFD resource you had created
 
-### Step 2: Create an Azure WAF profile to use with Azure Front Door resources
+## Step 2: Create an Azure WAF profile to use with Azure Front Door resources
 
 ```azurecli-interactive 
 az network front-door waf-policy create --name <>  --resource-group <>  --disabled false --mode Prevention
@@ -70,7 +70,7 @@ In the response you get from successfully executing this command, look for the k
 
 /subscriptions/**subscription id**/resourcegroups/**resource group name**/providers/Microsoft.Network/frontdoorwebapplicationfirewallpolicies/**WAF policy name**
 
-### Step 3: Add managed rulesets to this WAF policy
+## Step 3: Add managed rulesets to this WAF policy
 
 In a WAF policy, you can add managed rulesets that are a set of rules built and managed by Microsoft and gives out of the box protection against entire classes of threats. In this example, we are adding two such rulesets (1) Default ruleset that protects against common web threats and (2) Bot protection ruleset, which protects against malicious bots
 
@@ -90,7 +90,7 @@ az network front-door waf-policy managed-rules add --policy-name <> --resource-g
 
 --resource-group The resource group you had placed this WAF resource in.
 
-### Step 4: Associate the WAF policy with the AFD resource
+## Step 4: Associate the WAF policy with the AFD resource
 
 In this step, we will be associating the WAF policy we have built with the AFD resource that is in front of your web application.
 
@@ -108,7 +108,7 @@ Note: the above example is for the case where you are not using a custom domain,
 
 If you are not using any custom domains to access your web applications, you can skip step #5. In that case, you will be providing to your end users the hostname you obtained in step #1 to navigate to your web application
 
-### Step 5: Configure custom domain for your web application
+## Step 5: Configure custom domain for your web application
 
 Initially the custom domain name of your web application (the one that customers use to refer to your application, for example, www.contoso.com) was pointing towards the place where you had it running before AFD was introduced. After this change of architecture adding AFD+WAF to front the application, the DNS entry corresponding to that custom domain should now point to this AFD resource. This can be done by remapping this entry in your DNS server to the AFD hostname you had noted in step #1.
 
@@ -120,6 +120,6 @@ In addition, you also need to update your AFD configuration to [add this custom
 
 Finally, if you are using a custom domain to reach your web application and want to enable the HTTPS protocol, you need to have the [certificates for your custom domain setup in AFD](https://docs.microsoft.com/azure/frontdoor/front-door-custom-domain-https). 
 
-### Step 6: Lock down your web application
+## Step 6: Lock down your web application
 
 One optional best practice to follow is to ensure that only AFD edges can communicate with your web application. This action will ensure that no one can bypass the AFD protections and access your applications directly. You can accomplish this lock down by visiting the [FAQ section of AFD](https://docs.microsoft.com/azure/frontdoor/front-door-faq) and referring to the question regarding locking down backends for access only by AFD.