summaryrefslogtreecommitdiffstats
path: root/IntelFsp2Pkg/Tools/UserManuals
diff options
context:
space:
mode:
Diffstat (limited to 'IntelFsp2Pkg/Tools/UserManuals')
-rw-r--r--IntelFsp2Pkg/Tools/UserManuals/GenCfgOptUserManual.md2
-rw-r--r--IntelFsp2Pkg/Tools/UserManuals/PatchFvUserManual.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/IntelFsp2Pkg/Tools/UserManuals/GenCfgOptUserManual.md b/IntelFsp2Pkg/Tools/UserManuals/GenCfgOptUserManual.md
index 938c18416d..0a0f592801 100644
--- a/IntelFsp2Pkg/Tools/UserManuals/GenCfgOptUserManual.md
+++ b/IntelFsp2Pkg/Tools/UserManuals/GenCfgOptUserManual.md
@@ -213,7 +213,7 @@ in the third.
```@Bsf NAME:{Variable 1} TYPE:{Combo}```
There is a special **None** type that puts the variable in the **StructDef**
-region of the BSF, but doesn?t put it in any **Page** section. This makes the
+region of the BSF, but doesn't put it in any **Page** section. This makes the
variable visible to BCT, but not to the end user.
###HELP
diff --git a/IntelFsp2Pkg/Tools/UserManuals/PatchFvUserManual.md b/IntelFsp2Pkg/Tools/UserManuals/PatchFvUserManual.md
index becaf96b21..5f1031e729 100644
--- a/IntelFsp2Pkg/Tools/UserManuals/PatchFvUserManual.md
+++ b/IntelFsp2Pkg/Tools/UserManuals/PatchFvUserManual.md
@@ -30,7 +30,7 @@ FSP tree.
The example used contains Windows batch script %VARIABLES%.
-#FvFileBaseNames (Argument 2: 0ptional Part 1)
+#FvFileBaseNames (Argument 2: Optional Part 1)
The firmware volume file base names (**_FvFileBaseNames_**) are the independent
Fv?s that are to be patched within the FD. (0 or more in the form
**FVFILEBASENAME:**) The colon **:** is used for delimiting the single