Fixed a common misspelling. "setup" is a noun. When "set up" is a

phrasal verb, it is spelled as two words. This commit fixes most of
the misspelled "set up" instances in the BLFS book.
This commit is contained in:
David Bryant 2022-12-12 14:17:31 -06:00
parent df210c3463
commit b59e5eb3ea
9 changed files with 18 additions and 18 deletions

View File

@ -48,7 +48,7 @@
</para>
<sect3>
<title>1. Setup Users, Groups, and Permissions</title>
<title>1. Set Up Users, Groups, and Permissions</title>
<para>
You will need to be user <systemitem class='username'>root</systemitem>
@ -161,7 +161,7 @@ chown -R git:git .</userinput></screen>
EOF</userinput></screen>
<para>
On the developer's machine, setup some files to be pushed
On the developer's machine, set up some files to be pushed
to the repository as the initial content:
</para>

View File

@ -97,7 +97,7 @@ mandb -c /opt/jdk/man</userinput></screen>
<filename>/etc/ssl/java/cacerts</filename>. The instructions
on the <xref linkend="make-ca"/> page previously created the file
located in <filename class="directory">/etc/ssl/java</filename>.
Setup a symlink in the default location as the
Set up a symlink in the default location as the
<systemitem class="username">root</systemitem> user:
</para>

View File

@ -608,7 +608,7 @@ php ./go-pear.phar</userinput></screen>
<para>
Additionally, it may be useful to add an entry for
<filename>index.php</filename> to the DirectoryIndex directive of the
<filename>httpd.conf</filename> file. Lastly, adding a line to setup the
<filename>httpd.conf</filename> file. Lastly, adding a line to set up the
<filename class='extension'>.phps</filename> extension to show
highlighted <application>PHP</application> source may be
desirable:

View File

@ -46,7 +46,7 @@
</para>
<sect3>
<title>1. Setup Users, Groups, and Permissions</title>
<title>1. Set Uup Users, Groups, and Permissions</title>
<para>
You'll need to be user
@ -128,7 +128,7 @@ svnadmin create /srv/svn/repositories/svntest</userinput></screen>
something useful. You'll need to have a predefined directory
layout set up exactly as you want your repository to look. For
example, here is a sample BLFS layout setup with a root of
<filename>svntest/</filename>. You'll need to setup a directory
<filename>svntest/</filename>. You'll need to set up a directory
tree similar to the following:
</para>

View File

@ -294,7 +294,7 @@ make</userinput></screen>
<bridgehead renderas="sect4">Periodic Jobs</bridgehead>
<para>
If you would like to setup a periodic hierarchy for the root user,
If you would like to set up a periodic hierarchy for the root user,
first issue the following commands (as the
<systemitem class="username">root</systemitem> user) to create the
<filename>/usr/bin/run-parts</filename> script:

View File

@ -233,7 +233,7 @@ install -v -m 644 dhcpcd-hooks/50-dhcpcd-compat /lib/dhcpcd/dhcpcd-hooks/</useri
and <filename>/etc/ntp.conf</filename>. These
modifications to system files are done by hooks which are stored in
<filename class="directory">/usr/lib/dhcpcd/dhcpcd-hooks</filename>.
Setup <command>dhcpcd</command> by removing or adding hooks from/to
Set up <command>dhcpcd</command> by removing or adding hooks from/to
that directory. The execution of hooks can be disabled by using
the <option>--nohook</option> (<option>-C</option>) command line
option or by the <option>nohook</option> option in the
@ -335,7 +335,7 @@ EOF</userinput></screen>
</filename> and <filename>/etc/ntp.conf</filename>. These
modifications to system configuration files are done by hooks which
are stored in <filename class="directory">
/lib/dhcpcd/dhcpcd-hooks</filename>. Setup <command>dhcpcd</command>
/lib/dhcpcd/dhcpcd-hooks</filename>. Set up <command>dhcpcd</command>
by removing or adding hooks from/to that directory. The execution
of hooks can be disabled by using the <option>--nohook</option>
(<option>-C</option>) command line option or by the

View File

@ -14,7 +14,7 @@
<!-- [pierre 2021-11-11]: quick test seems to be much smaller than previously.
I'll update anyway since this is a high priority release: feel free
to update figures. I seem to have all the optional dependencies that
are in the book, in addition to the python venv as setup in the
are in the book, in addition to the python venv as set up in the
instructions below. -->
<sect1 id="samba" xreflabel="Samba-&samba-version;">
<?dbhtml filename="samba.html"?>
@ -245,7 +245,7 @@ make</userinput></screen>
<!--
If doing a security update or a new minor version (point releases do not
apply here), run 'make testenv' before running 'make test' and 'make
subunit-test'. This will setup the test environment and make the tests
subunit-test'. This will set up the test environment and make the tests
run faster, as well as point out any glaring issues that might affect
the new Samba installation. With 4.10.4, I got 236 failures, 73 errors,
and 2 unexpected successes. These were all known upstream, and you can
@ -323,7 +323,7 @@ install -v -m755 examples/LDAP/{get*,ol*} \
<parameter>--without-ad-dc</parameter>: Disables
Active Directory Domain Controller functionality. See <ulink url=
"https://wiki.samba.org/index.php/Setup_a_Samba_Active_Directory_Domain_Controller">
Setup a Samba Active Directory Domain Controller</ulink> for detailed
Set up a Samba Active Directory Domain Controller</ulink> for detailed
information. Remove this switch if you've installed the Python modules
needed for ADS support. Note that BLFS does not provide a samba bootscript
or systemd unit for an Active Directory domain controller.

View File

@ -166,7 +166,7 @@ if [ $EUID -eq 0 ] ; then
unset HISTFILE
fi
# Setup some environment variables.
# Set up some environment variables.
export HISTSIZE=1000
export HISTIGNORE="&amp;:[bf]g:exit"
@ -175,7 +175,7 @@ export XDG_DATA_DIRS=${XDG_DATA_DIRS:-/usr/share/}
export XDG_CONFIG_DIRS=${XDG_CONFIG_DIRS:-/etc/xdg/}
export XDG_RUNTIME_DIR=${XDG_RUNTIME_DIR:-/tmp/xdg-$USER}
# Setup a red prompt for root and a green one for users.
# Set up a red prompt for root and a green one for users.
NORMAL="\[\e[0m\]"
RED="\[\e[1;31m\]"
GREEN="\[\e[1;32m\]"
@ -364,7 +364,7 @@ EOF</userinput></screen>
</para>
<screen role="root"><userinput>cat &gt; /etc/profile.d/readline.sh &lt;&lt; "EOF"
<literal># Setup the INPUTRC environment variable.
<literal># Set up the INPUTRC environment variable.
if [ -z "$INPUTRC" -a ! -f "$HOME/.inputrc" ] ; then
INPUTRC=/etc/inputrc
fi

View File

@ -356,7 +356,7 @@ startlxde &amp;</screen>
systemd aware for VNC sessions and allows desktop environments like
<application>GNOME</application> to autostart services once the VNC
session is started. This configuration also gives the added benefit
of starting VNC Sessions on system startup. To setup the VNC server
of starting VNC Sessions on system startup. To set up the VNC server
in this fashion, follow these instructions.
</para>
@ -369,7 +369,7 @@ startlxde &amp;</screen>
install -v -m755 ../Xsession /etc/X11/tigervnc</userinput></screen>
<para revision="systemd">
Next, setup a user mapping in
Next, set up a user mapping in
<filename>/etc/tigervnc/vncserver.users</filename>. This tells the VNC
Server which session is allocated to a user.
<!-- For example: :1=renodr will assign 'renodr' to :1 -->
@ -378,7 +378,7 @@ install -v -m755 ../Xsession /etc/X11/tigervnc</userinput></screen>
<screen role="root" revision="systemd"><userinput>echo ":1=$(whoami)" >> /etc/tigervnc/vncserver.users</userinput></screen>
<para revision="systemd">
Next, setup a configuration file to tell
Next, set up a configuration file to tell
<application>vncserver</application> which desktop environment should be
used and what display geometry should be used. There are several other
options that can be defined in this file, but they are outside the scope