DOC-6738 removed mention of Active-active as a source DB

content/embeds/rdi-when-to-use-dec-tree.md

@@ -39,7 +39,7 @@ questions:
         text: |
             Are you transferring data from a single source database?
         whyAsk: |
-            RDI is designed to work with a single source database. Multiple sources or Active-Active replicas create conflicting change events.
+            RDI is designed to work with a single source database. Multiple sources create conflicting change events.
         answers:
             no:
                 value: "No"

content/embeds/rdi-when-to-use.md

@@ -35,7 +35,6 @@ RDI is not a good fit when:
 - Your app needs *immediate* cache consistency (or a hard limit on latency) rather
   than *eventual* consistency.
 - You need *transactional* consistency between the source and target databases.
-- The data is ingested from two replicas of Active-Active at the same time.
 - The app must *write* data to the Redis cache, which then updates the source database
   (write-behind/write-through patterns).
 - Your data set will only ever be small.

content/operate/rc/rdi/_index.md

@@ -76,7 +76,6 @@ RDI is not a good fit when:
 - Your app needs *immediate* cache consistency (or a hard limit on latency) rather
   than *eventual* consistency.
 - You need *transactional* consistency between the source and target databases.
-- The data is ingested from two replicas of Active-Active at the same time.
 - The app must *write* data to the Redis cache, which then updates the source database
   (write-behind/write-through patterns).
 - Your data set will only ever be small.