@@ -50,7 +50,7 @@ Let's examine a sample tile that has different Hoon code from the default, to ex
5050
5151In your pier, replace the code in `/app/testing.hoon` with the Hoon code below.
5252
53−```
53+``` hoon
5454/+ *server
5555/= tile-js
5656 /^ octs
@@ -157,7 +157,7 @@ In your pier, replace the code in `/app/testing.hoon` with the Hoon code below.
157157
158158Now, replace the code below is the contents of `/app/testing/js/tile.js` with the code below. Once you've replaced the code in both files, run `|commit %home` in the Dojo.
159159
160−```
160+``` javascript
161161import React, { Component } from 'react';
162162import classnames from 'classnames';
163163import _ from 'lodash';
@@ -215,7 +215,7 @@ The two arms that are the most important for our application are `++poke-json` w
215215
216216Now that we've glanced at the default components of the program, lets take a close look at the interesting parts of the code.
217217
218−```
218+``` hoon
219219++ poke-json
220220 |= jon=json
221221 ^- (quip move _+>.$)
@@ -248,7 +248,7 @@ There are several uses of the `~&` rune. These are simply debugging printfs that
248248
249249Finally, we produce the list of `move`s and the new state that is the data. This starts with the `:_` rune, which is the inverted form of `:-`, the [cons](https://en.wikipedia.org/wiki/Cons) rune. The state of our application will not actually change, so we can just use `+>.$` the existing core.
250250
251−```
251+``` hoon
252252++ send-status-diff
253253 |= msg=tape
254254 %- send-tile-diff
@@ -263,7 +263,7 @@ We weld the result of this gate with one more `move` we've built here: the list
263263
264264When we get a response from `%helm` to our `poke`, we'll receive a `coup`, which is the `move` always sent in response to a `poke`. Specifically, we'll get a `coup` for `helm-hi`, which is why we want an arm named `coup-helm-hi` to handle that.
265265
266−```
266+``` hoon
267267++ coup-helm-hi
268268 |= [pax=path cop=(unit tang)]
269269 ~& ["Coup recieved" pax]