DOC-4367 implemented feedback

Author: andy-stark-redis

content/integrate/redis-data-integration/architecture.md

@@ -142,7 +142,8 @@ for more information.
 ### RDI on Kubernetes
 
 You can use the RDI [Helm chart](https://helm.sh/docs/topics/charts/) to install
-on [Kubernetes (K8s)](https://kubernetes.io/). This creates:
+on [Kubernetes (K8s)](https://kubernetes.io/), including Red Hat
+[OpenShift](https://docs.openshift.com/). This creates:
 
 -   A K8s [namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) named `rdi`.
 -   [Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) for the 

content/integrate/redis-data-integration/release-notes/rdi-1-4-0.md

@@ -37,5 +37,4 @@ It also lets you _transform_ the data from relational tables into convenient and
 
 ## Limitations
 
-- RDI can write data to a Redis Active-Active database. However, it doesn't support writing data to two or more Active-Active replicas. Writing data from RDI to several Active-Active replicas could easily harm data integrity as RDI is not synchronous with the source database commits.
-- RDI write-behind (which is currently in preview) should not be used on the same data set that RDI ingest is writing to Redis. This would either cause an infinite loop or would harm the data integrity, since both ingest and write-behind are asynchronous, eventually-consistent processes.
+RDI can write data to a Redis Active-Active database. However, it doesn't support writing data to two or more Active-Active replicas. Writing data from RDI to several Active-Active replicas could easily harm data integrity as RDI is not synchronous with the source database commits.