aboutsummaryrefslogtreecommitdiff
path: root/docs/gnulinux/grub_cbfs.html
diff options
context:
space:
mode:
authorFrancis Rowe <info@gluglug.org.uk>2015-01-18 11:57:44 +0000
committerFrancis Rowe <info@gluglug.org.uk>2015-01-18 11:58:59 +0000
commit78067dd62a285731305b7a890da333d265ce6cad (patch)
tree499ecda40beb27d23dd39bb7f5689faf7ef4e9f2 /docs/gnulinux/grub_cbfs.html
parentc44ef19d49c16064bed8964557f102fb58a336e7 (diff)
downloadlibrebootfr-78067dd62a285731305b7a890da333d265ce6cad.tar.gz
librebootfr-78067dd62a285731305b7a890da333d265ce6cad.zip
Documentation: fix incorrect usage of apostrophes.
Diffstat (limited to 'docs/gnulinux/grub_cbfs.html')
-rw-r--r--docs/gnulinux/grub_cbfs.html14
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/gnulinux/grub_cbfs.html b/docs/gnulinux/grub_cbfs.html
index 8b5a8a61..5fb46dc5 100644
--- a/docs/gnulinux/grub_cbfs.html
+++ b/docs/gnulinux/grub_cbfs.html
@@ -31,7 +31,7 @@
filesystem inside called CBFS (coreboot filesystem). A utility called 'cbfstool'
allows you to change the contents of the ROM image. In this case, libreboot is configured
such that the 'grub.cfg' and 'grubtest.cfg' files exists directly inside CBFS instead of
- inside the GRUB payload's 'memdisk' (which is itself stored in CBFS).
+ inside the GRUB payload 'memdisk' (which is itself stored in CBFS).
</p>
<p>
@@ -102,7 +102,7 @@
<h2 id="which_rom">Which ROM image should I use?</h2>
<p>
- You can work directly with one of the ROM's already included in the libreboot ROM archives. For the purpose of
+ You can work directly with one of the ROM images already included in the libreboot ROM archives. For the purpose of
this tutorial it is assumed that your ROM is named <i>libreboot.rom</i> so please make sure to adapt.
</p>
@@ -120,7 +120,7 @@
<p>
If you currently have flashed a ROM image from an older version, it is recommended to update first:
- basically, modify one of the latest ROM's and then flash it.
+ basically, modify one of the latest ROM images and then flash it.
</p>
<p>
@@ -191,8 +191,8 @@
Yours might be different. In GRUB terms, sda means ahci0. 1 means msdos1, or gpt1, depending
on whether I am using MBR or GPT partitioning. Thus, /dev/sda1 is GRUB is (ahci0,msdos1) or
(ahci0,gpt1). In my case, I use MBR partitioning so it's (ahci0,msdos1).
- 'msdos' is GRUB's name simply because this partitioning type is traditionally used by MS-DOS.
- It doesn't mean you have a proprietary OS.
+ 'msdos' is a GRUB name simply because this partitioning type is traditionally used by MS-DOS.
+ It doesn't mean that you have a proprietary OS.
</p>
<p>
@@ -209,14 +209,14 @@
</p>
<p>
- For the GRUB payload's grubtest.cfg (in the 'Load Operating System' menu entry), we therefore have (in this example):<br/>
+ For the GRUB payload grubtest.cfg (in the 'Load Operating System' menu entry), we therefore have (in this example):<br/>
<b>set root='ahci0,msdos1'</b><br/>
<b>linux /vmlinuz root=UUID=3a008e14-4871-497b-95e5-fb180f277951</b><br/>
<b>initrd /initrd.img</b>
</p>
<p>
- Optionally, you can convert the UUID to it's real device name, for example /dev/sda1 in this case.
+ Optionally, you can convert the UUID to its real device name, for example /dev/sda1 in this case.
sdX naming isn't very reliable, though, which is why UUID is used for most distributions.
</p>