Remove bias sensitive term include file name

MikeRayMSFT · MikeRayMSFT · commit 6c9166b4599e · 2020-06-19T13:03:29.000-07:00
diff --git a/docs/includes/bias-sensitive-term-t.md b/docs/includes/bias-sensitive-term-t.md
diff --git a/docs/linux/sql-server-linux-availability-group-cluster-sles.md b/docs/linux/sql-server-linux-availability-group-cluster-sles.md
@@ -22,7 +22,7 @@ For more information on cluster configuration, resource agent options, managemen
 >[!NOTE]
 >At this point, SQL Server's integration with Pacemaker on Linux is not as coupled as with WSFC on Windows. SQL Server service on Linux is not cluster aware. Pacemaker controls all of the orchestration of the cluster resources, including the availability group resource. On Linux, you should not rely on Always On Availability Group Dynamic Management Views (DMVs) that provide cluster information like sys.dm_hadr_cluster. Also, virtual network name is specific to WSFC, there is no equivalent of the same in Pacemaker. You can still create a listener to use it for transparent reconnection after failover, but you will have to manually register the listener name in the DNS server with the IP used to create the virtual IP resource (as explained in the following sections).
 
-[!INCLUDE [bias-sensitive-term-slave](../includes/bias-sensitive-term-slave.md)]
+[!INCLUDE [bias-sensitive-term-t](../includes/bias-sensitive-term-t.md)]
 
 ## Roadmap
 
diff --git a/docs/linux/sql-server-linux-create-availability-group.md b/docs/linux/sql-server-linux-create-availability-group.md
@@ -579,7 +579,7 @@ After an availability group is created in [!INCLUDE[ssnoversion-md](../includes/
 
 The AG resource that is created is a special kind of resource called a clone. The AG resource essentially has copies on each node, and there is one controlling resource called the master. The master is associated with the server hosting the primary replica. The other resources host secondary replicas (regular or configuration-only) and can be promoted to master in a failover.
 
-[!INCLUDE [bias-sensitive-term-slave](../includes/bias-sensitive-term-slave.md)]
+[!INCLUDE [bias-sensitive-term-t](../includes/bias-sensitive-term-t.md)]
 
 1.  Create the AG resource with the following syntax:
 
diff --git a/docs/linux/sql-server-linux-ha-basics.md b/docs/linux/sql-server-linux-ha-basics.md
@@ -164,7 +164,7 @@ Both a WSFC and a Pacemaker cluster have the concept of a resource. A resource i
 
 Pacemaker has standard and clone resources. Clone resources are ones that run simultaneously on all nodes. An example would be an IP address that runs on multiple nodes for load balancing purposes. Any resource that gets created for FCIs uses a standard resource, since only one node can host an FCI at any given time.
 
-[!INCLUDE [bias-sensitive-term-slave](../includes/bias-sensitive-term-slave.md)]
+[!INCLUDE [bias-sensitive-term-t](../includes/bias-sensitive-term-t.md)]
 
 When an AG is created, it requires a specialized form of a clone resource called a multi-state resource. While an AG only has one primary replica, the AG itself is running across all nodes that it is configured to work on, and can potentially allow things such as read-only access. Because this is a "live" use of the node, the resources have the concept of two states: master and slave. For more information, see [Multi-state resources: Resources that have multiple modes](https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Configuring_the_Red_Hat_High_Availability_Add-On_with_Pacemaker/s1-multistateresource-HAAR.html).
 
