@@ -107,7 +107,7 @@ means you tried to pound a square peg into a round hole.
107107What was the peg and what was the hole? Hoon doesn't tell you by
108108default, because moral fiber, and also because in too many cases
109109trivial errors lead to large intimidating dumps. However, you
110−can use the `~!` rune ([**sigzap**](@/docs/reference/hoon-expressions/rune/sig.md#sigzap)) to print the type of any hoon in your stack trace.
110+can use the `~!` rune ([**sigzap**](@/docs/hoon/reference/rune/sig.md#sigzap)) to print the type of any hoon in your stack trace.
111111
112112For instance, you wrote `(foo bar)` and got a `nest-fail`. Change
113113your code to be:
@@ -149,7 +149,7 @@ infinite loop will time out either too slowly or too fast). The
149149stack trace will show what your code was doing when interrupted.
150150
151151The counterpart of `~!` for runtime crashes is `~|`
152−([**sigbar**](@/docs/reference/hoon-expressions/rune/sig.md#sigbar)):
152+([**sigbar**](@/docs/hoon/reference/rune/sig.md#sigbar)):
153153
154154```hoon
155155~| foo
@@ -165,7 +165,7 @@ The worst possibility, of course, is that your code runs but does
165165the wrong thing. This is relatively unusual in a typed
166166functional language, but it still happens.
167167
168−`~&` ([**sigpam**](@/docs/reference/hoon-expressions/rune/sig.md#sigpam)) is Hoon's debugging printf.
168+`~&` ([**sigpam**](@/docs/hoon/reference/rune/sig.md#sigpam)) is Hoon's debugging printf.
169169This pretty-prints its argument:
170170
171171```hoon
@@ -174,7 +174,7 @@ This pretty-prints its argument:
174174```
175175
176176will always print `foo` every time it executes. A variant is
177−`~?` ([**sigwut**](@/docs/reference/hoon-expressions/rune/sig.md#sigwut)), which prints only if a condition is
177+`~?` ([**sigwut**](@/docs/hoon/reference/rune/sig.md#sigwut)), which prints only if a condition is
178178true:
179179
180180```hoon