Update docs/content/en/install/eks/_index.md

Co-authored-by: annieden <[email protected]>

docs/content/en/install/eks/_index.md

@@ -31,7 +31,7 @@ Apache Cassandra can be deployed across a variety of [hardware profiles](https:/
 
 ## Installation Type
 
-K8ssandra Operator may be deployed in one of two modes. `Control Plane` mode is the default method of installation. In this mode K8ssandra Operator watches for the creation and changes to `K8ssandraCluster` custom resources. When this mode is active it may create Cassandra resources within the local Kubernetes cluster **and / or** remote Kubernetes clusters (in the case of multi-region) deployments. When using K8ssandra Operator you should only have one instance running in `Control Plane` mode. Kubernetes clusters acting as remote regions for Cassandra deployments should be run in `Data Plane` mode. In this mode K8ssandra Operator will not directly reconcile `K8ssandraCluster` resources.
+K8ssandra Operator may be deployed in one of two modes. `Control Plane` mode is the default method of installation. A `Control Plane` instance of K8ssandra Operator watches for the creation and changes to `K8ssandraCluster` custom resources. When `Control Plane` is active Cassandra resources may be created within the local Kubernetes cluster **and / or** remote Kubernetes clusters (in the case of multi-region) deployments. When using K8ssandra Operator you should only have one instance running in `Control Plane` mode. Kubernetes clusters acting as remote regions for Cassandra deployments should be run in `Data Plane` mode. In `Data Plane` mode K8ssandra Operator does not directly reconcile `K8ssandraCluster` resources.
 
 For example consider the following scenarios: