diff --git a/docs/CODE_STYLE.md b/docs/CODE_STYLE.md
index 248d76107..8f1c1cb58 100644
--- a/docs/CODE_STYLE.md
+++ b/docs/CODE_STYLE.md
@@ -12,9 +12,9 @@ directive](https://github.com/golangci/golangci-lint#nolint), e.g.  `var
 bad_name int //nolint:golint,unused`. This should be used sparingly and only
 when its clear that the lint warning is spurious.
 
-The linters can be run using [scripts/find-lint.sh](scripts/find-lint.sh)
+The linters can be run using [build/scripts/find-lint.sh](/build/scripts/find-lint.sh)
 (see file for docs) or as part of a build/test/lint cycle using
-[scripts/build-test-lint.sh](scripts/build-test-lint.sh).
+[build/scripts/build-test-lint.sh](/build/scripts/build-test-lint.sh).
 
 
 ## Labels
diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
index f2e3de4ae..30ef65ea9 100644
--- a/docs/CONTRIBUTING.md
+++ b/docs/CONTRIBUTING.md
@@ -49,7 +49,7 @@ To save waiting for CI to finish after every commit, it is ideal to run the
 checks locally before pushing, fixing errors first. This also saves other people
 time as only so many PRs can be tested at a given time.
 
-To execute what Buildkite tests, first run `./scripts/build-test-lint.sh`; this
+To execute what Buildkite tests, first run `./build/scripts/build-test-lint.sh`; this
 script will build the code, lint it, and run `go test ./...` with race condition
 checking enabled. If something needs to be changed, fix it and then run the
 script again until it no longer complains. Be warned that the linting can take a