diff options
| author | Alyssa Rosenzweig <alyssa@rosenzweig.io> | 2017-03-17 23:12:09 -0700 |
|---|---|---|
| committer | Alyssa Rosenzweig <alyssa@rosenzweig.io> | 2017-03-17 23:12:09 -0700 |
| commit | b62dbec1e23f03ae944b51fc4b510dc56ed9b83e (patch) | |
| tree | 1a0818a57127c0f878ea924e1d0fb3f139e766d7 /docs/gnulinux | |
| parent | 1eea5f7224362dcfce377dc0c99ad8a499c3ce6b (diff) | |
| download | librebootfr-b62dbec1e23f03ae944b51fc4b510dc56ed9b83e.tar.gz librebootfr-b62dbec1e23f03ae944b51fc4b510dc56ed9b83e.zip | |
Typographically correct ellipse
Diffstat (limited to 'docs/gnulinux')
| -rw-r--r-- | docs/gnulinux/encrypted_parabola.md | 4 | ||||
| -rw-r--r-- | docs/gnulinux/grub_cbfs.md | 4 | ||||
| -rw-r--r-- | docs/gnulinux/grub_hardening.md | 4 |
3 files changed, 6 insertions, 6 deletions
diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md index 36a60c61..f6c022a0 100644 --- a/docs/gnulinux/encrypted_parabola.md +++ b/docs/gnulinux/encrypted_parabola.md @@ -571,7 +571,7 @@ Ocassionally, coreboot changes the name of a given board. If flashrom 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 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 @@ -609,7 +609,7 @@ Now you have a modified ROM. Once more, refer to <http://libreboot.org/docs/install/#flashrom>. Cd to the libreboot\_util 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 7bba7730..745e47d4 100644 --- a/docs/gnulinux/grub_cbfs.md +++ b/docs/gnulinux/grub_cbfs.md @@ -155,7 +155,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** The files *grub.cfg* and *grubtest.cfg* should be present. grub.cfg is @@ -198,7 +198,7 @@ Ocassionally, coreboot changes the name of a given board. If flashrom 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 cad4ca40..ebd28645 100644 --- a/docs/gnulinux/grub_hardening.md +++ b/docs/gnulinux/grub_hardening.md @@ -146,7 +146,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 @@ -184,7 +184,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. |