on master help sign in
gall-guide: lesson 7 - clarify part two forthcoming
206bef9Tinnus Napbus
content/docs/userspace/gall-guide/7-sur-and-marks.md+3−3
@@ -285,9 +285,9 @@ will be interpreted as `/` if there's not already a `/mar/todo-action.hoon`.
285This simple mark file isn't all that useful. Typically, you'd add `json` arms to
285This simple mark file isn't all that useful. Typically, you'd add `json` arms to
286`grow` and `grab`, which allow your data to be converted to and from JSON, and
286`grow` and `grab`, which allow your data to be converted to and from JSON, and
287therefore allow your agent to communicate with a web front-end. Front-ends,
287therefore allow your agent to communicate with a web front-end. Front-ends,
288−JSON, and Eyre's APIs which facilitate such communications will be covered in
288+JSON, and Eyre's APIs which facilitate such communications will be covered in a
289−part two of the Gall guide. For now though, it's still useful to use marks and
289+forthcoming part two of the Gall guide. For now though, it's still useful to use
290−understand how they work.
290+marks and understand how they work.
291
291
292One further note on marks - while data from remote ships must have a matching
292One further note on marks - while data from remote ships must have a matching
293mark file in `/mar`, it's possible to exchange data between local agents with
293mark file in `/mar`, it's possible to exchange data between local agents with