active voice edits

Author: kaitlynmichael

content/operate/kubernetes/reference/_index.md

@@ -11,15 +11,15 @@ linkTitle: Reference
 weight: 89
 ---
 
-Reference documentation for Redis Enterprise custom resources, including API specifications and practical guides for creating, configuring, and managing Redis Enterprise deployments on Kubernetes.
+This reference documentation covers Redis Enterprise custom resources, API specifications, and practical instructions for creating, configuring, and managing Redis Enterprise deployments on Kubernetes.
 
 ## Work with custom resources
 
-Redis Enterprise for Kubernetes uses custom resources to manage clusters and databases. You can create, modify, and delete these resources using standard Kubernetes tools.
+Redis Enterprise for Kubernetes uses custom resources to manage clusters and databases. Use standard Kubernetes tools to create, modify, and delete these resources.
 
 ### Create custom resources
 
-Create custom resources using `kubectl apply` with YAML manifests:
+Use `kubectl apply` with YAML manifests to create custom resources:
 
 ```bash
 kubectl apply -f my-redis-cluster.yaml
@@ -28,7 +28,7 @@ kubectl apply -f my-redis-database.yaml
 
 ### View custom resources
 
-List and inspect existing custom resources:
+Use these commands to list and inspect existing custom resources:
 
 ```bash
 # List Redis Enterprise clusters
@@ -50,7 +50,7 @@ kubectl describe redb my-database
 
 ### Modify custom resources
 
-Update custom resources by editing the YAML manifest and reapplying:
+Edit the YAML manifest and reapply to update custom resources:
 
 ```bash
 # Edit and apply updated manifest
@@ -63,7 +63,7 @@ kubectl edit redb my-database
 
 ## YAML examples
 
-Complete YAML examples for common deployment scenarios:
+Find complete YAML examples for common deployment scenarios:
 
 - [YAML examples]({{< relref "/operate/kubernetes/reference/yaml-examples" >}}) - Ready-to-use YAML configurations for different deployment types
 
@@ -76,30 +76,30 @@ Complete YAML examples for common deployment scenarios:
 
 ## API reference
 
-Complete API specifications for all Redis Enterprise custom resources:
+Review complete API specifications for all Redis Enterprise custom resources:
 
-Core resources:
+### Core resources
 
 - [Redis Enterprise cluster API (REC)]({{< relref "/operate/kubernetes/reference/redis_enterprise_cluster_api" >}}) - Manage Redis Enterprise clusters
 - [Redis Enterprise database API (REDB)]({{< relref "/operate/kubernetes/reference/redis_enterprise_database_api" >}}) - Manage Redis databases
 
-Active-Active resources:
+### Active-Active resources
 
 - [Active-Active database API (REAADB)]({{< relref "/operate/kubernetes/reference/redis_enterprise_active_active_database_api" >}}) - Manage Active-Active databases
 - [Remote cluster API (RERC)]({{< relref "/operate/kubernetes/reference/redis_enterprise_remote_cluster_api" >}}) - Configure remote cluster connections
 
 ## Compatibility
 
-Information about supported Kubernetes distributions and versions:
+Check supported Kubernetes distributions and versions:
 
 - [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) - Compatible Kubernetes platforms and versions
 
 ## Best practices
 
-When working with custom resources:
+Follow these best practices when working with custom resources:
 
 - **Use version control**: Store your YAML manifests in version control systems
 - **Validate before applying**: Use `kubectl apply --dry-run=client` to validate changes
-- **Monitor resource status**: Check resource status after applying changes
+- **Monitor resource status**: Check resource status after you apply changes
 - **Follow naming conventions**: Use consistent naming for easier management
 - **Document configurations**: Add annotations and labels to describe resource purpose

content/operate/kubernetes/reference/api/_index.md

@@ -12,7 +12,7 @@ hideListLinks: true
 aliases:
 ---
 
-The Redis Enterprise operator provides Kubernetes custom resource definitions (CRDs) that allow you to manage Redis Enterprise clusters and databases declaratively. This section contains the complete API reference for all operator resources.
+The Redis Enterprise operator provides Kubernetes custom resource definitions (CRDs) that let you manage Redis Enterprise clusters and databases declaratively. This section contains the complete API reference for all operator resources.
 
 ## API versions and stability
 
@@ -34,7 +34,7 @@ The operator uses different API versions to indicate stability and feature matur
 
 ### Using kubectl
 
-All resources can be managed using standard `kubectl` commands:
+Manage all resources using standard `kubectl` commands:
 
 ```bash
 # List all Redis Enterprise clusters
@@ -49,8 +49,8 @@ kubectl apply -f my-redis-config.yaml
 
 ### Resource relationships
 
-- A `RedisEnterpriseCluster` (REC) must be created first to provide the Redis Enterprise infrastructure
-- `RedisEnterpriseDatabase` (REDB) resources are created within a cluster to provision individual databases
-- `RedisEnterpriseActiveActiveDatabase` (REAADB) requires `RedisEnterpriseRemoteCluster (RERC)` resources to define participating clusters
+- Create a `RedisEnterpriseCluster` (REC) first to provide the Redis Enterprise infrastructure
+- Create `RedisEnterpriseDatabase` (REDB) resources within a cluster to provision individual databases
+- Use `RedisEnterpriseActiveActiveDatabase` (REAADB) with `RedisEnterpriseRemoteCluster (RERC)` resources to define participating clusters
 
 For complete YAML configuration examples, see the [YAML examples](../yaml/) section.

content/operate/kubernetes/reference/supported_k8s_distributions.md

@@ -10,7 +10,7 @@ linkTitle: Supported distributions
 weight: 10
 ---
 
-Each release of Redis Enterprise for Kubernetes is thoroughly tested against a set of Kubernetes distributions. The table below lists Redis Enterprise for Kubernetes versions and the Kubernetes distributions they support.
+We thoroughly test each release of Redis Enterprise for Kubernetes against a set of Kubernetes distributions. The table below lists Redis Enterprise for Kubernetes versions and the Kubernetes distributions they support.
 
 {{<note>}}x86 is currently the only computer architecture supported by Redis Enterprise for Kubernetes. Support for ARM architecture is coming in future releases.{{</note>}}
 

content/operate/kubernetes/reference/yaml/active-active.md

@@ -24,7 +24,7 @@ For complete deployment instructions, see [Active-Active databases]({{< relref "
 
 ## RERC for Chicago cluster
 
-Each participating cluster needs a RedisEnterpriseRemoteCluster (RERC) resource pointing to the other clusters.
+Create a RedisEnterpriseRemoteCluster (RERC) resource on each participating cluster that points to the other clusters.
 
 {{<embed-yaml "k8s/rerc.md" "redis-enterprise-remote-cluster.yaml">}}
 

content/operate/kubernetes/reference/yaml/basic-deployment.md

@@ -10,7 +10,7 @@ linkTitle: Basic deployment
 weight: 10
 ---
 
-This page provides complete YAML examples for a basic Redis Enterprise deployment on Kubernetes. These examples include all the essential components needed to deploy a Redis Enterprise cluster and create a database.
+This page provides complete YAML examples for a basic Redis Enterprise deployment on Kubernetes. These examples include all the essential components you need to deploy a Redis Enterprise cluster and create a database.
 
 For complete deployment instructions, see [Deploy on Kubernetes]({{< relref "/operate/kubernetes/deployment/quick-start" >}}).
 

content/operate/kubernetes/reference/yaml/log-collector-rbac.md

@@ -12,11 +12,11 @@ weight: 50
 
 This page provides YAML examples for configuring RBAC permissions for the Redis Enterprise log collector tool. The log collector requires different permission levels depending on the collection mode you choose.
 
-For complete log collection instructions, see [Collect logs guide]({{< relref "/operate/kubernetes/logs/collect-logs" >}}).
+For complete log collection instructions, see [Collect logs]({{< relref "/operate/kubernetes/logs/collect-logs" >}}).
 
 ## Prerequisites
 
-- [Redis Enterprise operator]({{< relref "/operate/kubernetes/deployment" >}}) must be installed
+- Install the [Redis Enterprise operator]({{< relref "/operate/kubernetes/deployment" >}})
 - Appropriate permissions to create RBAC resources in target namespaces
 - Understanding of your deployment model (single namespace, multi-namespace, etc.)
 

content/operate/kubernetes/reference/yaml/multi-namespace.md

@@ -10,7 +10,7 @@ linkTitle: Multi-namespace
 weight: 40
 ---
 
-Multi-namespace deployment allows a single Redis Enterprise operator to manage clusters and databases in different namespaces, providing better resource isolation and organization.
+Multi-namespace deployment lets a single Redis Enterprise operator manage clusters and databases in different namespaces, providing better resource isolation and organization.
 
 Multi-namespace deployment enables:
 - Namespace isolation: Separate Redis Enterprise resources by team, environment, or application
@@ -26,13 +26,13 @@ For complete deployment instructions, see [Manage databases in multiple namespac
 
 ## Operator service account
 
-These resources are deployed in the namespace where the Redis Enterprise operator runs.
+Deploy these resources in the namespace where the Redis Enterprise operator runs.
 
 {{<embed-yaml "k8s/service_account.md" "operator-service-account.yaml">}}
 
 ## Operator cluster role
 
-The operator needs cluster-wide permissions to manage resources across namespaces.
+Grant the operator cluster-wide permissions to manage resources across namespaces.
 
 {{<embed-yaml "k8s/multi-ns_operator_cluster_role.md" "operator-cluster-role.yaml">}}
 

content/operate/kubernetes/reference/yaml/rack-awareness.md

@@ -14,10 +14,10 @@ This page provides YAML examples for deploying Redis Enterprise with [rack aware
 
 ## Prerequisites
 
-- [Kubernetes nodes](https://kubernetes.io/docs/concepts/architecture/nodes/) must be labeled with zone information
+- Label [Kubernetes nodes](https://kubernetes.io/docs/concepts/architecture/nodes/) with zone information
 - Typically uses the standard label `topology.kubernetes.io/zone`
 - Verify node labels: `kubectl get nodes --show-labels`
-- [Redis Enterprise operator]({{< relref "/operate/kubernetes/deployment" >}}) must be installed
+- Install the [Redis Enterprise operator]({{< relref "/operate/kubernetes/deployment" >}})
 
 For complete deployment instructions, see [Deploy on Kubernetes]({{< relref "/operate/kubernetes/deployment" >}}).