docs: batch one-line typo and syntax fixes

content/en/docs/getting-started/kind.md

@@ -288,7 +288,7 @@ To remove all the resources you just created, run the commands below:
 kubectl delete crp sample-crp
 
 kubectl delete ns kubefleet-sample
-kubectl delete configmap app -n kubefleet-sample
+kubectl delete configmap kf-cm -n kubefleet-sample
 ```
 
 To uninstall KubeFleet components on the clusters, run the commands below:

content/en/docs/getting-started/on-prem.md

@@ -189,6 +189,9 @@ the completion.
 Now, log into the member clusters to confirm that the placement has been completed.
 
 ```sh
+# Replace YOUR-MEMBER-CLUSTER-CONTEXT with the name of the kubeconfig context for one of
+# the member clusters you joined above.
+export MEMBER_CLUSTER_CONTEXT=YOUR-MEMBER-CLUSTER-CONTEXT
 kubectl config use-context $MEMBER_CLUSTER_CONTEXT
 kubectl get ns
 kubectl get configmap -n work

content/en/docs/how-tos/affinities.md

@@ -80,9 +80,9 @@ includes:
   * `In`: the cluster must have a label key with one of the listed values.
   * `NotIn`: the cluster must have a label key that is not associated with any of the listed values.
   * `Exists`: the cluster must have the label key present; any value is acceptable.
-  * `NotExists`: the cluster must not have the label key.
+  * `DoesNotExist`: the cluster must not have the label key.
 
-    If you plan to use `Exists` and/or `NotExists`, you must leave the list of values empty.
+    If you plan to use `Exists` and/or `DoesNotExist`, you must leave the list of values empty.
 
 Below is an example of `matchExpressions` affinity term using the `In` operator:
 

content/en/docs/how-tos/crp.md

@@ -266,9 +266,9 @@ spec:
             preferredDuringSchedulingIgnoredDuringExecution:
                 - weight: 20
                   preference:
-                    - labelSelector:
-                        matchLabels:
-                            critical-level: 1
+                      labelSelector:
+                          matchLabels:
+                              critical-level: "1"
 ```
 
 The `ClusterResourcePlacement` object above will pick first clusters with the `critical-level=1`