Update priority-classes.mdx

Author: joaniekube

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

@@ -44,9 +44,9 @@ If you try to create a PriorityClass directly in the virtual cluster, using for
 
 When PriorityClass syncing is enabled, vCluster uses a label selector to control which PriorityClass and Pod resources are synchronized between the host and virtual clusters. This affects two resource types with separate unidirectional sync flows:
 
-- **PriorityClass resources** (host → virtual): vCluster copies PriorityClass resources from the host cluster to the virtual cluster if they match the selector. You cannot create PriorityClass resources directly in the virtual cluster. If no selector is defined, all PriorityClass resources from the host cluster are synced and made available for reference in Pods.
+- **PriorityClass resources (host → virtual)**: vCluster copies PriorityClass resources from the host cluster to the virtual cluster if they match the selector. You cannot create PriorityClass resources directly in the virtual cluster. If no selector is defined, all PriorityClass resources from the host cluster are synced and made available for reference in Pods.
 
-- **Pod resources** (virtual → host): vCluster syncs Pod resources from the virtual cluster to the host cluster only if one of the following is true:
+- **Pod resources (virtual → host)**: vCluster syncs Pod resources from the virtual cluster to the host cluster only if one of the following is true:
    - The Pod's `priorityClassName` matches a PriorityClass allowed by the selector.
    - The Pod has an empty `priorityClassName` field.
    - No selector is defined, which disables PriorityClass filtering entirely and allows all Pods to sync regardless of their priorityClassName.
@@ -70,9 +70,9 @@ The `matchExpressions` selector allows more flexible, set-based filtering with s
 
 All specified label conditions must match for a PriorityClass to be included in the sync. This means that if you define both `matchLabels` and `matchExpressions`, a PriorityClass 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 PriorityClass resources function like any other Kubernetes resource in the virtual cluster. You can view them with `kubectl get priorityclass` and reference them in their Pod specifications. When you modify a PriorityClass in the host cluster, vCluster re-evaluates whether it still matches the selector criteria. If the PriorityClass continues to match, vCluster updates the corresponding resource in the virtual cluster to reflect the changes. If the PriorityClass no longer matches the selector criteria, vCluster removes it from the virtual cluster.
 
@@ -92,7 +92,7 @@ If you create a Pod resource that references a PriorityClass not matching the se
 
 The error output appears as a Kubernetes event that you can view using `kubectl describe`. The event message states that the pod was not synced because the referenced PriorityClass does not match the configured selector criteria. This immediate feedback can help you understand why Pod resources are not working.
 
-### Orphaned resources and cleanup
+### Remove orphaned resources
 
 When vCluster removes a synced PriorityClass 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. This manual approach ensures that you maintain full control over resource cleanup and can verify that deletions are intentional.
 
@@ -102,7 +102,7 @@ When vCluster removes a synced PriorityClass from the virtual cluster due to sel
 
 To sync only PriorityClass resources labeled `environment: development`:
 
-```yaml title="Filter example priorityClass"
+```yaml title="Filter example PriorityClass"
 sync:
   fromHost:
     priorityClasses:
@@ -116,7 +116,7 @@ sync:
 
 To sync PriorityClass resources where the label `kubernetes.io/priority.class` is either `low` or `medium`:
 
-```yaml title="Flexible filter example priorityClass"
+```yaml title="Flexible filter example PriorityClass"
 sync:
   fromHost:
     priorityClasses:
@@ -134,7 +134,7 @@ sync:
 
 The following configuration syncs PriorityClass resources that match both label and expression criteria:
 
-```yaml title="Combined filter example priorityClass"
+```yaml title="Combined filter example PriorityClass"
 sync:
   fromHost:
     priorityClasses:
@@ -154,7 +154,7 @@ sync:
 
 When a Pod resource references a PriorityClass that doesn't match the selector criteria, the error output looks like this:
 
-```bash title="Error handling example priorityClass"
+```bash title="Error handling example PriorityClass"
 vcluster-virtual-cluster-1:~$ kubectl describe pod my-pod
 Name:             my-pod
 Namespace:        default