Update per feedback from @v-thepet

Author: MikeRayMSFT

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

@@ -1,4 +1,4 @@
-## Introduction
+This article provides an overview of business continuity solutions for high availability and disaster recovery in SQL Server. 
 
 One common task everyone deploying SQL Server has to account for is making sure that all mission critical SQL Server instances and the databases within them are available when the business and end users need them, whether that is 9 to 5 or around the clock. The goal is to keep the business up and running with minimal or no interruption. This concept is also known as business continuity.
 
@@ -134,7 +134,7 @@ If recovery point and recovery time objectives are more flexible, or databases a
 
 ![Log Shipping][LogShipping]
 
-Arguably the biggest advantavailability groupe to using log shipping in some capacity is that it accounts for human error. The application of transaction logs can be delayed. Therefore, if someone issues something like an UPDATE without a WHERE clause, the standby may not have the change so you could switch to that while you repair the primary system. While log shipping is easy to configure, switching from the primary to a warm standby, known as a role change, is always manual. A role change is initiated via Transact-SQL, and like an availability group, all objects not captured in the transaction log must be manually synchronized. Log shipping also needs to be configured per database, whereas a single availability group can contain multiple databases. 
+Arguably the biggest advantage of using log shipping in some capacity is that it accounts for human error. The application of transaction logs can be delayed. Therefore, if someone issues something like an UPDATE without a WHERE clause, the standby may not have the change so you could switch to that while you repair the primary system. While log shipping is easy to configure, switching from the primary to a warm standby, known as a role change, is always manual. A role change is initiated via Transact-SQL, and like an availability group, all objects not captured in the transaction log must be manually synchronized. Log shipping also needs to be configured per database, whereas a single availability group can contain multiple databases. 
 Unlike an availability group or FCI, log shipping has no abstraction for a role change. Applications must be able to handle this. Techniques such as a DNS alias (CNAME) could be employed, but there are pros and cons, such as the time it takes for DNS to refresh after the switch.
 
 ## Disaster recovery

docs/linux/sql-server-linux-business-continuity-dr.md

@@ -10,6 +10,6 @@ ms.prod: sql-linux
 ms.technology: database-engine
 ms.assetid: c75717c8-c677-4033-8ca6-d0ac93aee04d
 ---
-# Business continuity and database recovery ~ SQL Server on Linux
+# Business continuity and database recovery - SQL Server on Linux
 
 [!INCLUDE[HA-Story](../includes/sql-server-ha-story.md)]