aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/bsd/freebsd.md2
-rw-r--r--docs/bsd/netbsd.md2
-rw-r--r--docs/bsd/openbsd.md2
-rw-r--r--docs/gnulinux/encrypted_parabola.md4
-rw-r--r--docs/gnulinux/grub_cbfs.md4
-rw-r--r--docs/gnulinux/grub_hardening.md4
-rw-r--r--docs/hardware/gm45_remove_me.md2
-rw-r--r--docs/install/bbb_setup.md2
-rw-r--r--docs/install/c201.md4
-rw-r--r--docs/install/index.md8
-rw-r--r--docs/install/r400_external.md2
-rw-r--r--docs/install/t400_external.md2
-rw-r--r--docs/install/t500_external.md2
-rw-r--r--docs/install/t60_unbrick.md2
-rw-r--r--docs/install/x200_external.md2
-rw-r--r--docs/install/x60_unbrick.md2
-rw-r--r--docs/install/x60tablet_unbrick.md2
17 files changed, 24 insertions, 24 deletions
diff --git a/docs/bsd/freebsd.md b/docs/bsd/freebsd.md
index 9557ae45..0148cf2f 100644
--- a/docs/bsd/freebsd.md
+++ b/docs/bsd/freebsd.md
@@ -138,7 +138,7 @@ because it doesn't exist.
In most cases, you should use the vesafb ROM images. Example filename:
libreboot\_ukdvorak\_vesafb.rom.
-won't boot\...something about file not found
+won't boot...something about file not found
---------------------------------------------
Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and
diff --git a/docs/bsd/netbsd.md b/docs/bsd/netbsd.md
index 28b4d2df..226b3b96 100644
--- a/docs/bsd/netbsd.md
+++ b/docs/bsd/netbsd.md
@@ -154,7 +154,7 @@ because it doesn't exist.
In most cases, you should use the vesafb ROM images. Example filename:
libreboot\_ukdvorak\_vesafb.rom.
-won't boot\...something about file not found
+won't boot...something about file not found
---------------------------------------------
Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and
diff --git a/docs/bsd/openbsd.md b/docs/bsd/openbsd.md
index fb596161..8c33e5df 100644
--- a/docs/bsd/openbsd.md
+++ b/docs/bsd/openbsd.md
@@ -174,7 +174,7 @@ because it doesn't exist.
In most cases, you should use the vesafb ROM images. Example filename:
libreboot\_ukdvorak\_vesafb.rom.
-Won't boot\...something about file not found
+Won't boot...something about file not found
---------------------------------------------
Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and
diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md
index 48dba39b..63c15c0f 100644
--- a/docs/gnulinux/encrypted_parabola.md
+++ b/docs/gnulinux/encrypted_parabola.md
@@ -645,7 +645,7 @@ correct ROM image, then run this alternative command:
# ./flash forceupdate libreboot.rom
-You should see "Verifying flash\... VERIFIED." written at the end of
+You should see "Verifying flash... VERIFIED." written at the end of
the flashrom output.
With this new configuration, Parabola can boot automatically and you
@@ -691,7 +691,7 @@ directory and update the flash chip contents:
# ./flash update libreboot.rom
-And wait for the "Verifying flash\... VERIFIED." Once you have done
+And wait for the "Verifying flash... VERIFIED." Once you have done
that, shut down and then boot up with your new configuration.
When done, delete GRUB (remember, we only needed it for the
diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md
index 09e2c288..d4038bfc 100644
--- a/docs/gnulinux/grub_cbfs.md
+++ b/docs/gnulinux/grub_cbfs.md
@@ -120,7 +120,7 @@ Extract grubtest.cfg from the ROM image {#extract_testconfig}
You can check the contents of the ROM image, inside CBFS:
- $ cd \.../libreboot\_util/cbfstool** $ ./cbfstool libreboot.rom
+ $ cd .../libreboot\_util/cbfstool** $ ./cbfstool libreboot.rom
print**
@@ -160,7 +160,7 @@ complains about a board mismatch, but you are sure that you chose the
correct ROM image, then run this alternative command:
# ./flash forceupdate libreboot.rom
-You should see **"Verifying flash\... VERIFIED."** written at the end
+You should see **"Verifying flash... VERIFIED."** written at the end
of the flashrom output. Once you have done that, shut down and then boot
up with your new test configuration.**
diff --git a/docs/gnulinux/grub_hardening.md b/docs/gnulinux/grub_hardening.md
index 780d2c03..918fd45b 100644
--- a/docs/gnulinux/grub_hardening.md
+++ b/docs/gnulinux/grub_hardening.md
@@ -139,7 +139,7 @@ First generate a GPG keypair to use for signing. Option RSA (sign only)
is ok.
**Warning:** GRUB does not read ASCII armored keys. When attempting to
-trust \... a key filename it will print error: bad signature
+trust ... a key filename it will print error: bad signature
mkdir --mode 0700 keys
gpg --homedir keys --gen-key
@@ -177,7 +177,7 @@ What remains now is to include the modifications into the image (rom):
cbfstool my.rom add -n grubtest.cfg -f my.grubtest.cfg -t raw
cbfstool my.rom add -n grubtest.cfg.sig -f my.grubtest.cfg.sig -t raw
-\... and flashing it.
+... and flashing it.
Copyright © 2017 Fedja Beader <fedja@protonmail.ch>\
diff --git a/docs/hardware/gm45_remove_me.md b/docs/hardware/gm45_remove_me.md
index d230c2a5..253b4b6e 100644
--- a/docs/hardware/gm45_remove_me.md
+++ b/docs/hardware/gm45_remove_me.md
@@ -439,7 +439,7 @@ actually be others on the X200.
0xBABA"*
In honour of the song *Baba O'Reilly* by *The Who* apparently. We're
-not making this stuff up\...
+not making this stuff up...
0x3ABA, 0x34BA, 0x40BA and more have been observed in the main Gbe
regions on the X200 factory.rom dumps. The checksums of the backup
diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md
index 7c55319e..e9eacd77 100644
--- a/docs/install/bbb_setup.md
+++ b/docs/install/bbb_setup.md
@@ -28,7 +28,7 @@ flashing on the ThinkPad X200, but it should work for other targets.
here is a photo of the setup for the teensy:
<http://h5ai.swiftgeek.net/IMG_20160601_120855.jpg>
-Onto the Beaglebone black\...
+Onto the Beaglebone black...
Hardware requirements
=====================
diff --git a/docs/install/c201.md b/docs/install/c201.md
index b8edc211..3e60711a 100644
--- a/docs/install/c201.md
+++ b/docs/install/c201.md
@@ -140,7 +140,7 @@ The resulting flash image can then be flashed back:
# flashrom -p host -w flash.img
You should also see within the output the following:\
-**"Verifying flash\... VERIFIED."**
+**"Verifying flash... VERIFIED."**
Shut down. The device will now boot to Libreboot.
@@ -192,7 +192,7 @@ programmer):
# flashrom -p *programmer* -w flash.img
You should also see within the output the following:\
-**"Verifying flash\... VERIFIED."**
+**"Verifying flash... VERIFIED."**
The device will now boot to Libreboot.
diff --git a/docs/install/index.md b/docs/install/index.md
index 6a947da6..8c504365 100644
--- a/docs/install/index.md
+++ b/docs/install/index.md
@@ -254,7 +254,7 @@ Use this to find out:
All good?
---------
-Excellent! Moving on\...
+Excellent! Moving on...
Download the *libreboot\_util.tar.xz* archive, and extract it. Inside,
you will find a directory called *flashrom*. This contains statically
@@ -277,7 +277,7 @@ correct ROM image, then run this alternative command:
$ sudo ./flash forceupdate [yourrom.rom](#rom)
-You should see **"Verifying flash\... VERIFIED."** written at the end
+You should see **"Verifying flash... VERIFIED."** written at the end
of the flashrom output. **Shut down** after you see this, and then boot
up again after a few seconds.
@@ -340,7 +340,7 @@ You should see within the output the following:\
untranslated"**
You should also see within the output the following:\
-**"Verifying flash\... VERIFIED."**
+**"Verifying flash... VERIFIED."**
MacBook2,1: Initial installation guide (if running the proprietary firmware) {#flashrom_macbook21}
============================================================================
@@ -370,7 +370,7 @@ Use this flashing script, to install libreboot:
$ sudo ./flash i945apple\_firstflash [yourrom.rom](#rom)
You should also see within the output the following:\
-**"Verifying flash\... VERIFIED."**
+**"Verifying flash... VERIFIED."**
Shut down.
diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md
index 7c87b08d..83049200 100644
--- a/docs/install/r400_external.md
+++ b/docs/install/r400_external.md
@@ -270,7 +270,7 @@ path/to/libreboot/rom/image.rom -V
![](images/x200/disassembly/0015.jpg)
-You might see errors, but if it says **Verifying flash\... VERIFIED** at
+You might see errors, but if it says **Verifying flash... VERIFIED** at
the end, then it's flashed and should boot. If you see errors, try
again (and again, and again); the message **Chip content is identical to
the requested image** is also an indication of a successful
diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md
index bb3a93e2..11e98535 100644
--- a/docs/install/t400_external.md
+++ b/docs/install/t400_external.md
@@ -268,7 +268,7 @@ path/to/libreboot/rom/image.rom -V
![](images/x200/disassembly/0015.jpg)
-You might see errors, but if it says **Verifying flash\... VERIFIED** at
+You might see errors, but if it says **Verifying flash... VERIFIED** at
the end, then it's flashed and should boot. If you see errors, try
again (and again, and again); the message **Chip content is identical to
the requested image** is also an indication of a successful
diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md
index 05f418c8..4cee6b3e 100644
--- a/docs/install/t500_external.md
+++ b/docs/install/t500_external.md
@@ -285,7 +285,7 @@ path/to/libreboot/rom/image.rom -V
![](images/x200/disassembly/0015.jpg)
-You might see errors, but if it says **Verifying flash\... VERIFIED** at
+You might see errors, but if it says **Verifying flash... VERIFIED** at
the end, then it's flashed and should boot. If you see errors, try
again (and again, and again); the message **Chip content is identical to
the requested image** is also an indication of a successful
diff --git a/docs/install/t60_unbrick.md b/docs/install/t60_unbrick.md
index 9fd49bbf..e3469074 100644
--- a/docs/install/t60_unbrick.md
+++ b/docs/install/t60_unbrick.md
@@ -147,7 +147,7 @@ SSH'd into the BBB:
yourrom.rom
-It should be **Verifying flash\... VERIFIED** at the end. If flashrom
+It should be **Verifying flash... VERIFIED** at the end. If flashrom
complains about multiple flash chip definitions detected, then choose
one of them following the instructions in the output.
diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md
index 2cce70ba..05ba3063 100644
--- a/docs/install/x200_external.md
+++ b/docs/install/x200_external.md
@@ -184,7 +184,7 @@ Now flash it:
![](images/x200/disassembly/0015.jpg)
-You might see errors, but if it says **Verifying flash\... VERIFIED** at
+You might see errors, but if it says **Verifying flash... VERIFIED** at
the end, then it's flashed and should boot. If you see errors, try
again (and again, and again); the message **Chip content is identical to
the requested image** is also an indication of a successful
diff --git a/docs/install/x60_unbrick.md b/docs/install/x60_unbrick.md
index 2493e56a..233209c9 100644
--- a/docs/install/x60_unbrick.md
+++ b/docs/install/x60_unbrick.md
@@ -132,7 +132,7 @@ SSH'd into the BBB:
yourrom.rom
-It should be **Verifying flash\... VERIFIED** at the end. If flashrom
+It should be **Verifying flash... VERIFIED** at the end. If flashrom
complains about multiple flash chip definitions detected, then choose
one of them following the instructions in the output.
diff --git a/docs/install/x60tablet_unbrick.md b/docs/install/x60tablet_unbrick.md
index f18e3629..0386cc1b 100644
--- a/docs/install/x60tablet_unbrick.md
+++ b/docs/install/x60tablet_unbrick.md
@@ -111,7 +111,7 @@ SSH'd into the BBB:
yourrom.rom
-It should be **Verifying flash\... VERIFIED** at the end. If flashrom
+It should be **Verifying flash... VERIFIED** at the end. If flashrom
complains about multiple flash chip definitions detected, then choose
one of them following the instructions in the output.
generated by cgit v1.2.3-70-g09d2 (git 2.47.0) at 2024-11-22 11:24:33 +0000