diff --git a/docs/howto/enforce-agent-startup-remotely-registry.md b/docs/howto/enforce-agent-startup-remotely-registry.md
index f4c533d86..431bb468d 100644
--- a/docs/howto/enforce-agent-startup-remotely-registry.md
+++ b/docs/howto/enforce-agent-startup-remotely-registry.md
@@ -18,7 +18,7 @@ remote management solution capable of deploying MS Store (or MSIX-packaged) appl
 - A Windows remote management solution.
 - If using Intune, an Enterprise E3 or E5 or Education A3 or A5 licenses.
 
-## Key takeaways
+## Overview
 
 1. The registry path `"HKCU:\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\CanonicalGroupLimited.UbuntuPro_79rhkp1fndgsc"`
    holds configuration information specific about UP4W and is created or overwritten when the MSIX package is
diff --git a/docs/howto/start-agent-remotely.md b/docs/howto/start-agent-remotely.md
index 0860b770d..ec1982391 100644
--- a/docs/howto/start-agent-remotely.md
+++ b/docs/howto/start-agent-remotely.md
@@ -19,7 +19,7 @@ choice, as long as the said solution can run scripts with current user's credent
 - At least one managed Windows device.
 - A Windows remote management solution.
 
-## Key takeaways
+## Overview
 
 1. Running a script as user to start the UP4W background agent makes it immediately available.
 2. Remote management solutions can be used to start the agent.