summaryrefslogtreecommitdiff
path: root/Documentation/mainboard/lenovo
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/mainboard/lenovo')
-rw-r--r--Documentation/mainboard/lenovo/xx20_series.md4
-rw-r--r--Documentation/mainboard/lenovo/xx30_series.md4
2 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/mainboard/lenovo/xx20_series.md b/Documentation/mainboard/lenovo/xx20_series.md
index 976a29ba9f..8603853b94 100644
--- a/Documentation/mainboard/lenovo/xx20_series.md
+++ b/Documentation/mainboard/lenovo/xx20_series.md
@@ -26,8 +26,8 @@
* Do **NOT** accidently swap pins or power on the board while a SPI flasher
is connected. It will destroy your device.
* It's recommended to only flash the BIOS region. In that case you don't
- need to extract BLOBs from vendor firmware.
- If you want to flash the whole chip, you need BLOBs when building
+ need to extract blobs from vendor firmware.
+ If you want to flash the whole chip, you need blobs when building
coreboot.
* The shipped *Flash layout* allocates 3MiB to the BIOS region, which is the space
usable by coreboot.
diff --git a/Documentation/mainboard/lenovo/xx30_series.md b/Documentation/mainboard/lenovo/xx30_series.md
index e65a3f2a6f..ad856057f0 100644
--- a/Documentation/mainboard/lenovo/xx30_series.md
+++ b/Documentation/mainboard/lenovo/xx30_series.md
@@ -26,8 +26,8 @@
* Do **NOT** accidently swap pins or power on the board while a SPI flasher
is connected. It will permanently brick your device.
* It's recommended to only flash the BIOS region. In that case you don't
- need to extract BLOBs from vendor firmware.
- If you want to flash the whole chip, you need BLOBs when building
+ need to extract blobs from vendor firmware.
+ If you want to flash the whole chip, you need blobs when building
coreboot.
* The *Flash layout* shows that by default 7MiB of space are available for
the use with coreboot.