diff --git a/README.md b/README.md
index 2560c51..2664ba4 100644
--- a/README.md
+++ b/README.md
@@ -514,7 +514,7 @@ in this catalog whose remedy is a manual bump, not a re-run.
 Two senses of *bare* meet here, and the gap between them is the **rc release
 path** — the one door an operator actually walks through. decide calls a
 version bare when it is not `-dev`
-([version_is_dev](lib/version.sh#L69-L76) matches that suffix and nothing
+([version_is_dev](lib/version.sh#L68-L76) matches that suffix and nothing
 else), so row 6 admits a transition to `1.2.3-rc1`, and a labeled rc ceremony
 is designed to ship ([lib/decide.sh](lib/decide.sh#L108-L110)).
 `version_next_dev` means `^[0-9]+\.[0-9]+\.[0-9]+$`. An rc sits between the
@@ -532,7 +532,7 @@ rows 1–2 send `-dev` to a no-op, and the tag door never bumps.
 
 [L106](lib/version.sh#L106): the package-json backend needs npm to write —
 `npm pkg set version=` plus a lockfile-only `npm install`
-([L102–L112](lib/version.sh#L102-L112)), never `npm version`, which would tag
+([L114–L115](lib/version.sh#L114-L115)), never `npm version`, which would tag
 — and the runner has none. The read path fails the
 same way one step earlier (`node is required…`, above), so a run reaching
 *this* message got past the read — set up node/npm in the caller.