Update runtime-classes.mdx

Author: joaniekube

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

@@ -52,7 +52,7 @@ When RuntimeClass synchronization is enabled, vCluster uses selector criteria to
 
 **Unified selector control**: The same selector determines which RuntimeClass resources are imported into the virtual cluster and which Pod resources can sync to the host cluster. If a Pod references a RuntimeClass that was not synced to the virtual cluster, that Pod cannot sync to the host cluster.
 
-## Using selectors to filter RuntimeClasses
+## Use selectors to filter RuntimeClasses
 
 Selectors provide precise control over which RuntimeClass resources get synced from the host cluster. vCluster supports two types of selector criteria that follow standard Kubernetes label selector syntax.
 
@@ -69,9 +69,9 @@ All specified label conditions must match for a RuntimeClass 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 RuntimeClass resources function like any other Kubernetes resource in the virtual cluster. You can view them with `kubectl get runtimeclass` and reference them in Pod specifications using the runtimeClassName field.
 
@@ -89,7 +89,7 @@ When a RuntimeClass 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 RuntimeClass from the virtual cluster due to selector changes or deletion from the host cluster, any Pod resources that reference it remain in the virtual cluster. These orphaned Pod 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.
 
@@ -99,7 +99,7 @@ When vCluster removes a synced RuntimeClass from the virtual cluster due to sele
 
 To sync only RuntimeClass resources labeled `environment: development`:
 
-```yaml title="Filter example runtimeClass"
+```yaml title="Filter example RuntimeClass"
 sync:
   toHost:
     pods:
@@ -116,7 +116,7 @@ sync:
 
 To sync RuntimeClass resources where the label `kubernetes.io/runtime.class` is either `gvisor` or `youki`:
 
-```yaml title="Flexible filter example runtimeClass"
+```yaml title="Flexible filter example RuntimeClass"
 sync:
   toHost:
     pods:
@@ -137,7 +137,7 @@ sync:
 
 The following configuration syncs RuntimeClass resources that match both label and expression criteria:
 
-```yaml title="Combined filter example runtimeClass"
+```yaml title="Combined filter example RuntimeClass"
 sync:
   toHost:
     pods:
@@ -160,7 +160,7 @@ sync:
 
 When a Pod resource references a RuntimeClass that doesn't match the selector criteria, the error output looks like this:
 
-```bash title="Error handling example runtimeClass"
+```bash title="Error handling example RuntimeClass"
 vcluster-virtual-cluster-1:~$ kubectl describe pod my-pod
 Name:             my-pod
 Namespace:        default