From 74ea418a1505c5d7ae513caab2443b144f4db64d Mon Sep 17 00:00:00 2001 From: Rachel Elledge Date: Fri, 27 Jun 2025 16:59:50 -0500 Subject: [PATCH] DOC-5393 RS: Fixed typos and links in develop Active-Active Redis apps docs --- .../databases/active-active/develop/_index.md | 18 +++++++++--------- .../active-active/develop/data-types/_index.md | 4 ++-- .../databases/active-active/develop/_index.md | 18 +++++++++--------- .../active-active/develop/data-types/_index.md | 4 ++-- .../databases/active-active/develop/_index.md | 18 +++++++++--------- .../active-active/develop/data-types/_index.md | 4 ++-- 6 files changed, 33 insertions(+), 33 deletions(-) diff --git a/content/operate/rs/7.4/databases/active-active/develop/_index.md b/content/operate/rs/7.4/databases/active-active/develop/_index.md index a7069cfe21..f9ef41ffdf 100644 --- a/content/operate/rs/7.4/databases/active-active/develop/_index.md +++ b/content/operate/rs/7.4/databases/active-active/develop/_index.md @@ -19,9 +19,9 @@ of events under geo-failovers and cross-region write conflicts. In Redis Enterpr simplify developing such applications by directly using built-in smarts for handling conflicting writes based on the data type in use. Instead of depending on just simplistic "last-writer-wins" type conflict -resolution, geo-distributed Active-Active databases (formerly known as CRDBs) combines techniques defined in CRDT +resolution, geo-distributed Active-Active databases (formerly known as CRDBs) combine techniques defined in CRDT (conflict-free replicated data types) research with Redis types to -provide smart and automatic conflict resolution based on the data types +provide smart and automatic conflict resolution based on the data type's intent. An Active-Active database is a globally distributed database that spans multiple Redis @@ -32,8 +32,8 @@ using the proven approach. [CRDT](https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type) research describes a set of techniques for creating systems that can -handle conflicting writes. CRDBs are powered by Multi-Master Replication -(MMR) provides a straightforward and effective way to replicate your +handle conflicting writes. CRDBs powered by Multi-Master Replication +(MMR) provide a straightforward and effective way to replicate your data between regions and simplify development of complex applications that can maintain correctness under geo-failovers and concurrent cross-region writes to the same data. @@ -43,14 +43,14 @@ cross-region writes to the same data. Active-Active databases replicate data between multiple Redis Enterprise Software clusters. Common uses for Active-Active databases include disaster recovery, geographically redundant applications, and keeping data closer to your -user's locations. MMR is always multi-directional amongst the clusters +users' locations. MMR is always multi-directional amongst the clusters configured in the Active-Active database. For unidirectional replication, please see the Replica Of capabilities in Redis Enterprise Software. ## Example of synchronization -In the example below, database writes are concurrent at the point in -times t1 and t2 and happen before a sync can communicate the changes. +In the example below, database writes are concurrent at the points in +time t1 and t2 and happen before a sync can communicate the changes. However, writes at times t4 and t6 are not concurrent as a sync happened in between. @@ -64,5 +64,5 @@ in between. | t6 | | SET key1 “d” | [Learn more about -synchronization]({{< relref "/operate/rs/7.4/databases/active-active" >}}) for -each supported data type and [how to develop]({{< relref "/operate/rs/7.4/databases/active-active/develop/develop-for-aa.md" >}}) with them on Redis Enterprise Software. +synchronization for +each supported data type]({{< relref "/operate/rs/7.4/databases/active-active/develop/data-types/" >}}) and [how to develop applications]({{< relref "/operate/rs/7.4/databases/active-active/develop/develop-for-aa.md" >}}) with them on Redis Enterprise Software. diff --git a/content/operate/rs/7.4/databases/active-active/develop/data-types/_index.md b/content/operate/rs/7.4/databases/active-active/develop/data-types/_index.md index b373c70502..534479ecb6 100644 --- a/content/operate/rs/7.4/databases/active-active/develop/data-types/_index.md +++ b/content/operate/rs/7.4/databases/active-active/develop/data-types/_index.md @@ -8,7 +8,7 @@ categories: - rc description: Introduction to differences in data types between standalone and Active-Active Redis databases. -hideListLinks: true +hideListLinks: false linktitle: Data types weight: 90 url: '/operate/rs/7.4/databases/active-active/develop/data-types/' @@ -22,5 +22,5 @@ conflicting concurrent writes for each data type. As conflict handling rules differ between data types, some commands have slightly different requirements in Active-Active databases versus standard Redis databases. -See the following articles for more information +See the following articles for more information. diff --git a/content/operate/rs/7.8/databases/active-active/develop/_index.md b/content/operate/rs/7.8/databases/active-active/develop/_index.md index 0894fd54f2..afea33fc79 100644 --- a/content/operate/rs/7.8/databases/active-active/develop/_index.md +++ b/content/operate/rs/7.8/databases/active-active/develop/_index.md @@ -19,9 +19,9 @@ of events under geo-failovers and cross-region write conflicts. In Redis Enterpr simplify developing such applications by directly using built-in smarts for handling conflicting writes based on the data type in use. Instead of depending on just simplistic "last-writer-wins" type conflict -resolution, geo-distributed Active-Active databases (formerly known as CRDBs) combines techniques defined in CRDT +resolution, geo-distributed Active-Active databases (formerly known as CRDBs) combine techniques defined in CRDT (conflict-free replicated data types) research with Redis types to -provide smart and automatic conflict resolution based on the data types +provide smart and automatic conflict resolution based on the data type's intent. An Active-Active database is a globally distributed database that spans multiple Redis @@ -32,8 +32,8 @@ using the proven approach. [CRDT](https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type) research describes a set of techniques for creating systems that can -handle conflicting writes. CRDBs are powered by Multi-Master Replication -(MMR) provides a straightforward and effective way to replicate your +handle conflicting writes. CRDBs powered by Multi-Master Replication +(MMR) provide a straightforward and effective way to replicate your data between regions and simplify development of complex applications that can maintain correctness under geo-failovers and concurrent cross-region writes to the same data. @@ -43,14 +43,14 @@ cross-region writes to the same data. Active-Active databases replicate data between multiple Redis Enterprise Software clusters. Common uses for Active-Active databases include disaster recovery, geographically redundant applications, and keeping data closer to your -user's locations. MMR is always multi-directional amongst the clusters +users' locations. MMR is always multi-directional amongst the clusters configured in the Active-Active database. For unidirectional replication, please see the Replica Of capabilities in Redis Enterprise Software. ## Example of synchronization -In the example below, database writes are concurrent at the point in -times t1 and t2 and happen before a sync can communicate the changes. +In the example below, database writes are concurrent at the points in +time t1 and t2 and happen before a sync can communicate the changes. However, writes at times t4 and t6 are not concurrent as a sync happened in between. @@ -64,5 +64,5 @@ in between. | t6 | | SET key1 “d” | [Learn more about -synchronization]({{< relref "/operate/rs/7.8/databases/active-active" >}}) for -each supported data type and [how to develop]({{< relref "/operate/rs/7.8/databases/active-active/develop/develop-for-aa.md" >}}) with them on Redis Enterprise Software. +synchronization for +each supported data type]({{< relref "/operate/rs/7.8/databases/active-active/develop/data-types/" >}}) and [how to develop applications]({{< relref "/operate/rs/7.8/databases/active-active/develop/develop-for-aa.md" >}}) with them on Redis Enterprise Software. diff --git a/content/operate/rs/7.8/databases/active-active/develop/data-types/_index.md b/content/operate/rs/7.8/databases/active-active/develop/data-types/_index.md index 09282d4972..a753275ef2 100644 --- a/content/operate/rs/7.8/databases/active-active/develop/data-types/_index.md +++ b/content/operate/rs/7.8/databases/active-active/develop/data-types/_index.md @@ -8,7 +8,7 @@ categories: - rc description: Introduction to differences in data types between standalone and Active-Active Redis databases. -hideListLinks: true +hideListLinks: false linktitle: Data types weight: 90 url: '/operate/rs/7.8/databases/active-active/develop/data-types/' @@ -22,5 +22,5 @@ conflicting concurrent writes for each data type. As conflict handling rules differ between data types, some commands have slightly different requirements in Active-Active databases versus standard Redis databases. -See the following articles for more information +See the following articles for more information. diff --git a/content/operate/rs/databases/active-active/develop/_index.md b/content/operate/rs/databases/active-active/develop/_index.md index 5a03d0dd00..0d20bd84fe 100644 --- a/content/operate/rs/databases/active-active/develop/_index.md +++ b/content/operate/rs/databases/active-active/develop/_index.md @@ -18,9 +18,9 @@ of events under geo-failovers and cross-region write conflicts. In Redis Enterpr simplify developing such applications by directly using built-in smarts for handling conflicting writes based on the data type in use. Instead of depending on just simplistic "last-writer-wins" type conflict -resolution, geo-distributed Active-Active databases (formerly known as CRDBs) combines techniques defined in CRDT +resolution, geo-distributed Active-Active databases (formerly known as CRDBs) combine techniques defined in CRDT (conflict-free replicated data types) research with Redis types to -provide smart and automatic conflict resolution based on the data types +provide smart and automatic conflict resolution based on the data type's intent. An Active-Active database is a globally distributed database that spans multiple Redis @@ -31,8 +31,8 @@ using the proven approach. [CRDT](https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type) research describes a set of techniques for creating systems that can -handle conflicting writes. CRDBs are powered by Multi-Master Replication -(MMR) provides a straightforward and effective way to replicate your +handle conflicting writes. CRDBs powered by Multi-Master Replication +(MMR) provide a straightforward and effective way to replicate your data between regions and simplify development of complex applications that can maintain correctness under geo-failovers and concurrent cross-region writes to the same data. @@ -42,14 +42,14 @@ cross-region writes to the same data. Active-Active databases replicate data between multiple Redis Enterprise Software clusters. Common uses for Active-Active databases include disaster recovery, geographically redundant applications, and keeping data closer to your -user's locations. MMR is always multi-directional amongst the clusters +users' locations. MMR is always multi-directional amongst the clusters configured in the Active-Active database. For unidirectional replication, please see the Replica Of capabilities in Redis Enterprise Software. ## Example of synchronization -In the example below, database writes are concurrent at the point in -times t1 and t2 and happen before a sync can communicate the changes. +In the example below, database writes are concurrent at the points in +time t1 and t2 and happen before a sync can communicate the changes. However, writes at times t4 and t6 are not concurrent as a sync happened in between. @@ -63,5 +63,5 @@ in between. | t6 | | SET key1 “d” | [Learn more about -synchronization]({{< relref "/operate/rs/databases/active-active" >}}) for -each supported data type and [how to develop]({{< relref "/operate/rs/databases/active-active/develop/develop-for-aa.md" >}}) with them on Redis Enterprise Software. +synchronization for +each supported data type]({{< relref "/operate/rs/databases/active-active/develop/data-types/" >}}) and [how to develop applications]({{< relref "/operate/rs/databases/active-active/develop/develop-for-aa.md" >}}) with them on Redis Enterprise Software. diff --git a/content/operate/rs/databases/active-active/develop/data-types/_index.md b/content/operate/rs/databases/active-active/develop/data-types/_index.md index 5d20a646b1..b83ad9c245 100644 --- a/content/operate/rs/databases/active-active/develop/data-types/_index.md +++ b/content/operate/rs/databases/active-active/develop/data-types/_index.md @@ -8,7 +8,7 @@ categories: - rc description: Introduction to differences in data types between standalone and Active-Active Redis databases. -hideListLinks: true +hideListLinks: false linktitle: Data types weight: 90 --- @@ -21,5 +21,5 @@ conflicting concurrent writes for each data type. As conflict handling rules differ between data types, some commands have slightly different requirements in Active-Active databases versus standard Redis databases. -See the following articles for more information +See the following articles for more information.