Clarify again

JamesFerebee · web-flow · commit e4baa7f25553 · 2023-03-22T16:48:52.000-05:00
diff --git a/articles/site-recovery/site-recovery-sql.md b/articles/site-recovery/site-recovery-sql.md
@@ -158,7 +158,7 @@ Site Recovery is application agnostic. Site Recovery can help protect any versio
 
 ### Does ASR Work with SQL Transasctional Replication?
 
-Due to ASR using file-level copy, SQL cannot guarantee the servers in an associated SQL Replication topology are in sync at the time of ASR failover. This may cause the logreader and/or distribution agents failing with LSN mismatches causing replication to break. Should you failover the publisher, distributor, or subscriber in a replication topology you will need to rebuild replication.
+Due to ASR using file-level copy, SQL cannot guarantee the servers in an associated SQL Replication topology are in sync at the time of ASR failover. This may cause the logreader and/or distribution agents to fail due to LSN mismatch which causes replication to break. Should you failover the publisher, distributor, or subscriber in a replication topology, you will need to rebuild replication.
 
 
 

Original file line number	Diff line number	Diff line change
`@@ -158,7 +158,7 @@ Site Recovery is application agnostic. Site Recovery can help protect any versio`
`158`	`158`
`159`	`159`	`### Does ASR Work with SQL Transasctional Replication?`
`160`	`160`
`161`		`-Due to ASR using file-level copy, SQL cannot guarantee the servers in an associated SQL Replication topology are in sync at the time of ASR failover. This may cause the logreader and/or distribution agents failing with LSN mismatches causing replication to break. Should you failover the publisher, distributor, or subscriber in a replication topology you will need to rebuild replication.`
	`161`	`+Due to ASR using file-level copy, SQL cannot guarantee the servers in an associated SQL Replication topology are in sync at the time of ASR failover. This may cause the logreader and/or distribution agents to fail due to LSN mismatch which causes replication to break. Should you failover the publisher, distributor, or subscriber in a replication topology, you will need to rebuild replication.`
`162`	`162`
`163`	`163`
`164`	`164`