SecurityPkg: Fix typos in comments

[mirror_edk2.git] / OvmfPkg / README

diff --git a/OvmfPkg/README b/OvmfPkg/README
index 0f70fa7359d0d045151b9047b9f2cadff2371833..304e69fbe5456d57ae1e0d4bf95800b3a91b3793 100644 (file)
--- a/OvmfPkg/README
+++ b/OvmfPkg/README
@@ -170,11 +170,6 @@ can be used on Windows.
 \r
   -global ICH9-LPC.disable_s3=1 \\r
 \r
-Dependent on the development status of the\r
-"UefiCpuPkg/Universal/Acpi/S3Resume2Pei" module, S3 resume may not work in\r
-OvmfPkg/OvmfPkgX64.dsc builds. In such cases, OvmfPkg/OvmfPkgIa32X64.dsc is\r
-recommended for running X64 guests.\r
-\r
 === Network Support ===\r
 \r
 OVMF provides a UEFI network stack by default. Its lowest level driver is the\r
@@ -236,8 +231,8 @@ longer.)
     - Install the drivers into a directory called Intel3.5 in your WORKSPACE.\r
 \r
   - Include the driver in OVMF during the build:\r
-    - Add "-D E1000_ENABLE -D FD_SIZE_2MB" to your build command,\r
-    - For example: "build -D E1000_ENABLE -D FD_SIZE_2MB".\r
+    - Add "-D E1000_ENABLE" to your build command,\r
+    - For example: "build -D E1000_ENABLE".\r
 \r
 * When a matching iPXE driver is configured for a NIC as described above, it\r
   takes priority over other drivers that could possibly drive the card too:\r
@@ -295,11 +290,11 @@ If you must use UNIXGCC, then you can override the build options for
 particular libraries and modules in the .dsc to re-enable debugging\r
 selectively. For example:\r
   [Components]\r
-  OvmfPkg/Library/PlatformBdsLib/PlatformBdsLib.inf {\r
+  OvmfPkg/Library/PlatformBootManagerLib/PlatformBootManagerLib.inf {\r
     <BuildOptions>\r
       GCC:*_*_*_CC_FLAGS             = -UMDEPKG_NDEBUG\r
   }\r
-  IntelFrameworkModulePkg/Universal/BdsDxe/BdsDxe.inf {\r
+  MdeModulePkg/Universal/BdsDxe/BdsDxe.inf {\r
     <BuildOptions>\r
       GCC:*_*_*_CC_FLAGS             = -UMDEPKG_NDEBUG\r
   }\r