From 79f821f5e9e7a0073b14d90a31a3c0b8253b8de9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jacob=20L=C3=A4rfors?=
 <1135394+jlarfors@users.noreply.github.com>
Date: Thu, 14 Mar 2024 16:15:32 +0200
Subject: [PATCH] polish a sentence about ssa

---
 docs/serversideapply.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/serversideapply.md b/docs/serversideapply.md
index 4a21bbd..ad18355 100644
--- a/docs/serversideapply.md
+++ b/docs/serversideapply.md
@@ -19,7 +19,7 @@ The answer: a server-side patching strategy that keeps track of which entity man
 
 ## Manager and Managed Fields
 
-When an object is applied, the `store` (server-side) requires a "manager" (string name) and will calculate the fields that this manager manages.
+When an object is applied, the `store` (server-side) requires a "manager" (string name) and will calculate the fields that this manager manages based on the object payload.
 
 The computed managed fields are stored along with the object in the `.metadata.managedFields` field.
 
@@ -43,7 +43,7 @@ The returned object will include the entire object (all the fields, including th
 The reconciler will want to modify some fields and apply the object back to the store, such as updating the `.status` field.
 The object which the reconcilier applies should only include the fields which the reconciler should manage.
 
-So, how do we "extract" the managed fields from object, so that we can mutate it and apply it back afterwards? Using the `hz.ExtractManagedFields(...)` function.
+So, how do we "extract" the managed fields from an object, so that we can mutate it and apply it back afterwards? Using the `hz.ExtractManagedFields(...)` function.
 
 A typical reconcile loop will look like this: