diff --git a/site/docs/build/index.md b/site/docs/build/index.md
index b324b91fa58c5dc40fe75eda21a0e448bebb1c2c..d68fda6ef8c321071f55233d33e6811f7e72c269 100644
--- a/site/docs/build/index.md
+++ b/site/docs/build/index.md
@@ -203,7 +203,7 @@ re-inserted (e.g. KBC1126 EC firmware on HP EliteBooks). Please read this page
 for context:
 <https://libreboot.org/docs/install/ivy_has_common.html>
 
-The scripts under directory `script/update/vendor/` are the ones that do this.
+The scripts under directory `script/vendor/` are the ones that do this.
 Specifically, `script/vendor/download`. The benefit of this is that you
 do not need to extract anything from the original vendor image (e.g. Lenovo
 UEFI image).
diff --git a/site/docs/maintain/index.md b/site/docs/maintain/index.md
index 872a9eed16799564ed0b4e58a523c9262af53bb2..e989f6deec6a85ad763e271ad0fe432313c69a00 100644
--- a/site/docs/maintain/index.md
+++ b/site/docs/maintain/index.md
@@ -348,7 +348,7 @@ may not have much RAM.
 Where large files (or a large number of files) are handled by lbmk on a
 temporary basis, this `tmp/` directory is created and then used.
 
-vendor/
+vendorfiles/
 ---------------
 
 Used by the vendor file handler scripts, referenced in certain coreboot configs.
@@ -1036,7 +1036,13 @@ update
 ---------------
 
 Symbolic link, pointing to the `build` script. This is executed by the user, or
-by lbmk, referencing scripts under `script/update/*/`.
+by lbmk, referencing scripts under `script/update/`.
+
+vendor
+---------------
+
+Symbolic link, pointing to the `build` script. This is executed by the user, or
+by lbmk, referincing scripts under `script/vendor/`
 
 include/
 ===============
@@ -1095,7 +1101,7 @@ in the script at `script/vendor/download`, and it is used from there.
 include/option.sh
 ---------------
 
-Functions used by scripts under `script/update/vendor/`, for checking defconfig
+Functions used by scripts under `script/vendor/`, for checking defconfig
 files. These files are checked because the scripts need to know whether a given
 file is used; if it is, a path is then specified in defconfig, telling the vendor
 script either where it is, or where it should be downloaded to.