diff --git a/content/build-on-urbit/core-academy/ca08.md b/content/build-on-urbit/core-academy/ca08.md
index fb61f265..de5b018d 100644
--- a/content/build-on-urbit/core-academy/ca08.md
+++ b/content/build-on-urbit/core-academy/ca08.md
@@ -149,7 +149,7 @@ If a remote ship sends a nack in response to a `%plea`, Ames waits until it rece
 
 Because Ames and Urbit assume several nines of uptime, sessions between ships are treated as persistent.
 
-> The basic argument for including end-to-end acks (and by extension, nacks) is that they’re necessary for everything except those things which we don’t care whether the message was received at all. Thus, for Ames to give the guarantee that “if you give me a payload I will get it to the other side exactly once” isn’t useful in itself, because no application cares about that. They either (1) don’t care whether it gets there or (2) care whether the request itself was “completed”, in an application-defined sense. ([Phillip Monk, `~wicdev-wisryt`](https://groups.google.com/a/urbit.org/g/dev/c/y_gaSpn9mxM/m/njlRhYZHBwAJ))
+> The basic argument for including end-to-end acks (and by extension, nacks) is that they’re necessary for everything except those things which we don’t care whether the message was received at all. Thus, for Ames to give the guarantee that “if you give me a payload I will get it to the other side exactly once” isn’t useful in itself, because no application cares about that. They either (1) don’t care whether it gets there or (2) care whether the request itself was “completed”, in an application-defined sense. ([Philip Monk, `~wicdev-wisryt`](https://groups.google.com/a/urbit.org/g/dev/c/y_gaSpn9mxM/m/njlRhYZHBwAJ))
 
 Keep in mind Postel’s law, also known as the robustness principle: “Be conservative in what you send, and liberal in what you accept.”