Update docs after code review

Co-authored-by: Amund Tenstad <[email protected]>
Signed-off-by: Erik Godding Boye <[email protected]>

Author: erikgb

api/v1/kustomization_types.go

@@ -101,8 +101,8 @@ type KustomizationSpec struct {
 
 	// DeletionPolicy can be used to control garbage collection when this
 	// Kustomization is deleted. Valid values are ('MirrorPrune', 'Delete',
-	// 'Orphan'). 'MirrorPrune' mirrors the Prune field (false = 'Ophan',
-	// true = 'Delete'). Defaults to 'MirrorPrune'.
+	// 'Orphan'). 'MirrorPrune' mirrors the Prune field (orphan if false,
+	// delete if true). Defaults to 'MirrorPrune'.
 	// +kubebuilder:validation:Enum=MirrorPrune;Delete;Orphan
 	// +optional
 	DeletionPolicy string `json:"deletionPolicy,omitempty"`

docs/spec/v1/kustomizations.md

@@ -171,16 +171,16 @@ to garbage collect, see [`.status.inventory`](#inventory).
 
 ### Deletion policy
 
-`.spec.deletionPolicy` is an optional field that is allowing control over
+`.spec.deletionPolicy` is an optional field that allows control over
 garbage collection when a Kustomization object is deleted. The default behavior
-is to mirror the value of [`.spec.prune`](#prune).
+is to mirror the configuration of [`.spec.prune`](#prune).
 
 Valid values:
 
 - `MirrorPrune` (default) - The managed resources will be deleted if `prune` is
   `true` and orphaned if `false`.
 - `Delete` - Ensure the managed resources are deleted before the Kustomization
-   is finalized.
+   is deleted.
 - `Orphan` - Leave the managed resources when the Kustomization is deleted.
 
 For special cases when the managed resources are removed by other means (e.g.