@@ -4,15 +4,12 @@ weight = 12
44template = "doc.html"
55+++
66
7−
8−## Move trace tutorial
9−
107In this tutorial we will run a simple "move trace" and use the output to get a
118picture of what the Arvo kernel proper does during the routine task of setting a
129timer. Some level of familiarity with the kernel is required for this section,
1310which can be obtained in our [Arvo kernel tutorial](@/docs/tutorials/arvo/arvo.md#the-kernel).
1411
15−### Running a move trace
12+## Running a move trace
1613
1714Ultimately, everything that happens in Arvo is reduced to Unix events, and the
1815Arvo kernel acts as a sort of traffic cop for vanes and apps to talk to one
@@ -84,7 +81,7 @@ another `move` to perform and the loop begins again. Thus this move trace does
8481not display information about what is going on inside of the vane or app such as
8582private function calls, only what the kernel itself sees.
8683
87−### Interpreting the move trace
84+## Interpreting the move trace
8885
8986In this section we will go over the move trace line-by-line, explaining how the
9087move trace is printed, what each line means (including some things not found in
@@ -93,7 +90,7 @@ first few lines that should equip you well enough to unravel the rest of the
9390move trace in as much detail as you desire.
9491
9592
96−#### The call
93+### The call
9794
9895Let's put the first part of the move trace into a diagram to make following
9996along a little easier.
@@ -310,7 +307,7 @@ Gall's spider's thread with id `~.dojo_0v6.210tt.1sme1.ev3qm.qgv2e.a754u` asks B
310307Behn `%give`s a `%doze` `card` to Unix, asking it to set a timer [for one second from
311308now]. At this point Arvo may rest.
312309
313−#### The return
310+### The return
314311
315312Now Unix sets a timer for one second, waits one second, and then informs Behn that a second has
316313passed, leading to a chain of `%give` `move`s that ultimately prints