Apply suggestions from code review

Co-authored-by: Colleen McGinnis <[email protected]>

Author: karenzone

docs/release-notes/known-issues.md

@@ -28,30 +28,30 @@ Known issues are significant defects or limitations that may impact your impleme
 
 **Applies to: {{agent}} 8.18.7, 9.0.7** 
 
-On September 17, 2025, a known issue was discovered that can cause {{agent}} upgrades to get stuck if an upgrade attempt fails early. This happens because the coordinator’s overrideState remains set, leaving the agent in a state that appears to be upgrading.
+On September 17, 2025, a known issue was discovered that can cause {{agent}} upgrades to get stuck if an upgrade attempt fails early. This happens because the coordinator’s `overrideState` remains set, leaving the agent in a state that appears to be upgrading.
 
 **Conditions**
 
-This issue is triggered if the upgrade fails during one of the early checks inside Coordinator.Upgrade, for example:
+This issue is triggered if the upgrade fails during one of the early checks inside `Coordinator.Upgrade`, for example:
 
 - The agent is not upgradeable
 - Capabilities check denies the upgrade
-- Most commonly: When {{agent}} is tamper-protected and Endpoint returns an error during action proxying, for example, because the upgrade action signature is invalid, missing, or fails verification. This causes the coordinator’s override state to be stuck.
+- When {agent} is tamper-protected, Endpoint must validate that the upgrade action was correctly signed by Kibana to allow the upgrade. If the signature is missing, invalid, or the connection between {agent} and Endpoint was interrupted, the validation fails. This causes the agent coordinator's override state to become stuck until the agent is restarted.
 
 **Symptoms**
 
 - {{fleet}} shows the upgrade action in progress, even though the upgrade remains stuck
 - No further upgrade attempts succeed 
-- Elastic-agent status shows an override state indicating upgrade 
+- Elastic Agent status shows an override state indicating upgrade 
 
 **Workaround**
 
-Restart the {{agent}} to clear the coordinator’s overrideState and allow new upgrade attempts to proceed.
+Restart the {{agent}} to clear the coordinator’s `overrideState` and allow new upgrade attempts to proceed.
 
 **Resolution**
 This issue was fixed in [#9992](https://github.com/elastic/elastic-agent/pull/9992), which ensures that the coordinator clears its override state whenever an early failure occurs.
 
-The fix will be included in versions 9.1.4, 8.19.4, 9.0.8, and 8.18.8.
+The fix is included in versions 9.1.4 and 8.19.4, and planned for versions 9.0.8 and 8.18.8.
 :::
 
 :::{dropdown} [Windows] {{agent}} does not process Windows security events