Rename directory toolchain/ to toolchains/

To be consistent with machines/

1 files changed, 4 insertions, 4 deletions

diff --git a/doc/manual.cli b/doc/manual.cli
index 7284c6a..cc55115 100644
--- a/doc/manual.cli
+++ b/doc/manual.cli
@@ -68,7 +68,7 @@ the following subdirectories:
   sub-directories inside this directory temporarily write-accessible to build
   machines by running custom instances of the TFTP server on other ports.|
 
-\li|\n\c{/build/toolchain/}\n
+\li|\n\c{/build/toolchains/}\n
 
   Contains \c{build2} toolchain installations after bootstrap. Each version
   is installed into a subdirectory named as the toolchain name. See
@@ -77,7 +77,7 @@ the following subdirectories:
 \li|\n\c{/build/bbot/}\n
 
   Contains \c{bbot} installations. Each version is installed into a
-  subdirectory names as the toolchain name. See \l{#config-toolchains
+  subdirectory named as the toolchain name. See \l{#config-toolchains
   Toolchains} for details.|
 
 \li|\n\c{/build/machines/}\n
@@ -339,7 +339,7 @@ e723[...]c305 *0.4.0/build2-mingw-0.4.0-x86_64-windows.tar.xz
 \
 
 Based on the checksums file the monitor downloads each file into
-\c{/build/tftp/toolchain/<name>/} (the file path is taken as relative to
+\c{/build/tftp/toolchains/<name>/} (the file path is taken as relative to
 \c{toolchain_url}), verifies their checksums, and creates \i{predictable name}
 symlinks (names without the version). It also creates the \c{version} which
 contains the toolchain version and the \c{trust} file which contains the
@@ -347,7 +347,7 @@ value of the \c{buildos.toolchain_trust} parameter or the special \c{\"no\"}
 value if none were specified.
 
 Continuing with the above example, the contents of
-\c{/build/tftp/toolchain/default/} would be:
+\c{/build/tftp/toolchains/default/} would be:
 
 \
 version