Apply suggestions from code review

Co-authored-by: HonkingGoose <[email protected]>

docs/usage/configuration-options.md

@@ -1679,8 +1679,10 @@ It falls back to Renovate-based automerge if the platform-native automerge is no
 
 You can also fine-tune the behavior by setting `packageRules` if you want to use it selectively (e.g. per-package).
 
-If you rely on Renovate's behavior of rebasing automerging branches when `rebaseWhen=auto`, then note that you are no longer guaranteed of up-to-date branches when automerging if you enable platform automerge.
-For example, GitHub might automerge a Renovate branch even if it is one or more commits behind the base branch at the time.
+Note that the outcome of `rebaseWhen=auto` can differ when `platformAutomerge=true` is enable.
+Normally when you set `rebaseWhen=auto` Renovate rebases any branch that's behind the base branch automatically, and some people rely on that.
+This behavior is no longer guaranteed when you enable `platformAutomerge` because the platform might automerge a branch which is not up-to-date.
+For example, GitHub might automerge a Renovate branch even if it's behind the base branch at the time.
 
 ## postUpdateOptions