diff --git a/mdop/mbam-v25/upgrade-mbam2.5-sp1.md b/mdop/mbam-v25/upgrade-mbam2.5-sp1.md
index 18e3f0554a..f30ade580a 100644
--- a/mdop/mbam-v25/upgrade-mbam2.5-sp1.md
+++ b/mdop/mbam-v25/upgrade-mbam2.5-sp1.md
@@ -2,10 +2,11 @@
 title:  Upgrading from MBAM 2.5 to MBAM 2.5 SP1 Servicing Release Update
 author: TobyTu 
 ms.author: ksharma
-manager: DCSCPMCAIM365 
+manager: 
 audience: ITPro  
 ms.topic: article  
-ms.prod: mbam
+ms.prod: w10
+manager: miaposto
 localization_priority: Normal
 --- 
 
diff --git a/windows/client-management/introduction-page-file.md b/windows/client-management/introduction-page-file.md
index 747ac0b22a..662ae5f90e 100644
--- a/windows/client-management/introduction-page-file.md
+++ b/windows/client-management/introduction-page-file.md
@@ -7,9 +7,8 @@ ms.topic: troubleshooting
 author: Deland-Han
 ms.localizationpriority: medium
 ms.author: delhan
-ms.date: 8/22/2019
-ms.reviewer: 
-manager: dcscontentpm
+ms.reviewer: greglin
+manager: willchen
 ---
 
 # Introduction to page files
@@ -31,11 +30,8 @@ Some products or services require a page file for various reasons. For specific
 For example, the following Windows servers requires page files:
 
 - Windows Server domain controllers (DCs)
-
 - DFS Replication (DFS-R) servers
-
 - Certificate servers
-
 - ADAM/LDS servers
 
 This is because the algorithm of the database cache for Extensible Storage Engine (ESENT, or ESE in Microsoft Exchange Server) depends on the "\Memory\Transition Pages RePurposed/sec" performance monitor counter. A page file is required to make sure that the database cache can release memory if other services or applications request memory.
@@ -60,13 +56,13 @@ Page files extend how much "committed memory" (also known as "virtual memory") i
 
 The system commit memory limit is the sum of physical memory and all page files combined. It represents the maximum system-committed memory (also known as the "system commit charge") that the system can support.
 
-![Task manager](media/task-manager.png)
+![Task manager](images/task-manager.png)
  
 The system commit charge is the total committed or "promised" memory of all committed virtual memory in the system. If the system commit charge reaches the system commit limit, the system and processes might not get committed memory. This condition can cause freezing, crashing, and other malfunctions. Therefore, make sure that you set the system commit limit high enough to support the system commit charge during peak usage.
 
-![Out of memory](media/out-of-memory.png)
+![Out of memory](images/out-of-memory.png)
 
-![Task Manager](media/task-manager-commit.png)
+![Task Manager](images/task-manager-commit.png)
 
 The system committed charge and system committed limit can be measured on the **Performance** tab in Task Manager or by using the "\Memory\Committed Bytes" and "\Memory\Commit Limit" performance counters. The \Memory\% Committed Bytes In Use counter is a ratio of \Memory\Committed Bytes to \Memory\Commit Limit values.
 
diff --git a/windows/security/threat-protection/microsoft-defender-atp/tvm-security-recommendation.md b/windows/security/threat-protection/microsoft-defender-atp/tvm-security-recommendation.md
index 0c8c9f14f6..cb1913abcb 100644
--- a/windows/security/threat-protection/microsoft-defender-atp/tvm-security-recommendation.md
+++ b/windows/security/threat-protection/microsoft-defender-atp/tvm-security-recommendation.md
@@ -36,6 +36,7 @@ Each machine in the organization is scored based on three important factors: thr
 
 
 ## Navigate through your security recommendations
+
 You can access the security recommendation from the Microsoft Defender ATP Threat & Vulnerability Management menu, dashboard, software page, and machine page, to give you the context that you need, as you require it. 
 
 There are security recommendations for application, operating system, network, accounts, and security controls.