gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

More spelling fixes

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11252 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Bruce Dubbs 2017-05-14 05:52:34 +00:00
parent 26a1b335e7
commit 1af5572aaa
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
chapter01/changelog.xml
View File

@ -338,7 +338,7 @@
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>[bdubbs] - Update to binutils-2.28. Moved m4 and <para>[bdubbs] - Update to binutils-2.28. Moved m4 and
bc to before binutils to accomodate the gold linker bc to before binutils to accommodate the gold linker
regression tests. Fixes regression tests. Fixes
<ulink url="&lfs-ticket-root;4059">#4059</ulink>.</para> <ulink url="&lfs-ticket-root;4059">#4059</ulink>.</para>
</listitem> </listitem>

2
chapter02/creatingpartition.xml
View File

@ -124,7 +124,7 @@
<note><para>The Grub Bios partition must be on the drive that the BIOS <note><para>The Grub Bios partition must be on the drive that the BIOS
uses to boot the system. This is not necessarily the same drive where the uses to boot the system. This is not necessarily the same drive where the
LFS root partition is located. Disks on a system may use different LFS root partition is located. Disks on a system may use different
partition table types. The requirment for this partition depends partition table types. The requirement for this partition depends
only on the partition table type of the boot disk.</para></note> only on the partition table type of the boot disk.</para></note>
</sect3> </sect3>

4
chapter07/systemd-custom.xml
View File

@ -111,7 +111,7 @@ EOF</userinput></screen>
<para>Rather than plain shell scripts used in SysVinit or BSD style init <para>Rather than plain shell scripts used in SysVinit or BSD style init
systems, systemd uses a unified format for different types of startup systems, systemd uses a unified format for different types of startup
files (or units). The command <command>systemctl</command> is used to files (or units). The command <command>systemctl</command> is used to
enable, disable, controll state, and obtain status of unit files. Here enable, disable, control state, and obtain status of unit files. Here
are some examples of frequently used commands:</para> are some examples of frequently used commands:</para>
<itemizedlist> <itemizedlist>
@ -163,7 +163,7 @@ EOF</userinput></screen>
</listitem> </listitem>
<listitem> <listitem>
<para><command>journalctl -b[=ID] -r</command>: shows the journal <para><command>journalctl -b[=ID] -r</command>: shows the journal
entries since last successfull boot (or for boot ID) in reverse entries since last successful boot (or for boot ID) in reverse
chronological order.</para> chronological order.</para>
</listitem> </listitem>
<listitem> <listitem>