Acrolinx fixes

Author: denrea

docs/database-engine/availability-groups/windows/monitor-performance-for-always-on-availability-groups.md

@@ -26,8 +26,8 @@ To estimate the time to full synchronization and to identify the bottleneck, you
 | Sequence | Step description | Comments | Useful metrics |
 | --- | --- | --- | --- |
 | 1 | Log generation | Log data is flushed to disk. This log must be replicated to the secondary replicas. The log records enter the send queue. | [SQL Server:Database > Log bytes flushed/sec](../../../relational-databases/performance-monitor/sql-server-databases-object.md) |
-| 2 | Capture | Logs for each database is captured and sent to the corresponding partner queue (one per database-replica pair). This capture process runs continuously as long as the availability replica is connected and data movement isn't suspended for any reason, and the database-replica pair is shown to be either Synchronizing or Synchronized. If the capture process isn't able to scan and enqueue the messages fast enough, the log send queue builds up. | [SQL Server:Availability Replica > Bytes Sent to Replica/sec](../../../relational-databases/performance-monitor/sql-server-availability-replica.md), which is an aggregation of the sum of all database messages queued for that availability replica.<br /><br />[log_send_queue_size](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md) (KB) and [log_bytes_send_rate](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md) (KB/sec) on the primary replica. |
-| 3 | Send | The messages in each database-replica queue is dequeued and sent across the wire to the respective secondary replica. | [SQL Server:Availability Replica > Bytes sent to transport/sec](../../../relational-databases/performance-monitor/sql-server-availability-replica.md) |
+| 2 | Capture | Logs for each database are captured and sent to the corresponding partner queue (one per database-replica pair). This capture process runs continuously as long as the availability replica is connected and data movement isn't suspended for any reason, and the database-replica pair is shown to be either Synchronizing or Synchronized. If the capture process isn't able to scan and enqueue the messages fast enough, the log send queue builds up. | [SQL Server:Availability Replica > Bytes Sent to Replica/sec](../../../relational-databases/performance-monitor/sql-server-availability-replica.md), which is an aggregation of the sum of all database messages queued for that availability replica.<br /><br />[log_send_queue_size](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md) (KB) and [log_bytes_send_rate](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md) (KB/sec) on the primary replica. |
+| 3 | Send | The messages in each database-replica queue are dequeued and sent across the wire to the respective secondary replica. | [SQL Server:Availability Replica > Bytes sent to transport/sec](../../../relational-databases/performance-monitor/sql-server-availability-replica.md) |
 | 4 | Receive and cache | Each secondary replica receives and caches the message. | Performance counter [SQL Server:Availability Replica > Log Bytes Received/sec](../../../relational-databases/performance-monitor/sql-server-availability-replica.md) |
 | 5 | Harden | Log is flushed on the secondary replica for hardening. After the log flush, an acknowledgment is sent back to the primary replica.<br /><br />Once the log is hardened, data loss is avoided. | Performance counter [SQL Server:Database > Log Bytes Flushed/sec](../../../relational-databases/performance-monitor/sql-server-databases-object.md)<br />Wait type [HADR_LOGCAPTURE_SYNC](../../../relational-databases/system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql.md) |
 | 6 | Redo | Redo the flushed pages on the secondary replica. Pages are kept in the redo queue as they wait to be redone. | [SQL Server:Database Replica > Redone Bytes/sec](../../../relational-databases/performance-monitor/sql-server-database-replica.md)<br /><br />[redo_queue_size](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md) (KB) and [redo_rate](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md).<br />Wait type [REDO_SYNC](../../../relational-databases/system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql.md) |