diff --git a/themes/default/content/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply.md b/themes/default/content/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply.md
index de5d3e88c6..72628fe739 100644
--- a/themes/default/content/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply.md
+++ b/themes/default/content/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply.md
@@ -147,7 +147,9 @@ Users may opt into the previous default Client-side Apply (CSA) mode by setting
 
 ## Upsert a Resource
 
-With Server-Side Apply mode enabled, you can "upsert" a resource; that is, update a resource if it already exists, or create it if it does not yet exist. You can set the `pulumi.com/patchForce` annotation if you want to force an override for any conflicts with an existing version of the resource.
+With Server-Side Apply mode enabled, you can "upsert" a resource; that is, update a resource if it already exists, or create it if it does not yet exist.
+
+If the resource already exists, the default behavior is for any conflicting values to be resolved with the value from the patch being applied (that is, the new version of the resource). If you would prefer to resolve conflicts using the value of the existing resource, add the `pulumi.com/patchForce` annotation:
 
 {{< chooser language "typescript,python,go,csharp,java,yaml" >}}