Update sys-dm-hadr-database-replica-states-transact-sql.md

updated definition of Redo_Rate to change Rate to Average Rate.

Author: SQLSourabh

docs/relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md

@@ -1,7 +1,7 @@
 ---
 title: "sys.dm_hadr_database_replica_states (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "02/11/2018"
+ms.date: "06/26/2018"
 ms.prod: sql
 ms.reviewer: ""
 ms.suite: "sql"
@@ -63,7 +63,7 @@ manager: craigg
 |**log_send_queue_size**|**bigint**|Amount of log records of the primary database that has not been sent to the secondary databases, in kilobytes (KB).|  
 |**log_send_rate**|**bigint**|Average rate at which primary replica instance sent data during last active period, in kilobytes (KB)/second.|  
 |**redo_queue_size**|**bigint**|Amount of log records in the log files of the secondary replica that has not yet been redone, in kilobytes (KB).|  
-|**redo_rate**|**bigint**|Rate at which the log records are being redone on a given secondary database, in kilobytes (KB)/second.|  
+|**redo_rate**|**bigint**|Average Rate at which the log records are being redone on a given secondary database, in kilobytes (KB)/second.|  
 |**filestream_send_rate**|**bigint**|The rate at which the FILESTREAM files are shipped to the secondary replica, in kilobytes (KB)/second.|  
 |**end_of_log_lsn**|**numeric(25,0)**|Local end of log LSN. Actual LSN corresponding to the last log record in the log cache on the primary and secondary databases. On the primary replica, the secondary rows reflect the end of log LSN from the latest progress messages that the secondary replicas have sent to the primary replica.<br /><br /> **end_of_log_lsn** reflects a log-block ID padded with zeroes. It is not an actual log sequence number. For more information, see [Understanding the LSN Column Values](#LSNcolumns), later in this topic.|  
 |**last_commit_lsn**|**Numeric(25,0)**|Actual log sequence number corresponding to the last commit record in the transaction log.<br /><br /> On the primary database, this corresponds to the last commit record processed. Rows for secondary databases show the log sequence number that the secondary replica has sent to the primary replica.<br /><br /> On the secondary replica, this is the last commit record that was redone.|