fix typos

Signed-off-by: Shubham Pampattiwar <[email protected]>

Author: shubham-pampattiwar

design/existing-resource-policy_design.md

@@ -27,7 +27,7 @@ Related issue: https://github.com/vmware-tanzu/velero/issues/4066
 ### Use-cases/Scenarios
 
 ### A. Production Cluster - Backup Cluster:
-Let's say you have a Backup Cluster which is identical to the Production Cluster. After some operations/usage/time the Production Cluster had changed itself, there might be new deployments, some secrets might have been updated. Now, this means that the Backup cluster will no longer be identical to the Production Cluster. In order to keep the Backup Cluster upto date/identical to the Production Cluster with respect to Kubernetes resources except PV data we would like to use Velero for scheduling new backups which would in turn help us update the Backup Cluster via Velero restore.
+Let's say you have a Backup Cluster which is identical to the Production Cluster. After some operations/usage/time the Production Cluster had changed itself, there might be new deployments, some secrets might have been updated. Now, this means that the Backup cluster will no longer be identical to the Production Cluster. In order to keep the Backup Cluster up to date/identical to the Production Cluster with respect to Kubernetes resources except PV data we would like to use Velero for scheduling new backups which would in turn help us update the Backup Cluster via Velero restore.
 
 Reference: https://github.com/vmware-tanzu/velero/issues/4066#issuecomment-954320686
 
@@ -50,16 +50,16 @@ In this approach we do *not* change existing velero behavior. If the resource to
 skip restoration.
 2. `update` or `merge` or `patch`: In this behaviour Velero will try an attempt to patch the resource with the backed up version, 
 if the patch fails log it as a warning and continue the restore process, user may wish specify the merge type.
-3. `updateAll`: Similar to `update` option but Velero will update annotation on unchanged resources too.
+3. `updateAll`: Similar to `update` option but Velero will update labels on unchanged resources too.
 4. `recreate`:  If resource already exists, then Velero will delete it and recreate the resource.
 
 In summary,
 
-| Policy      | Action performed by Velero                                                                  | Velero Logging                                                |
-|-------------|---------------------------------------------------------------------------------------------|---------------------------------------------------------------|
-| `none`      | Existing Velero behavior.                                                                   | `info` log for unchanged resource, `warn` on changed resource |
-| `update`    | Velero tries to attempt a `patch` on changed resource                                       | `info` log for unchanged, `warn` if patch failed              |
-| `updateAll` | Velero updates annotation on unchanged resource  and attempts a `patch` on changed resource | `info` log for unchanged and `warn` if patch failed           |
+| Policy      | Action performed by Velero                                                              | Velero Logging                                                |
+|-------------|-----------------------------------------------------------------------------------------|---------------------------------------------------------------|
+| `none`      | Existing Velero behavior.                                                               | `info` log for unchanged resource, `warn` on changed resource |
+| `update`    | Velero tries to attempt a `patch` on changed resource                                   | `info` log for unchanged, `warn` if patch failed              |
+| `updateAll` | Velero updates labels on unchanged resource  and attempts a `patch` on changed resource | `info` log for unchanged and `warn` if patch failed           |
 
 *Note:* The `recreate` option is a non-goal for this enhancement proposal, but it is considered as a future scope.
 Another thing to highlight is that Velero will not be deleting any resources in any of the policy options proposed in