@@ -95,7 +95,7 @@ In this section we discuss the types most commonly used for Hoon parsers. In sho
96A `hair` is a pair of `@ud` used to keep track of what has already been parsed
96A `hair` is a pair of `@ud` used to keep track of what has already been parsed
97for stack tracing purposes. This allows the parser to reveal where the problem
97for stack tracing purposes. This allows the parser to reveal where the problem
98−is in case it hits something unexpected during parsing.
98+is in case it hits something unexpected during parsing.
100`p` represents the column and `q` represents the line.
100`p` represents the column and `q` represents the line.
@@ -139,7 +139,7 @@ of what is to be parsed. If `q` is not null, `p` and `p.q.q` are identical.
139++ rule _|:($:nail $:edge)
139++ rule _|:($:nail $:edge)
141A `rule` is a gate which takes in a `nail` and returns an `edge` - in other
141A `rule` is a gate which takes in a `nail` and returns an `edge` - in other
142−words, a parser.
142+words, a parser.
144## Parser builders
144## Parser builders
@@ -300,7 +300,7 @@ need to deal directly with `nail`s except where it is ilustrative to do so.
301### Parsing atoms
301### Parsing atoms
303−[Recall](@/docs/tutorials/hoon/lists.md) that `cord`s are atoms with the aura
303+[Recall](@/docs/tutorials/hoon/hoon-school/lists.md) that `cord`s are atoms with the aura
304`@t` and are typically used to represent strings internally as data, as atoms
304`@t` and are typically used to represent strings internally as data, as atoms
305are faster for the computer to work with than `tape`s, which are `list`s of
305are faster for the computer to work with than `tape`s, which are `list`s of
306`@tD` atoms. `+rash` and `+rush` are for parsing atoms, with `+rash` being
306`@tD` atoms. `+rash` and `+rush` are for parsing atoms, with `+rash` being
@@ -444,7 +444,7 @@ is more than one `rule`.
445syntax error
445syntax error
450## Parsing numbers
450## Parsing numbers