@@ -22,7 +22,7 @@ a correct Hoon file. These values are always correct.
2222Usually, the line and column tell you everything you need to
2323know. But the worst-case scenario for a syntax error is that,
2424somewhere above, you've confused Hoon's tall form by using the
25−wrong fanout for a rune. For example, `%+` ([*cenlus*](../rune/cen/lus),
25+wrong fanout for a rune. For example, `%+` ([*cenlus*](/docs/reference/hoon-expressions/rune/cen#cenlus),
2626a function call whose sample is a cell) has three subhoons:
2727
2828```
@@ -102,7 +102,7 @@ means you tried to pound a square peg into a round hole.
102102What was the peg and what was the hole? Hoon doesn't tell you by
103103default, because moral fiber, and also because in too many cases
104104trivial errors lead to large intimidating dumps. However, you
105−can use the `~!` rune ([*sigzap*](../rune/sig/zap)) to print the type of
105+can use the `~!` rune ([*sigzap*](/docs/reference/hoon-expressions/rune/sig#sigzap)) to print the type of
106106any hoon in your stack trace.
107107
108108For instance, you wrote `(foo bar)` and got a `nest-fail`. Change
@@ -132,7 +132,7 @@ function.
132132
133133These are errors caused by type inference in pattern matching.
134134`mint-vain` means this hoon is never executed. `mint-lost` means
135−there's a case in a `?-` ([*wuthep*](../rune/wut/hep)) that isn't handled.
135+there's a case in a `?-` ([*wuthep*](./docs/reference/hoon-expressions/rune/wut#wuthep)) that isn't handled.
136136
137137## Runtime crashes
138138
@@ -146,7 +146,7 @@ infinite loop will time out either too slowly or too fast). The
146146stack trace will show what your code was doing when interrupted.
147147
148148The counterpart of `~!` for runtime crashes is `~|`
149−([*sigbar*](../rune/sig/bar)):
149+([*sigbar*](/docs/reference/hoon-expressions/rune/sig#sigbar)):
150150
151151```
152152~| foo
@@ -162,7 +162,7 @@ The worst possibility, of course, is that your code runs but does
162162the wrong thing. This is relatively unusual in a typed
163163functional language, but it still happens.
164164
165−`~&` ([*sigpad*](../rune/sig/pad)) is Hoon's debugging printf.
165+`~&` ([*sigpad*](/docs/reference/hoon-expressions/rune/sig#sigpad)) is Hoon's debugging printf.
166166This pretty-prints its argument:
167167
168168```
@@ -171,7 +171,7 @@ This pretty-prints its argument:
171171```
172172
173173will always print `foo` every time it executes. A variant is
174−`~?` ([*sigwut*](../rune/sig/wut)), which prints only if a condition is
174+`~?` ([*sigwut*](/docs/reference/hoon-expressions/rune/sig#sigwut)), which prints only if a condition is
175175true:
176176
177177```