Make the document specific for X86 systems

Jiaxin Wu · Jiaxin Wu · commit 4f7b21d67d69 · 2025-04-29T17:16:30.000+08:00
Signed-off-by: Jiaxin Wu &lt;jiaxin.wu@intel.com&gt;
diff --git a/1_mm_introduction.md b/1_mm_introduction.md
@@ -1,5 +1,5 @@
 <!--- @file
-  First Chapter of Standalone MM Getting Started Guide
+  First Chapter of Getting Started Guide for Standalone MM on X86 Systems
 
   Copyright (c) 2025, Intel Corporation. All rights reserved.<BR>
 
@@ -33,7 +33,7 @@
 
 ## 1.1 SMM and MM Overview
 
-This section describes the main differences between Traditional SMM and Standalone MM. A detailed comparison of the Traditional MM and Standalone MM load process is described in the PI Specification sections "Initializing Management Mode in MM Traditional Mode" and "Initializing Management Mode in Standalone Mode" respectively.
+This section describes the main differences between Traditional SMM and Standalone MM on X86 systems. A detailed comparison of the Traditional MM and Standalone MM load process is described in the PI Specification sections "Initializing Management Mode in MM Traditional Mode" and "Initializing Management Mode in Standalone Mode" respectively.
 
 In the following comparison, we will use "SMM" to represent "Traditional SMM" and "MM" to represent "Standalone MM".
 
@@ -59,7 +59,7 @@ MM Driver:
 
 ## 1.2 MM Driver Dispatch
 
-For traditional SMM drivers, they are dispatched within multiple rounds: The dispatch is hooked on the `gEfiEventDxeDispatchGuid` event, which is signaled by DXE Core when DXE Core finishes one round of dispatch.
+For traditional SMM drivers dispatch on X86 systems, they are dispatched within multiple rounds: The dispatch is hooked on the `gEfiEventDxeDispatchGuid` event, which is signaled by DXE Core when DXE Core finishes one round of dispatch.
 
 `StandaloneMmIpl` is a PEIM responsible for locating and loading `StandaloneMmCore`. All the MM drivers are dispatched by `StandaloneMmCore` in the 2-round dispatches in X86:
 
@@ -153,7 +153,7 @@ But in cases where silicon initialization code does not want to rely on the comm
 
 The `PiSmmCpuStandaloneMm` driver creates a page table used in MM mode according to the `EFI_HOB_RESOURCE_DESCRIPTOR` in the MM HOB list. The newly created page table controls memory accessibility in MM.
 
-The following table outlines the differences in memory protection policies between the traditional SMM and the Standalone MM. This comparison is particularly relevant for x86 systems and highlights the security enhancements provided by Standalone MM.
+The following table outlines the differences in memory protection policies between the traditional SMM and the Standalone MM. Note: this comparison is particularly relevant for x86 systems and highlights the security enhancements provided by Standalone MM.
 
 | Items                        | Policy                                      | SMM                          | MM                           |
 |------------------------------|---------------------------------------------|------------------------------|------------------------------|
diff --git a/2_smm_to_mm_porting_guide.md b/2_smm_to_mm_porting_guide.md
@@ -1,5 +1,5 @@
 <!--- @file
-  First Chapter of Standalone MM Getting Started Guide
+  First Chapter of Getting Started Guide for Standalone MM on X86 Systems
 
   Copyright (c) 2025, Intel Corporation. All rights reserved.<BR>
 
@@ -33,7 +33,7 @@
 
 ## 2.1 Porting Design Overview
 
-This section provides instructions on how to convert traditional SMM drivers to MM drivers. A traditional SMM driver may need to be split into one or more drivers when transitioning to a Standalone MM driver:
+This section provides instructions on how to convert traditional SMM drivers to MM drivers on X86 systems. A traditional SMM driver may need to be split into one or more drivers when transitioning to a Standalone MM driver:
 
 1. **PEI/DXE Driver**: If the traditional SMM driver contains non-MM initialization code:
    - The PEI driver can be used to either unblock memory or prepare required data for runtime code and pass the data via HOB or Comm PPI/Protocol.
diff --git a/README.md b/README.md
@@ -1,5 +1,5 @@
 <!--- @file
-  README.md for Standalone MM Getting Started Guide
+  README.md for Getting Started Guide for Standalone MM on X86 Systems
 
   Copyright (c) 2025, Intel Corporation. All rights reserved.<BR>
 
diff --git a/SUMMARY.md b/SUMMARY.md
@@ -31,7 +31,7 @@
 
 # Summary
 
-* [Standalone MM Getting Started Guide](README.md)
+* [Getting Started Guide for Standalone MM on X86 Systems](README.md)
 
 * [1 MM Introduction](1_mm_introduction.md#1-mm-introduction)
   * [1.1 SMM and MM Overview](1_mm_introduction.md#11-smm-and-mm-overview)
diff --git a/book.json b/book.json
@@ -1,7 +1,7 @@
 {
   "variables" : {
     "draft"   : "yes",
-    "title"   : "Standalone MM Getting Started Guide",
+    "title"   : "Getting Started Guide for Standalone MM on X86 Systems",
     "version" : "Revision 1.00"
   },
   "plugins": ["puml-aleung"],
diff --git a/cover.jpg b/cover.jpg

Original file line number	Diff line number	Diff line change
`@@ -1,7 +1,7 @@`
`1`	`1`	`{`
`2`	`2`	`"variables" : {`
`3`	`3`	`"draft" : "yes",`
`4`		`- "title" : "Standalone MM Getting Started Guide",`
	`4`	`+ "title" : "Getting Started Guide for Standalone MM on X86 Systems",`
`5`	`5`	`"version" : "Revision 1.00"`
`6`	`6`	`},`
`7`	`7`	`"plugins": ["puml-aleung"],`