@@ -353,30 +353,7 @@ To see other irregular expressions, check the irregular expression [reference do
353353
354354## Hoon Style
355355
356−In this section we'll talk about preferred Hoon code style. Strictly speaking, all the guidelines in this section are optional -- if you follow the minimum syntax rules, your code should parse and run correctly. On the other hand, code clarity and maintainability are important. We think the following guidelines will help you to write better, clearer code. None of these rules is absolute, however -- use your judgment about what looks neat and clear.
357−
358−### Code Margin, Blank Lines
359−
360−An 80-column right margin is strongly encouraged. Really well-groomed Hoon uses a 55-column code margin and puts a standard line comment at column 57. Use `::` to begin a comment -- Hoon will ignore everything past the `::` until the line break. Here's an example of code that follows these principles:
361−
362−```
363−|= a=@ :: even number checker
364−^- ? :: output is a flag
365−=(0 (mod a 2)) :: =(...) evals to flag
366−```
367−
368−Blank lines are discouraged. If you want vertical space in your code, use `::` at the beginning of one or more lines.
369−
370−```
371−|= a=@ :: even number checker
372−^- ? :: output is a flag
373−::
374−:: lots
375−:: of
376−:: space
377−::
378−=(0 (mod a 2)) :: =(...) evals to flag
379−```
356+See [Hoon Style Guide](/docs/learn/arvo/style).
380357
381358### Rune Expression Body Types
382359