copy edit

Author: joaniekube

vcluster/configure/vcluster-yaml/sync/to-host/advanced/custom-resources.mdx

@@ -79,7 +79,8 @@ With multi-namespace-mode you only need to rewrite references that include a nam
 ### JavaScript expression patches {#javascript-expression-patches}
 <!-- vale on -->
 
-These are powerful JavaScript ES6 compatible expression patches that can be used to change a field while syncing. You define how it changes when syncing from the virtual cluster into the host cluster or when syncing from the host cluster into the virtual cluster. To add a suffix to certificate DNS names you can do:
+These are JavaScript ES6 compatible expression patches that can be used to change a field while syncing. You define how it changes when syncing from the virtual cluster into the host cluster or when syncing from the host cluster into the virtual cluster. To add a suffix to certificate DNS names you can:
+
 ```yaml
 sync:
   toHost:
@@ -95,14 +96,15 @@ sync:
 ```
 
 There is also a variable called `context` besides `value` that can be used to access vCluster specific data:
-* `context.vcluster.name`: Name of the virtual cluster
-* `context.vcluster.namespace`: Namespace of the virtual cluster
-* `context.vcluster.config`: Config of the virtual cluster, basically `vcluster.yaml` merged with the defaults
-* `context.hostObject`: Host object (can be null if not available)
-* `context.virtualObject`: Virtual object (can be null if not available)
-* `context.path`: The matched path on the object, useful when using wildcard path selectors (*)
+- `context.vcluster.name`: Name of the virtual cluster
+- `context.vcluster.namespace`: Namespace of the virtual cluster
+- `context.vcluster.config`: Config of the virtual cluster, basically `vcluster.yaml` merged with the defaults
+- `context.hostObject`: Host object (can be null if not available)
+- `context.virtualObject`: Virtual object (can be null if not available)
+- `context.path`: The matched path on the object, useful when using wildcard path selectors (*)
 
 For example, to add `www.` to every DNS name specified in a cert-manager certificate in the path `spec.dnsNames`, you can use the following patch:
+
 ```yaml
 sync:
   toHost:
@@ -117,7 +119,8 @@ sync:
           reverseExpression: "value.startsWith('www.') ? value.slice(4) : value"
 ```
 
-With that patch, creating a new certificate within the vCluster like this:
+The patch creates a new certificate within the vCluster:
+
 ```yaml
 apiVersion: cert-manager.io/v1
 kind: Certificate
@@ -128,7 +131,8 @@ spec:
     - example.com
 ```
 
-Would create the following certificate in the host cluster:
+vCluster syncs the host cluster and applies your patch, creating this modified certificate:
+
 ```yaml
 apiVersion: cert-manager.io/v1
 kind: Certificate
@@ -139,7 +143,8 @@ spec:
     - www.example.com # the patch added www. to this field
 ```
 
-When you change now the certificate in the host cluster like this:
+If you directly edit the certificate in the host cluster and change the domain:
+
 ```yaml
 apiVersion: cert-manager.io/v1
 kind: Certificate
@@ -150,7 +155,8 @@ spec:
     - www.other-domain.com # changed from www.example.com
 ```
 
-vCluster would sync back the certificate like this:
+vCluster detects the change, applies the reverse patch, and updates the certificate in your virtual cluster:
+
 ```yaml
 apiVersion: cert-manager.io/v1
 kind: Certificate