Typographically correct ellipse

18 files changed, 27 insertions, 27 deletions

diff --git a/docs/bsd/freebsd.md b/docs/bsd/freebsd.md
index f57144f9..a2691704 100644
--- a/docs/bsd/freebsd.md
+++ b/docs/bsd/freebsd.md
@@ -156,7 +156,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 4f6385b9..7f4dcd7c 100644
--- a/docs/bsd/netbsd.md
+++ b/docs/bsd/netbsd.md
@@ -173,7 +173,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 8dffa3d6..50904bb9 100644
--- a/docs/bsd/openbsd.md
+++ b/docs/bsd/openbsd.md
@@ -194,7 +194,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/future/index.md b/docs/future/index.md
index fd9aaeaa..557782ec 100644
--- a/docs/future/index.md
+++ b/docs/future/index.md
@@ -94,13 +94,13 @@ stefanct: vimuser: they suggest that you change the value and look how
 BSM reacts to that\
 stefanct: as they pointed out earlier vram size = TOM - BSM\
 stefanct: different values of GMS\
-stefanct: phcoder: hm\... this could be a hint. look at the text
+stefanct: phcoder: hm... this could be a hint. look at the text
 description of TOLUD at page 103\
 stefanct: it mentions 64 MB in the text about BSM as well\
-stefanct: table 18\...\
+stefanct: table 18...\
 phcoder: stefanct: I have a guess which value make is 64 but I will not
 tell to avoid skewing test results\
-stefanct: phcoder: sure\... i assumed you were not sure if it supports
+stefanct: phcoder: sure... i assumed you were not sure if it supports
 it at all. testing it properly is of course a good idea :)\
 stefanct: test the various possible (but reserved) values of GMS and see
 what the resulting VRAM size is\
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.
 
 
 
diff --git a/docs/hcl/gm45_remove_me.md b/docs/hcl/gm45_remove_me.md
index 350e048c..bd20cdfc 100644
--- a/docs/hcl/gm45_remove_me.md
+++ b/docs/hcl/gm45_remove_me.md
@@ -440,7 +440,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 3c66a58e..4a219c39 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...
 
 [Back to previous index](./)
 
diff --git a/docs/install/c201.md b/docs/install/c201.md
index 2f7240ce..fb4eb2f7 100644
--- a/docs/install/c201.md
+++ b/docs/install/c201.md
@@ -164,7 +164,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.
 
@@ -212,7 +212,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 7c28613a..c11d6ca2 100644
--- a/docs/install/index.md
+++ b/docs/install/index.md
@@ -259,7 +259,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
@@ -285,7 +285,7 @@ $ **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.
 
@@ -357,7 +357,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."**
 
 
 [Back to top of page.](#pagetop)
@@ -398,7 +398,7 @@ $ **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 48016e65..a6edcab2 100644
--- a/docs/install/r400_external.md
+++ b/docs/install/r400_external.md
@@ -275,7 +275,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 67e1471c..347c1932 100644
--- a/docs/install/t400_external.md
+++ b/docs/install/t400_external.md
@@ -281,7 +281,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 0843ff87..239b7d25 100644
--- a/docs/install/t500_external.md
+++ b/docs/install/t500_external.md
@@ -286,7 +286,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 79dec613..fa5a77a1 100644
--- a/docs/install/t60_unbrick.md
+++ b/docs/install/t60_unbrick.md
@@ -160,7 +160,7 @@ SSH'd into the BBB:\
 # **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w
 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 12570a8c..fd4af287 100644
--- a/docs/install/x200_external.md
+++ b/docs/install/x200_external.md
@@ -215,7 +215,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/x60_unbrick.md b/docs/install/x60_unbrick.md
index ae79a40f..c02f3ff9 100644
--- a/docs/install/x60_unbrick.md
+++ b/docs/install/x60_unbrick.md
@@ -145,7 +145,7 @@ SSH'd into the BBB:\
 # **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w
 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 d918675b..afbfd7ac 100644
--- a/docs/install/x60tablet_unbrick.md
+++ b/docs/install/x60tablet_unbrick.md
@@ -124,7 +124,7 @@ SSH'd into the BBB:\
 # **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w
 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.