Changing headers

Author: VanMSFT

articles/sql-database/sql-database-auditing.md

@@ -83,7 +83,7 @@ The following section describes the configuration of auditing using the Azure po
 
    ![storage options](./media/sql-database-auditing-get-started/auditing-select-destination.png)
 
-### <a id="audit-storage-destination">Audit to storage destination</a>
+### <a id="audit-storage-destination"></a>Audit to storage destination
 
 To configure writing audit logs to a storage account, select **Storage** and open **Storage details**. Select the Azure storage account where logs will be saved, and then select the retention period. Then click **OK**. Logs older than the retention period are deleted.
 
@@ -102,13 +102,13 @@ To configure writing audit logs to a storage account, select **Storage** and ope
 - When using AAD Authentication, failed logins records will *not* appear in the SQL audit log. To view failed login audit records, you need to visit the [Azure Active Directory portal]( ../active-directory/reports-monitoring/reference-sign-ins-error-codes.md), which logs details of these events.
 - Auditing on [Read-Only Replicas](sql-database-read-scale-out.md) is automatically enabled. For further details about the hierarchy of the storage folders, naming conventions, and log format, see the [SQL Database Audit Log Format](sql-database-audit-log-format.md). 
 
-### <a id="audit-log-analytics-destination">Audit to Log Analytics destination</a>
+### <a id="audit-log-analytics-destination"></a>Audit to Log Analytics destination
 
 To configure writing audit logs to a Log Analytics workspace, select **Log Analytics (Preview)** and open **Log Analytics details**. Select or create the Log Analytics workspace where logs will be written and then click **OK**.
 
    ![LogAnalyticsworkspace](./media/sql-database-auditing-get-started/auditing_select_oms.png)
 
-### <a id="audit-event-hub-destination">Audit to Event Hub destination</a>
+### <a id="audit-event-hub-destination"></a>Audit to Event Hub destination
 
 > [!WARNING]
 > Enabling auditing on a server that has a SQL pool on it **results in the SQL pool being resumed and re-paused again** which may incur billing charges.
@@ -193,7 +193,7 @@ If you chose to write audit logs to an Azure storage account, there are several
 
 <!--The description in this section refers to preceding screen captures.-->
 
-#### Auditing geo-replicated databases
+### Auditing geo-replicated databases
 
 With geo-replicated databases, when you enable auditing on the primary database the secondary database will have an identical auditing policy. It is also possible to set up auditing on the secondary database by enabling auditing on the **secondary server**, independently from the primary database.
 
@@ -205,7 +205,7 @@ With geo-replicated databases, when you enable auditing on the primary database
     >[!IMPORTANT]
     >With database-level auditing, the storage settings for the secondary database will be identical to those of the primary database, causing cross-regional traffic. We recommend that you enable only server-level auditing, and leave the database-level auditing disabled for all databases.
 
-#### Storage key regeneration
+### Storage key regeneration
 
 In production, you are likely to refresh your storage keys periodically. When writing audit logs to Azure storage, you need to resave your auditing policy when refreshing your keys. The process is as follows:
 
@@ -220,7 +220,7 @@ In production, you are likely to refresh your storage keys periodically. When wr
 
 ## <a id="manage-auditing"></a>Manage Azure SQL Server and Database auditing
 
-#### Using Azure PowerShell
+### Using Azure PowerShell
 
 **PowerShell cmdlets (including WHERE clause support for additional filtering)**:
 
@@ -233,7 +233,7 @@ In production, you are likely to refresh your storage keys periodically. When wr
 
 For a script example, see [Configure auditing and threat detection using PowerShell](scripts/sql-database-auditing-and-threat-detection-powershell.md).
 
-#### Using REST API
+### Using REST API
 
 **REST API**:
 
@@ -249,7 +249,7 @@ Extended policy with WHERE clause support for additional filtering:
 - [Get Database *Extended* Auditing Policy](/rest/api/sql/database%20extended%20auditing%20settings/get)
 - [Get Server *Extended* Auditing Policy](/rest/api/sql/server%20auditing%20settings/get)
 
-#### Using Azure Resource Manager templates
+### Using Azure Resource Manager templates
 
 You can manage Azure SQL database auditing using [Azure Resource Manager](../azure-resource-manager/management/overview.md) templates, as shown in these examples: