Acorlynx fixes

Author: jovanpop-msft

articles/sql-database/sql-database-service-tier-business-critical.md

@@ -41,12 +41,12 @@ In addition, Business Critical cluster has built-in [Read Scale-Out](sql-databas
 Business Critical service tier is designed for the applications that require low-latency responses from the underlying SSD storage (1-2 ms in average), fast recovery if the underlying infrastructure fails, or need to off-load reports, analytics, and read-only queries to the free of charge readable secondary replica of the primary database.
 
 The key reasons why you should choose Business Critical service tier instead of General Purpose tier are:
--	Low IO latency requirements – workload that need the fast response from the storage layer (less than 1-2 millisecond in average) should use Business Critical tier. 
+-	Low IO latency requirements – workload that needs the fast response from the storage layer (1-2 milliseconds in average) should use Business Critical tier. 
 -	Frequent communication between application and database. Application that cannot leverage application-layer caching or [request batching](sql-database-use-batching-to-improve-performance.md) and need to send many SQL queries that must be quickly processed are good candidates for Business Critical tier.
--	Large number of updates – insert, update, and delete operations modify the data pages in memory (dirty page) that must be saved to data files with `CHECKPOINT` operation. Potential database engine process crash or a failover of the database with a large number of dirty pages might increase recovery time in General Purpose tier. Use Business Critical tier if you have a workload that causes a lot of in-memory changes. 
--	Long running transactions that modify data. Transactions that are opened for a longer time prevent truncation of log file which might increase log size and number of [Virtual log files (VLF)](https://docs.microsoft.com/sql/relational-databases/sql-server-transaction-log-architecture-and-management-guide#physical_arch). High number of VLF can slow down recovery of database after failover.
+-	Large number of updates – insert, update, and delete operations modify the data pages in memory (dirty page) that must be saved to data files with `CHECKPOINT` operation. Potential database engine process crash or a failover of the database with a large number of dirty pages might increase recovery time in General Purpose tier. Use Business Critical tier if you have a workload that causes many in-memory changes. 
+-	Long running transactions that modify data. Transactions that are opened for a longer time prevent truncation of log file that might increase log size and number of [Virtual log files (VLF)](https://docs.microsoft.com/sql/relational-databases/sql-server-transaction-log-architecture-and-management-guide#physical_arch). High number of VLF can slow down recovery of database after failover.
 -	Workload with reporting and analytic queries that can be redirected to the free-of-charge secondary read-only replica.
-- Higher resiliency and faster recovery from the failures. In a case of system failure, the database on primary instance will be disabled and one of the secondary replica will be immediately became new read-write primary database that is ready to process the queries. Database engine don't need to analyze and redo transactions from the log file and load all data in the memory buffer.
+- Higher resiliency and faster recovery from the failures. In a case of system failure, the database on primary instance will be disabled and one of the secondary replicas will be immediately became new read-write primary database that is ready to process the queries. Database engine doesn't need to analyze and redo transactions from the log file and load all data in the memory buffer.
 - Advanced data corruption protection - Business Critical tier leverages database replicas behind-the-scenes for business continuity purposes, and so the service also then leverages automatic page repair, which is the same technology used for SQL Server database [mirroring and availability groups](https://docs.microsoft.com/sql/sql-server/failover-clusters/automatic-page-repair-availability-groups-database-mirroring). In the event that a replica cannot read a page due to a data integrity issue, a fresh copy of the page will be retrieved from another replica, replacing the unreadable page without data loss or customer downtime. This functionality is applicable in General Purpose tier if the database has geo-secondary replica.
 - Higher availability - Business Critical tier in Multi-AZ configuration guarantees 99.995% availability, compared to 99.99% of General Purpose tier.
 - Fast geo-recovery - Business Critical tier configured with geo-replication has a guaranteed Recovery point objective (RPO) of 5 sec and Recovery time objective (RTO) of 30 sec for 100% of deployed hours.