@@ -65,7 +65,7 @@ drifts out of sync with this doc).
6565We'll go over the two parts to an API connector (one-time reading vs listening
6666for events) separately.
6767
68−# Reading
68+## Reading
6969
7070A connector exposes a tree of data. Every read request has a
7171`care`, which is generally either `%x` or `%y. `%x` is a request
@@ -156,7 +156,12 @@ control. There are four functions we need to define:
156156That's really all there is to the reading portion of API
157157connectors.
158158
159−# Listening
159+One of the most accessbile ways to jump into Arvo programming is
160+to just add more places to an existing API connector. It's
161+useful, small in scope, and comes in bite-sized chunks since most
162+places are less than ten lines of code.
163+
164+## Listening
160165
161166Listening for events is fairly service-specific. In some
162167services, we poll for changes. For an example of that, check out
@@ -200,6 +205,12 @@ standardized, so even if your chosen service is powered by
200205webhooks, your listening code might look rather different. The
201206point is to expose the correct interface.
202207
208+
209+## Github API Connector Code
210+
211+In case the code in `/=home=/app/gh/hoon` drifts out of sync with
212+this doc:
213+
203214```
204215:: This is a connector for the Github API v3.
205216::