Slight updates to Readme

diff --git a/Readme.txt b/Readme.txt
index eaff771d9007d0866a1b952604876994ff617b32..16def7c04c0f1062ac0892cd3085fc5c5d2fbb57 100644 (file)
--- a/Readme.txt
+++ b/Readme.txt
@@ -34,11 +34,10 @@ builds, cross-compilation and pkg-config integration.
 
 2. Building Builder
 
-Builder is normally built using itself.  However, if you just downloaded the
-source and don't yet have a Builder binary, how is that possible?  To resolve
-this problem, there's a script called bootstrap.sh in the Builder main
-directory.  Before running it, make sure you have the following libraries
-available:
+Builder is normally built using itself.  This creates a conundrum if you just
+downloaded the source and don't yet have a Builder binary.  To resolve the
+problem, there's a script called bootstrap.sh in the Builder main directory.
+Before running it, make sure you have the following libraries available:
 
 MSP libraries: core datafile
 
@@ -47,10 +46,9 @@ Others: sigc++-2.0
 You should be able to get the MSP libraries from the same place you got
 Builder itself from.  Since they are also normally built with Builder, the
 script will need to have their sources available.  By default, it will look at
-the parent directory of builder.  You can change this by setting the LIBPATH
-evironment variable for the script.  If everything goes well, the script will
-build a builder-stage1 binary and then proceed to build a normal version with
-it.
+the parent directory of builder.  You can change this with the --libpath
+parameter for the script.  If everything goes well, the script will build a
+builder-stage1 binary and then proceed to build a normal version with it.
 
 -------------------------------------------------------------------------------