Merge pull request #5811 from kendaleiv/patch-2

Small text fix

Author: ktoliver

docs/relational-databases/system-dynamic-management-views/sys-dm-geo-replication-link-status-azure-sql-database.md

@@ -34,7 +34,7 @@ ms.custom: seo-dt-2019
 |partner_database|**sysname**|Name of the linked database on the linked SQL Database server.|  
 |last_replication|**datetimeoffset**|The timestamp of the last transaction's acknowledgement by the secondary based on the primary database clock. This value is available on the primary database only.|  
 |replication_lag_sec|**int**|Time difference in seconds between the last_replication value and the timestamp of that transaction's commit on the primary based on the primary database clock.  This value is available on the primary database only.|  
-|replication_state|**tinyint**|The state of geo-replication for this database, one of:.<br /><br /> 1 = Seeding. The geo-replication target is being seeded but the two databases are not yet synchronized. Until seeding completes, you cannot connect to the secondary database. Removing secondary database from the primary will cancel the seeding operation.<br /><br /> 2 = Catch-up. The secondary database is  in a transactionally consistent state and is being constantly  synchronized with the primary database.<br /><br /> 4 = Suspended. This is not an active continuous-copy relationship. This state usually indicates that the bandwidth available for the interlink is insufficient for the level of transaction activity on the primary database. However, the continuous-copy relationship is still intact.|  
+|replication_state|**tinyint**|The state of geo-replication for this database, one of:<br /><br /> 1 = Seeding. The geo-replication target is being seeded but the two databases are not yet synchronized. Until seeding completes, you cannot connect to the secondary database. Removing secondary database from the primary will cancel the seeding operation.<br /><br /> 2 = Catch-up. The secondary database is  in a transactionally consistent state and is being constantly  synchronized with the primary database.<br /><br /> 4 = Suspended. This is not an active continuous-copy relationship. This state usually indicates that the bandwidth available for the interlink is insufficient for the level of transaction activity on the primary database. However, the continuous-copy relationship is still intact.|  
 |replication_state_desc|**nvarchar(256)**|PENDING<br /><br /> SEEDING<br /><br /> CATCH_UP|  
 |role|**tinyint**|Geo-replication role, one of:<br /><br /> 0 = Primary. The database_id  refers to the primary database in the geo-replication partnership.<br /><br /> 1 = Secondary.  The database_id  refers to the primary database in the geo-replication partnership.|  
 |role_desc|**nvarchar(256)**|PRIMARY<br /><br /> SECONDARY|