@@ -280,13 +280,13 @@ we're just not there yet.
280280
281281```
282282# Run a nightly build
283−/opt/stackage-build/stackage/automated/run-nightly.sh
283+/var/stackage/stackage/automated/run-nightly.sh
284284
285285# Run an LTS minor bump
286−/opt/stackage-build/stackage/automated/build-next.sh lts-14.17
286+/var/stackage/stackage/automated/build.sh lts-15.1
287287
288288# Run an LTS major bump
289−/opt/stackage-build/stackage/automated/build-next.sh lts-15.0
289+/var/stackage/stackage/automated/build.sh lts-16.0
290290```
291291
292292Recommended: run these from inside a `tmux` session. If you get version bound
@@ -294,7 +294,7 @@ problems on nightly or LTS major, you need to fix build-constraints.yaml (see
294294info above).
295295
296296### Building LTS minor releases
297−First run `build-next.sh` to regenerate updated `ltsXX/work/constraints.yaml` and `ltsXX/work/snapshot-incomplete.yaml` files.
297+First run `build.sh` to regenerate updated `ltsXX/work/constraints.yaml` and `ltsXX/work/snapshot-incomplete.yaml` files.
298298
299299For an LTS minor bump, you'll typically want to:
300300
@@ -302,9 +302,9 @@ For an LTS minor bump, you'll typically want to:
302302* Add new packages to the `constraints.yaml` file
303303* Test, benchmark, haddock failures can also be added to package fields in the `constraints.yaml` if necessary, though it should be avoided if possible for LTS.
304304
305−Then run `NOPLAN=1 build-next.sh` to build the generate an updated snapshot.
305+Then run `NOPLAN=1 build.sh` to build the generate an updated snapshot.
306306
307−This replaces `CONSTRAINTS=...' /opt/stackage-build/stackage/automated/build.sh lts-x.y` for the old curator-1.
307+This replaces `CONSTRAINTS=...' /var/stackage/stackage/automated/build.sh lts-x.y` for the old curator-1.
308308
309309If a build fails for bounds reasons, see all of the advice above. If the code
310310itself doesn't build, or tests fail, open up an issue and then either put in a