Merge pull request #26946 from rwestMSFT/rw-0502-linux-fix-headings

Fix headings in some Linux articles

Author: prmerger-automator[bot]

docs/linux/sql-server-linux-availability-group-failover-ha.md

@@ -3,7 +3,7 @@ title: Manage availability group failover - SQL Server on Linux
 description: "This article describes types of failover: automatic, planned manual failover, and forced manual failover. Automatic and planned manual preserve all your data."
 author: tejasaks
 ms.author: tejasaks
-ms.reviewer: vanto
+ms.reviewer: vanto, randolphwest
 ms.date: 10/05/2021
 ms.service: sql
 ms.subservice: linux
@@ -17,14 +17,14 @@ Within the context of an availability group (AG), the primary role and secondary
 
 For background information about failover, see [Failover and failover modes](../database-engine/availability-groups/windows/failover-and-failover-modes-always-on-availability-groups.md).
 
-## <a name="failover"></a>Manual failover
+## <a id="failover"></a> Manual failover
 
 Use the cluster management tools to fail over an AG managed by an external cluster manager. For example, if a solution uses Pacemaker to manage a Linux cluster, use `pcs` to perform manual failovers on RHEL or Ubuntu. On SLES use `crm`. 
 
 > [!IMPORTANT]
 > Under normal operations, do not fail over with Transact-SQL or SQL Server management tools like SSMS or PowerShell. When `CLUSTER_TYPE = EXTERNAL`, the only acceptable value for `FAILOVER_MODE` is `EXTERNAL`. With these settings, all manual or automatic failover actions are executed by the external cluster manager. For instructions to force failover with potential data loss, see [Force failover](#forceFailover).
 
-### <a name="manualFailover">Manual failover steps
+### <a id="manualFailover"></a> Manual failover steps
 
 To fail over, the secondary replica that will become the primary replica must be synchronous. If a secondary replica is asynchronous, [change the availability mode](../database-engine/availability-groups/windows/change-the-availability-mode-of-an-availability-replica-sql-server.md).
 
@@ -36,7 +36,7 @@ Manually fail over in two steps.
 
    Second, [remove the location constraint](#removeLocConstraint).
 
-#### <a name="manualMove"></a> Step 1. Manually fail over by moving availability group resource
+#### <a id="manualMove"></a> Step 1. Manually fail over by moving availability group resource
 
 To manually fail over an AG resource named *ag_cluster* to cluster node named *nodeName2*, run the appropriate command for your distribution:
 
@@ -56,7 +56,7 @@ To manually fail over an AG resource named *ag_cluster* to cluster node named *n
 >When you use the --lifetime option, the location constraint created to move the resource is temporary in nature and is valid for 30 seconds in previous example.
 >Please note that the temporary constraint is not cleared automatically and may show up in the constraint list, but as an expired constraint. Expired constraints do not affect the failover behavior of pacemaker cluster. If you do not use the --lifetime option when moving the resource, you should remove a location constraint that is automatically added as noted below.
 
-#### <a name="removeLocConstraint"> </a> Step 2. Remove the location constraint
+#### <a id="removeLocConstraint"></a> Step 2. Remove the location constraint
 
 During a manual failover, the `pcs` command `move` or `crm` command `migrate` adds a location constraint for the resource to be placed on the new target node. To see the new constraint, run the following command after manually moving the resource:
 
@@ -116,7 +116,7 @@ For more information:
 - [Pacemaker - Move Resources Manually](https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_move_resources_manually.html)
  [SLES Administration Guide - Resources](https://www.suse.com/documentation/sle-ha-12/singlehtml/book_sleha/book_sleha.html#sec.ha.troubleshooting.resource) 
 
-## <a name="forceFailover"></a> Force failover 
+## <a id="forceFailover"></a> Force failover
 
 A forced failover is intended strictly for disaster recovery. In this case, you cannot fail over with cluster management tools because the primary datacenter is down. If you force failover to an unsynchronized secondary replica, some data loss is possible. Only force failover if you must restore service to the AG immediately and are willing to risk losing data.
 

docs/linux/sql-server-linux-setup-full-text-search.md

@@ -24,7 +24,7 @@ Install SQL Server Full-Text Search for your platform:
 - [Ubuntu](#ubuntu)
 - [SUSE Linux Enterprise Server](#SLES)
 
-## <a name="RHEL">Install on RHEL</a>
+## <a id="RHEL"></a> Install on RHEL
 
 Use the following commands to install the **mssql-server-fts** on Red Hat Enterprise Linux. 
 
@@ -41,7 +41,7 @@ sudo yum update mssql-server-fts
 
 If you need an offline installation, locate the Full-text Search package download in the [Release notes](sql-server-linux-release-notes-2017.md). Then use the same offline installation steps described in the article [Install SQL Server](sql-server-linux-setup.md#offline).
 
-## <a name="ubuntu">Install on Ubuntu</a>
+## <a id="ubuntu"></a> Install on Ubuntu
 
 Use the following commands to install the **mssql-server-fts** on Ubuntu. 
 
@@ -59,7 +59,7 @@ sudo apt-get install -y mssql-server-fts
 
 If you need an offline installation, locate the Full-text Search package download in the [Release notes](sql-server-linux-release-notes-2017.md). Then use the same offline installation steps described in the article [Install SQL Server](sql-server-linux-setup.md#offline).
 
-## <a name="SLES">Install on SLES</a>
+## <a id="SLES"></a> Install on SLES
 
 Use the following commands to install the **mssql-server-fts** on SUSE Linux Enterprise Server. 
 

docs/linux/sql-server-linux-setup-sql-agent.md

@@ -36,7 +36,7 @@ Before using the SQL Server Agent on Linux, use the following steps to enable or
    | SQL Server 2017 CU4 and higher</br>SQL Server 2019 | [Enable the SQL Server Agent](#EnableAgentAfterCU4) |
    | SQL Server 2017 CU3 and lower | [Install the SQL Server Agent](#InstallAgentBelowCU4) |
 
-## <a id="EnableAgentAfterCU4"></a>Enable the SQL Server Agent
+## <a id="EnableAgentAfterCU4"></a> Enable the SQL Server Agent
 
 For SQL Server 2019 and SQL Server 2017 CU4 and higher, you only need to enable the SQL Server Agent. You do not need to install a separate package.
 
@@ -53,7 +53,7 @@ sudo systemctl restart mssql-server
 > [!NOTE]
 > SQL Server Management Studio Object Explorer does not display the contents of the SQL Server Agent node unless *Agent XPs* extended stored procedures are enabled, regardless of the SQL Server Agent service state. For more information, see [Agent XPs Server Configuration Option](../database-engine/configure-windows/agent-xps-server-configuration-option.md)
 
-## <a name="InstallAgentBelowCU4"></a>Install the SQL Server Agent
+## <a id="InstallAgentBelowCU4"></a> Install the SQL Server Agent
 
 For SQL Server 2017 CU3 and earlier, you must install the SQL Server Agent package.
 
@@ -65,7 +65,7 @@ Install the SQL Server Agent for your platform:
 - [Ubuntu](#ubuntu)
 - [SUSE Linux Enterprise Server](#SLES)
 
-### <a name="RHEL">Install on RHEL</a>
+### <a id="RHEL"></a> Install on RHEL
 
 Use the following steps to install the **mssql-server-agent** on Red Hat Enterprise Linux. 
 
@@ -84,7 +84,7 @@ sudo systemctl restart mssql-server
 
 If you need an offline installation, locate the SQL Server Agent package download in the [Release notes](sql-server-linux-release-notes-2017.md). Then use the same offline installation steps described in the article [Install SQL Server](sql-server-linux-setup.md#offline).
 
-### <a name="ubuntu">Install on Ubuntu</a>
+### <a id="ubuntu"></a> Install on Ubuntu
 
 Use the following steps to install the **mssql-server-agent** on Ubuntu. 
 
@@ -104,7 +104,7 @@ sudo systemctl restart mssql-server
 
 If you need an offline installation, locate the SQL Server Agent package download in the [Release notes](sql-server-linux-release-notes-2017.md). Then use the same offline installation steps described in the article [Install SQL Server](sql-server-linux-setup.md#offline).
 
-### <a name="SLES">Install on SLES</a>
+### <a id="SLES"></a> Install on SLES
 
 Use the following steps to install the **mssql-server-agent** on SUSE Linux Enterprise Server.