@@ -191,13 +191,13 @@ of secret superpowers for hacking the namespace. Remember that
191Hoon doesn't have anything like a symbol table; to resolve a
191Hoon doesn't have anything like a symbol table; to resolve a
192limb, we just search the type depth-first.
192limb, we just search the type depth-first.
194−If a name is in the `p.q.p` `map`, it's an alias. (An alias is defined using the
194+If a name is in the `p.p` `map`, it's an alias. (An alias is defined using the
195`=*` rune.) The map contains a `(unit hoon)`; if the unit is full, the name
195`=*` rune.) The map contains a `(unit hoon)`; if the unit is full, the name
196resolves to that hoon (compiled against the `q` type). If the unit is empty,
196resolves to that hoon (compiled against the `q` type). If the unit is empty,
197the name is blocked / skipped (see [limb](@/docs/reference/hoon-expressions/limb/limb.md) for what
197the name is blocked / skipped (see [limb](@/docs/reference/hoon-expressions/limb/limb.md) for what
198this means).
198this means).
200−If a name is the `p.p` `term`, it's a bridge. (A bridge is defined using the
200+If a name is the `q.p` `term`, it's a bridge. (A bridge is defined using the
201`=,` rune.) When we search for a name, we also compile the bridge, and check
201`=,` rune.) When we search for a name, we also compile the bridge, and check
202if the name resolves against the bridge product. If so, we use it.
202if the name resolves against the bridge product. If so, we use it.