Update storage-classes.mdx

Author: joaniekube

vcluster/configure/vcluster-yaml/sync/from-host/storage-classes.mdx

@@ -46,7 +46,7 @@ When StorageClass sync is enabled, vCluster uses selector criteria to control wh
 
 **Unified selector control**: The same selector determines which StorageClass resources are imported into the virtual cluster and which PersistentVolume and PersistentVolumeClaim resources can sync to the host cluster. If a PersistentVolumeClaim references a StorageClass that was not synced to the virtual cluster, that PersistentVolumeClaim cannot sync to the host cluster.
 
-## Using selectors to filter StorageClasses
+## Use selectors to filter StorageClasses
 
 Selectors provide precise control over which StorageClass resources get synced from the host cluster. vCluster supports two types of selector criteria that follow standard Kubernetes label selector syntax.
 
@@ -63,9 +63,9 @@ All specified label conditions must match for a StorageClass to be included in t
 
 For more details on label selectors, refer to the [Kubernetes documentation on label selectors](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#resources-that-support-set-based-requirements).
 
-## Sync behavior and considerations
+## Sync behavior considerations
 
-### Resource lifecycle and validation
+### Resource lifecycle
 
 Synced StorageClass resources function like any other Kubernetes resource in the virtual cluster. You can view them with `kubectl get storageclass` and reference them in PersistentVolumeClaim specifications using the storageClassName field.
 
@@ -83,7 +83,7 @@ When a StorageClass fails to meet the selector criteria during evaluation, vClus
 
 The error output appears as a Kubernetes event that you can view using `kubectl describe`.
 
-### Orphaned resources and cleanup
+### Remove orphaned resources
 
 When vCluster removes a synced StorageClass from the virtual cluster due to selector changes or deletion from the host cluster, any PersistentVolume and PersistentVolumeClaim resources that reference it remain in the virtual cluster. These orphaned resources stop receiving updates but vCluster does not automatically delete them to prevent unintended data loss. To remove these orphaned resources, you must delete them manually in the host cluster.
 
@@ -93,7 +93,7 @@ When vCluster removes a synced StorageClass from the virtual cluster due to sele
 
 To sync only StorageClass resources labeled `environment: development`:
 
-```yaml title="Filter example for storageClass"
+```yaml title="Filter example for StorageClass"
 sync:
   toHost:
     persistentVolumes:
@@ -112,7 +112,7 @@ sync:
 
 To sync StorageClass resources where the label `kubernetes.io/storage.class` is either `network-nas` or `fast-ssd`:
 
-```yaml title="Flexible filter example for storageClass"
+```yaml title="Flexible filter example for StorageClass"
 sync:
   toHost:
     persistentVolumes:
@@ -135,7 +135,7 @@ sync:
 
 The following configuration syncs StorageClass resources that match both label and expression criteria:
 
-```yaml title="Combined filter example for storageClass"
+```yaml title="Combined filter example for StorageClass"
 sync:
   toHost:
     persistentVolumes:
@@ -160,7 +160,7 @@ sync:
 
 When a PersistentVolumeClaim resource references a StorageClass that doesn't match the selector criteria, the error output looks like this:
 
-```bash title="Error handling example for storageClass"
+```bash title="Error handling example for StorageClass"
 vcluster-virtual-cluster-1:~$ kubectl describe pvc my-pvc
 Name:             my-pvc
 Namespace:        default