Apply suggestions from code review

Co-authored-by: David Dougherty <[email protected]>

Author: kaitlynmichael

content/operate/kubernetes/networking/_index.md

@@ -17,7 +17,7 @@ Configure networking and external access for your Redis Enterprise deployment on
 
 Connect applications to your Redis Enterprise databases:
 
-- [Database connectivity]({{< relref "/operate/kubernetes/networking/database-connectivity" >}}) - Comprehensive guide to in-cluster and external database access, service discovery, and credentials management
+- [Database connectivity]({{< relref "/operate/kubernetes/networking/database-connectivity" >}}) - Comprehensive guide to in-cluster and external database access, service discovery, and credentials management.
 
 ## External routing methods
 

content/operate/kubernetes/networking/database-connectivity.md

@@ -20,8 +20,8 @@ When you create a RedisEnterpriseDatabase (REDB), the Redis Enterprise operator
 
 By default, the operator creates two services for each database:
 
-- ClusterIP service - Provides a stable cluster-internal IP address
-- Headless service - Enables direct pod-to-pod communication and service discovery
+- ClusterIP service - Provides a stable cluster-internal IP address.
+- Headless service - Enables direct pod-to-pod communication and service discovery.
 
 Both services are created in the same namespace as your database and follow predictable naming conventions.
 
@@ -139,9 +139,9 @@ See [OpenShift routes]({{< relref "/operate/kubernetes/networking/routes" >}}) f
 
 ### Default port behavior
 
-- Redis Enterprise databases use dynamic port allocation
-- Port numbers are assigned automatically during database creation
-- The actual port is stored in the database secret
+- Redis Enterprise databases use dynamic port allocation.
+- Port numbers are assigned automatically during database creation.
+- The actual port is stored in the database secret.
 
 ### Custom port configuration
 
@@ -264,10 +264,10 @@ client.on('connect', () => {
 
 ### Common issues
 
-1. Connection refused - Verify service names and ports from the database secret
-2. Authentication failed - Check password encoding and special characters
-3. DNS resolution - Ensure applications use correct service FQDNs
-4. Network policies - Verify Kubernetes network policies allow traffic
+1. Connection refused - Verify service names and ports from the database secret.
+2. Authentication failed - Check password encoding and special characters.
+3. DNS resolution - Ensure applications use correct service FQDNs.
+4. Network policies - Verify Kubernetes network policies allow traffic.
 
 ### Debugging steps
 

content/operate/kubernetes/re-databases/_index.md

@@ -37,7 +37,7 @@ Explore advanced database features and configurations:
 
 Connect applications to your Redis Enterprise databases:
 
-- [Database connectivity]({{< relref "/operate/kubernetes/networking/database-connectivity" >}}) - Comprehensive guide to in-cluster and external database access, service discovery, and credentials management
+- [Database connectivity]({{< relref "/operate/kubernetes/networking/database-connectivity" >}}) - Comprehensive guide to in-cluster and external database access, service discovery, and credentials management.
 - [Networking]({{< relref "/operate/kubernetes/networking" >}}) - Configure ingress, routes, and service exposure for database access
 - [Security]({{< relref "/operate/kubernetes/security" >}}) - Set up TLS, authentication, and access control for secure database connections
 

content/operate/kubernetes/security/configuration-secrets.md

@@ -81,11 +81,11 @@ kubectl create secret generic <secret-name> \
 
 ## Best practices
 
-- Store sensitive configuration in Secrets rather than directly in YAML files
-- Use `--from-file` to avoid manual base64 encoding
-- Create secrets in the same namespace as your REC or REDB resources
-- Use descriptive secret names for easy identification
-- Regularly rotate certificates and update secrets
+- Store sensitive configuration in Secrets rather than directly in YAML files.
+- Use `--from-file` to avoid manual base64 encoding.
+- Create secrets in the same namespace as your REC or REDB resources.
+- Use descriptive secret names for easy identification.
+- Regularly rotate certificates and update secrets.
 
 ## See also