summaryrefslogtreecommitdiff
path: root/doc/design/assistant/blog/day_83__3-way.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/design/assistant/blog/day_83__3-way.mdwn')
-rw-r--r--doc/design/assistant/blog/day_83__3-way.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/design/assistant/blog/day_83__3-way.mdwn b/doc/design/assistant/blog/day_83__3-way.mdwn
index d58ec9fe5..9411c4c1c 100644
--- a/doc/design/assistant/blog/day_83__3-way.mdwn
+++ b/doc/design/assistant/blog/day_83__3-way.mdwn
@@ -68,6 +68,6 @@ still possible with other network topologies (ie, if D is connected to both
B and C, there would be an upload loop 'B -> C -> D -> B`). So unless I can
find a better event to hook into, this idea is doomed.
-I do have another idea to fix the same problem. C could certianly remember
+I do have another idea to fix the same problem. C could certainly remember
that it saw a file and didn't know where to get the content from, and then
when it receives a git push of a git-annex branch, try again.