@@ -114,7 +114,7 @@ The `cage` in the `riot` of the `%writ` contains the file's data due to our use
115Here's a breakdown of the `task` we sent:
115Here's a breakdown of the `task` we sent:
117−
117+
@@ -150,7 +150,7 @@ You can see the `riot` is just `~` due to the file being deleted.
151Here's a breakdown of the task we sent:
151Here's a breakdown of the task we sent:
153−
153+
@@ -209,7 +209,7 @@ As you can see, a relevant change to any of the subscribed files will trigger a
210Here's a breakdown of the `task` we sent:
210Here's a breakdown of the `task` we sent:
212−
212+
@@ -303,7 +303,7 @@ Run `:spider|kill` to stop the thread.
304Here's a breakdown of the `task` we sent:
304Here's a breakdown of the `task` we sent:
306−
306+
308## Cancel Subscription
308## Cancel Subscription
@@ -347,7 +347,7 @@ Run `:spider|kill` to stop the thread.
348Here's a breakdown of the `task` we sent:
348Here's a breakdown of the `task` we sent:
350−
350+
352# Write and Modify
352# Write and Modify
@@ -370,7 +370,7 @@ We've created the `cage` of the content like `[%txt !>(~['foo'])]`, if you want
371Here's a breakdown of the `task` we sent:
371Here's a breakdown of the `task` we sent:
373−
373+
@@ -387,7 +387,7 @@ If you have a look in the home of your pier you'll see the `foo.txt` file is now
388Here's a breakdown of the `task` we sent:
388Here's a breakdown of the `task` we sent:
390−
390+
@@ -693,7 +693,7 @@ As you can see it's back to the default inherited from `/`.
694Here's a breakdown of a `%perm` task:
694Here's a breakdown of a `%perm` task:
696−
696+