Apply suggestions from code review

Co-authored-by: Aishwarya Chakravarthy  <[email protected]>

docs/content/preview/admin/yb-ts-cli.md

@@ -106,7 +106,7 @@ yb-ts-cli [ --server_address=<host>:<port> ] compact_tablet <tablet_id>
 
 ##### count_intents
 
-Print the count of uncommitted intents (or [provisional records](../../../architecture/transactions/distributed-txns/#provisional-records)). Helpful for debugging transactional workloads.
+Print the count of uncommitted intents (or [provisional records](../../architecture/transactions/distributed-txns/#provisional-records)). Helpful for debugging transactional workloads.
 
 **Syntax**
 
@@ -118,7 +118,7 @@ yb-ts-cli  [ --server_address=<host>:<port> ] count_intents
 
 ##### current_hybrid_time
 
-Prints the value of the current [hybrid time](../../../architecture/transactions/transactions-overview/#mvcc-using-hybrid-time).
+Prints the value of the current [hybrid time](../../architecture/transactions/transactions-overview/#mvcc-using-hybrid-time).
 
 **Syntax**
 

docs/content/preview/architecture/docdb-replication/async-replication.md

@@ -146,7 +146,7 @@ Because of this restriction, xCluster does not need to do a deep translation of
 
 ### Supporting schema changes
 
-Today, this is a manual process where the exact same schema change must be manually made on first one side then the other.  Replication of the given table automatically pauses while schema differences are detected and resumes after the schemas are the same again.
+Currently, this is a manual process where the exact same schema change must be manually made on first one side then the other.  Replication of the given table automatically pauses while schema differences are detected and resumes after the schemas are the same again.
 
 Ongoing work, [#11537](https://github.com/yugabyte/yugabyte-db/issues/11537), will make this automatic: schema changes made on the source universe will automatically be replicated to the target universe and made, allowing replication to continue running without operator intervention.
 
@@ -226,7 +226,7 @@ Because of this applications using active-active should avoid `UNIQUE` indexes a
 
 In the future, it may be possible to detect such unsafe constraints and issue a warning, potentially by default.  This is tracked in [#11539](https://github.com/yugabyte/yugabyte-db/issues/11539).
 
-Note that if you attempt to insert the same row on both universes at the same time to a table that does not have a primary key then you will end up with two rows with the same data.  This is the expected PostgreSQL behavior — tables without primary keys can have multiple rows with the same data.
+Note that if you attempt to insert the same row on both universes at the same time to a table that does not have a primary key then you will end up with two rows with the same data. This is the expected PostgreSQL behavior — tables without primary keys can have multiple rows with the same data.
 
 ### Non-transactional–mode consistency issues