Remove unnecessary 'File:' labels from YAML examples

- Removed 'File: filename.yaml' labels from all YAML examples across all pages
- YAML examples are self-explanatory and don't need explicit file labels
- Fixed duplicate 'Customization options' headings in basic-deployment.md
- Renamed to 'Cluster customization options' and 'Database customization options'
- Cleaner, more focused presentation of YAML configurations

Author: kaitlynmichael

content/operate/kubernetes/logs/log-collector-rbac.md

@@ -55,8 +55,6 @@ The key differences between the two modes:
 
 Use restricted mode for minimal security exposure while still collecting essential Redis Enterprise diagnostics.
 
-**File: `log-collector-restricted-rbac.yaml`**
-
 {{<embed-md "k8s/log_collector_role_restricted_mode.md">}}
 
 ### Restricted mode permissions
@@ -83,8 +81,6 @@ The restricted mode provides access to:
 
 Use all mode when you need comprehensive cluster diagnostics or when specifically requested by Redis Support.
 
-**File: `log-collector-all-rbac.yaml`**
-
 {{<embed-md "k8s/log_collector_role_all_mode.md">}}
 
 ### All mode additional permissions
@@ -103,8 +99,6 @@ In addition to all restricted mode permissions, all mode provides:
 
 Bind the Role to your service account in each namespace where you want to collect logs.
 
-**File: `log-collector-role-binding.yaml`**
-
 ```yaml
 apiVersion: rbac.authorization.k8s.io/v1
 kind: RoleBinding
@@ -125,8 +119,6 @@ roleRef:
 
 Bind the ClusterRole to your service account for cluster-wide permissions.
 
-**File: `log-collector-cluster-role-binding.yaml`**
-
 ```yaml
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding

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

@@ -39,8 +39,6 @@ This example shows a two-cluster Active-Active setup:
 
 Each participating cluster needs a RedisEnterpriseRemoteCluster (RERC) resource pointing to the other clusters.
 
-**File: `rerc-chicago.yaml`** (applied on Boston cluster)
-
 {{<embed-md "k8s/rerc.md">}}
 
 ### RERC configuration
@@ -76,8 +74,6 @@ spec:
 
 ## RERC for Boston cluster
 
-**File: `rerc-boston.yaml`** (applied on Chicago cluster)
-
 ```yaml
 apiVersion: app.redislabs.com/v1alpha1
 kind: RedisEnterpriseRemoteCluster
@@ -95,8 +91,6 @@ spec:
 
 The RedisEnterpriseActiveActiveDatabase (REAADB) resource defines the Active-Active database.
 
-**File: `active-active-database.yaml`**
-
 {{<embed-md "k8s/reaadb.md">}}
 
 ### REAADB configuration

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

@@ -26,8 +26,6 @@ Apply the YAML files in this order:
 
 The service account provides an identity for the Redis Enterprise operator.
 
-**File: `service-account.yaml`**
-
 {{<embed-md "k8s/service_account.md">}}
 
 ### Service account configuration
@@ -39,8 +37,6 @@ The service account provides an identity for the Redis Enterprise operator.
 
 The Role defines the permissions needed by the Redis Enterprise operator within the namespace.
 
-**File: `role.yaml`**
-
 {{<embed-md "k8s/role.md">}}
 
 ### Role configuration
@@ -61,8 +57,6 @@ The Role defines the permissions needed by the Redis Enterprise operator within
 
 The RoleBinding connects the service account to the role, granting the necessary permissions.
 
-**File: `role-binding.yaml`**
-
 {{<embed-md "k8s/role_binding.md">}}
 
 ### Role binding configuration
@@ -75,8 +69,6 @@ The RoleBinding connects the service account to the role, granting the necessary
 
 The RedisEnterpriseCluster (REC) custom resource defines the cluster specification.
 
-**File: `redis-cluster.yaml`**
-
 {{<embed-md "k8s/rec.md">}}
 
 ### Cluster configuration
@@ -86,19 +78,19 @@ The RedisEnterpriseCluster (REC) custom resource defines the cluster specificati
 - **persistentSpec.volumeSize**: Storage size per node
 - **redisEnterpriseNodeResources**: CPU and memory allocation per node
 
-### Customization options
+### Cluster customization options
 
 Edit these values based on your requirements:
 
 ```yaml
 spec:
   # Increase nodes for larger clusters
   nodes: 5
-  
+
   # Adjust storage size
   persistentSpec:
     volumeSize: 50Gi
-  
+
   # Modify resource allocation
   redisEnterpriseNodeResources:
     requests:
@@ -113,8 +105,6 @@ spec:
 
 The RedisEnterpriseDatabase (REDB) custom resource defines the database specification.
 
-**File: `redis-database.yaml`**
-
 {{<embed-md "k8s/redb.md">}}
 
 ### Database configuration
@@ -124,21 +114,21 @@ The RedisEnterpriseDatabase (REDB) custom resource defines the database specific
 - **spec.shardCount**: Number of shards (affects performance and scalability)
 - **spec.replication**: Enable/disable database replication
 
-### Customization options
+### Database customization options
 
 Edit these values based on your requirements:
 
 ```yaml
 spec:
   # Increase memory for larger datasets
   memorySize: 1GB
-  
+
   # Add more shards for better performance
   shardCount: 3
-  
+
   # Enable replication for high availability
   replication: true
-  
+
   # Add database-specific configuration
   redisEnterpriseConfiguration:
     # Enable specific Redis modules

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

@@ -43,30 +43,22 @@ Apply the YAML files in this order:
 
 These resources are deployed in the namespace where the Redis Enterprise operator runs.
 
-**File: `operator-service-account.yaml`**
-
 {{<embed-md "k8s/service_account.md">}}
 
 ## Operator cluster role
 
 The operator needs cluster-wide permissions to manage resources across namespaces.
 
-**File: `operator-cluster-role.yaml`**
-
 {{<embed-md "k8s/multi-ns_operator_cluster_role.md">}}
 
 ## Operator cluster role binding
 
-**File: `operator-cluster-role-binding.yaml`**
-
 {{<embed-md "k8s/multi-ns_operator_cluster_role_binding.md">}}
 
 ## Consumer service account
 
 These resources are deployed in each namespace where you want to create Redis Enterprise clusters or databases.
 
-**File: `consumer-service-account.yaml`**
-
 ```yaml
 apiVersion: v1
 kind: ServiceAccount
@@ -78,14 +70,10 @@ metadata:
 
 ## Consumer role
 
-**File: `consumer-role.yaml`**
-
 {{<embed-md "k8s/multi-ns_role.md">}}
 
 ## Consumer role binding
 
-**File: `consumer-role-binding.yaml`**
-
 {{<embed-md "k8s/multi-ns_role_binding.md">}}
 
 ### Consumer namespace configuration

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

@@ -39,16 +39,12 @@ Apply the YAML files in this order:
 
 The service account for rack-aware deployments is the same as basic deployments.
 
-**File: `service-account.yaml`**
-
 {{<embed-md "k8s/service_account.md">}}
 
 ## Cluster role
 
 Rack awareness requires additional permissions to read node labels across the cluster.
 
-**File: `cluster-role.yaml`**
-
 {{<embed-md "k8s/rack_aware_cluster_role.md">}}
 
 ### Cluster role configuration
@@ -66,8 +62,6 @@ Rack awareness requires additional permissions to read node labels across the cl
 
 The ClusterRoleBinding grants cluster-wide permissions to the service account.
 
-**File: `cluster-role-binding.yaml`**
-
 {{<embed-md "k8s/rack_aware_cluster_role_binding.md">}}
 
 ### Cluster role binding configuration
@@ -80,8 +74,6 @@ The ClusterRoleBinding grants cluster-wide permissions to the service account.
 
 The rack-aware REC configuration includes the `rackAwarenessNodeLabel` field.
 
-**File: `rack-aware-cluster.yaml`**
-
 {{<embed-md "k8s/rack_aware_rec.md">}}
 
 ### Rack-aware cluster configuration
@@ -135,8 +127,6 @@ kubectl get nodes -o custom-columns=NAME:.metadata.name,ZONE:.metadata.labels.'t
 
 Database configuration for rack-aware clusters is the same as basic deployments.
 
-**File: `redis-database.yaml`**
-
 {{<embed-md "k8s/redb.md">}}
 
 ### Rack awareness benefits