Update bootstrap script

1 files changed, 5 insertions, 5 deletions

diff --git a/bootstrap b/bootstrap
index 4eb33ff..7bf11f5 100755
--- a/bootstrap
+++ b/bootstrap
@@ -21,8 +21,8 @@
 #    For the latter case they would typically go to ~/work/{cli,odb/}, for
 #    example, for CLI:
 #
-#    NOTE: clone using the git.codesynthesis.com:/var/scm/... SSH URL for rw
-#          access.
+#    NOTE: clone using the git.codesynthesis.com:/var/scm/... SSH URL if you
+#          have rw access.
 #
 #    mkdir -p ~/work/cli
 #    cd ~/work/cli
@@ -32,7 +32,7 @@
 #      config.cxx=g++-N                             \
 #      config.cc.coptions="-Wall -Wextra -Werror -g3 -fsanitize=address -fsanitize=undefined -fno-omit-frame-pointer"
 #    b
-#    sudo ln -s "$(pwd)/cli/cli" /usr/local/bin/cli
+#    sudo ln -s "$(pwd)/cli/cli/cli" /usr/local/bin/cli
 #    which cli
 #    cli --version
 #
@@ -55,7 +55,7 @@
 # Once this is done, you should be able to:
 #
 # NOTE: clone using the git.build2.org:/var/scm/... SSH URL and pass the
-#       --ssh bootstrap option for rw access.
+#       --ssh bootstrap option if you have rw access.
 #
 # mkdir -p ~/work/build2
 # cd ~/work/build2
@@ -70,7 +70,7 @@
 # functioning correctly but to fix this you need to be able to run those
 # tools. This can happen, for example, because of the linking errors or
 # because the version (and therefore the name) of one of the shared libraries
-# has changed as a result of updating another part of a toolchain (for
+# has changed as a result of updating another part of the toolchain (for
 # instance, updating bpkg can trigger an update of libbpkg and this could make
 # bdep, which also depends on libbpkg, no longer runnable).
 #