aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--chapter02/aboutlfs.xml16
1 files changed, 7 insertions, 9 deletions
diff --git a/chapter02/aboutlfs.xml b/chapter02/aboutlfs.xml
index 1c15be452..de840e166 100644
--- a/chapter02/aboutlfs.xml
+++ b/chapter02/aboutlfs.xml
@@ -22,13 +22,11 @@ This way $LFS can be entered literally instead of replacing it with
<para><screen><userinput>export LFS=/mnt/lfs</userinput></screen></para>
-<para>Now, if you are told to run a command like </para>
-
-<para><screen><userinput>./configure --prefix=$LFS/static</userinput></screen></para>
-
-<para>you can type that literally. Your shell will
-replace $LFS with /mnt/lfs when it processes the command line (meaning
-when you hit enter after having typed the command).</para>
+<para>Now, if you are told to run a command such as
+<userinput>./configure --prefix=$LFS/static</userinput>, then you may type
+it literally. Your shell will replace $LFS with /mnt/lfs when it processes
+the command line (meaning when you hit enter after having typed the
+command).</para>
<para>If you plan to use $LFS, do not forget to set the $LFS variable at all
times. If the variable is not set and is used in a command, $LFS will
@@ -40,8 +38,8 @@ destroy your current password database file.</para>
<para>One way to make sure that $LFS is set at all times is adding it to
the /root/.bash_profile and /root/.bashrc files so that every time
-you login as user root, or you 'su' to user root, the $LFS variable is
-set.</para>
+you login as user root, or you <userinput>su</userinput> to user root,
+the $LFS variable is set.</para>
</sect1>