Merge pull request #23521 from tarynpratt/patch-3

Update sql-server-ha-story.md

Author: PRMerger14

docs/includes/sql-server-ha-story.md

@@ -70,7 +70,7 @@ Each supported Linux distribution ships its own version of the Pacemaker cluster
 
 A WSFC and Pacemaker are more similar than different. Both provide a way to take individual servers and combine them in a configuration to provide availability, and have concepts of things like resources, constraints (even if implemented differently), failover, and so on. To support Pacemaker for both availability group and FCI configurations including things like automatic failover, Microsoft provides the mssql-server-ha package, which is similar to, but not exactly the same as the resource DLLs in a WSFC, for Pacemaker. One of the differences between a WSFC and Pacemaker is that there's no network name resource in Pacemaker, which is the component that helps to abstract the name of the listener (or the name of the FCI) on a WSFC. DNS provides that name resolution on Linux.
 
-Because of the difference in the cluster stack, some changes needed to be made for availability groups because SQL Server has to handle some of the metadata that is natively handled by a WSFC. The most [!IMPORTANT] change is the introduction of a cluster type for an availability group. This is stored in sys.availability_groups in the cluster_type and cluster_type_desc columns. There are three cluster types:
+Because of the difference in the cluster stack, some changes needed to be made for availability groups because SQL Server has to handle some of the metadata that is natively handled by a WSFC. **The most change is the introduction of a cluster type for an availability group.** This is stored in sys.availability_groups in the cluster_type and cluster_type_desc columns. There are three cluster types:
 
 * WSFC 
 * External
@@ -263,4 +263,4 @@ Instances and databases of SQL Server 2017 can be made highly available using th
 [AlwaysOnFCI]:media\sql-server-ha-story\image8.png
 [BasicDAG]:media\sql-server-ha-story\image9.png
 [image10]:media\sql-server-ha-story\image10.png
-[DAG]:media\sql-server-ha-story\image11.png
+[DAG]:media\sql-server-ha-story\image11.png