Update ingress-classes.mdx

Author: joaniekube

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

@@ -44,13 +44,13 @@ If you try to create an IngressClass directly in the virtual cluster, using for
 
 When IngressClass sync is enabled, vCluster uses selector criteria to control which resources are synced between clusters. This affects two different resource types that flow in opposite directions.
 
-- **IngressClass resources**: Flow from host cluster to virtual cluster only. You cannot create IngressClass resources in the virtual cluster. vCluster copies IngressClass resources from the host cluster based on your selector criteria to make them available for you to reference in their Ingress configurations. If no `selector` is specified, all IngressClass resources from the host cluster are synced.
+- **IngressClass resources (host → virtual)**: Flow from host cluster to virtual cluster only. You cannot create IngressClass resources in the virtual cluster. vCluster copies IngressClass resources from the host cluster based on your selector criteria to make them available for you to reference in their Ingress configurations. If no `selector` is specified, all IngressClass resources from the host cluster are synced.
 
-- **Ingress resources**: Flow from virtual cluster to host cluster where ingress controllers process them. An Ingress syncs only if it references an IngressClass that matches your selector criteria. Ingress resources also sync if they have an empty `ingressClassName` field or if no `selector` is specified in the configuration - this works as a bypass mechanism.
+- **Ingress resources (virtual → host)**: Flow from virtual cluster to host cluster where ingress controllers process them. An Ingress syncs only if it references an IngressClass that matches your selector criteria. Ingress resources also sync if they have an empty `ingressClassName` field or if no `selector` is specified in the configuration.
 
 - **How selectors control both flows**: The selector determines which IngressClass resources get copied from host to virtual cluster. The same selector also determines which Ingress resources can sync from virtual to host cluster. If an Ingress references an IngressClass that wasn't synced to the virtual cluster, that Ingress cannot sync to the host cluster.
 
-## Using selectors to filter IngressClasses
+## Use selectors to filter IngressClasses
 
 Selectors provide precise control over which IngressClass resources get synced from the host cluster. vCluster supports two types of selector criteria that follow standard Kubernetes label selector syntax.
 
@@ -65,9 +65,9 @@ The `matchExpressions` selector allows more flexible, set-based filtering with s
 
 All specified label conditions must match for an IngressClass to be included in the sync. This means that if you define both `matchLabels` and `matchExpressions`, an IngressClass must satisfy all criteria to be synced to the virtual cluster.
 
-## Sync behavior and considerations
+## Sync behavior considerations
 
-### Resource lifecycle and validation
+### Resource lifecycle
 
 Synced IngressClass resources function like any other Kubernetes resource in the virtual cluster. You can view them with `kubectl get ingressclass` and reference them in your Ingress specifications. When you modify an IngressClass in the host cluster, vCluster re-evaluates whether it still matches the selector criteria. If the IngressClass continues to match, vCluster updates the corresponding resource in the virtual cluster to reflect the changes. If the IngressClass no longer matches the selector criteria, vCluster removes it from the virtual cluster.
 
@@ -85,7 +85,7 @@ When you creates an Ingress resource that references an IngressClass not matchin
 
 The error output appears as a Kubernetes event that you can view using `kubectl describe`. The event message clearly states that the ingress was not synced because the referenced IngressClass does not match the configured selector criteria.
 
-### Orphaned resources and cleanup
+### Remove orphaned resources
 
 When vCluster removes a synced IngressClass from the virtual cluster due to selector changes or deletion from the host cluster, any Ingress resources that reference it remain in the virtual cluster. These orphaned Ingress 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. This manual approach ensures that you maintain full control over resource cleanup and can verify that deletions are intentional.
 
@@ -95,7 +95,7 @@ When vCluster removes a synced IngressClass from the virtual cluster due to sele
 
 To sync only IngressClass resources labeled `environment: development`:
 
-```yaml title="Filter example ingressClass"
+```yaml title="Filter example IngressClass"
 sync:
   toHost:
     ingresses:
@@ -112,7 +112,7 @@ sync:
 
 To sync IngressClass resources where the label `kubernetes.io/ingress.class` is either `nginx` or `traefik`:
 
-```yaml title="Flexible filter example ingressClass"
+```yaml title="Flexible filter example IngressClass"
 sync:
   toHost:
     ingresses:
@@ -133,7 +133,7 @@ sync:
 
 The following configuration syncs IngressClass resources that match both label and expression criteria:
 
-```yaml title="Combined filter example ingressClass"
+```yaml title="Combined filter example IngressClass"
 sync:
   toHost:
     ingresses:
@@ -156,7 +156,7 @@ sync:
 
 When an Ingress resource references an IngressClass that doesn't match the selector criteria, the error output looks like this:
 
-```bash title"Error handling example ingressClass"
+```bash title"Error handling example IngressClass"
 vcluster-virtual-cluster-1:~$ kubectl describe ingress my-ingress
 Name:             my-ingress
 Namespace:        default