aboutsummaryrefslogtreecommitdiffstats
path: root/Lesson_0
diff options
context:
space:
mode:
authorKonstantin Aladyshev <aladyshev22@gmail.com>2021-06-12 21:51:49 +0300
committerKonstantin Aladyshev <aladyshev22@gmail.com>2021-06-12 21:51:49 +0300
commitdd797891e733e92e41826a7d0f281af379365076 (patch)
tree3ed97cf105eb4f2a99234836af219d2c1eeb84b1 /Lesson_0
parent021252f4a7689a87b9a305d750fbd9ec4547bc7d (diff)
downloadUEFI-Lessons-dd797891e733e92e41826a7d0f281af379365076.tar.gz
UEFI-Lessons-dd797891e733e92e41826a7d0f281af379365076.tar.bz2
UEFI-Lessons-dd797891e733e92e41826a7d0f281af379365076.zip
Fix typos in Lesson 0
Diffstat (limited to 'Lesson_0')
-rw-r--r--Lesson_0/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/Lesson_0/README.md b/Lesson_0/README.md
index ba9a98d..a45b5ae 100644
--- a/Lesson_0/README.md
+++ b/Lesson_0/README.md
@@ -47,7 +47,7 @@ To build OVMF execute:
build --platform=OvmfPkg/OvmfPkgX64.dsc --arch=X64 --buildtarget=RELEASE --tagname=GCC5
```
-If build is successful, result would be in the folder `Build/{Platform Name}/{TARGET}_{TOOL_CHAIN_TAG}/FV`. So in out case it would be:
+If build is successful, result would be in the folder `Build/{Platform Name}/{TARGET}_{TOOL_CHAIN_TAG}/FV`. So in our case it would be:
```
$ ls -lh Build/OvmfX64/RELEASE_GCC5/FV/OVMF*
-rw-r--r-- 1 kostr kostr 4.0M Jun 12 21:03 Build/OvmfX64/RELEASE_GCC5/FV/OVMF.fd
@@ -55,7 +55,7 @@ $ ls -lh Build/OvmfX64/RELEASE_GCC5/FV/OVMF*
-rw-r--r-- 1 kostr kostr 528K Jun 12 21:03 Build/OvmfX64/RELEASE_GCC5/FV/OVMF_VARS.fd
```
-The OVMF firmware (a UEFI implementation for QEMU) has been split into two files:
+The OVMF firmware (a UEFI implementation for QEMU) is split into two files:
- OVMF_CODE.fd contains the actual UEFI firmware,
- OVMF_VARS.fd is a "template" used to emulate persistent NVRAM storage.