diff options
author | Richard Hartmann <richih.mailinglist@gmail.com> | 2012-07-08 20:53:50 +0200 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2012-07-08 13:04:35 -0600 |
commit | 619297e1a7ba89f50fa5be9d7dfdfe5a9510129a (patch) | |
tree | 425a9931a9caa211ae24f9d8c05976757c2203a6 /doc/design/assistant/blog/day_19__random_improvements.mdwn | |
parent | b64a489a07f5e5be5b722ec3b942f505756ce853 (diff) |
Fix typos on blog
Diffstat (limited to 'doc/design/assistant/blog/day_19__random_improvements.mdwn')
-rw-r--r-- | doc/design/assistant/blog/day_19__random_improvements.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/design/assistant/blog/day_19__random_improvements.mdwn b/doc/design/assistant/blog/day_19__random_improvements.mdwn index 93c1296ba..acb30bf93 100644 --- a/doc/design/assistant/blog/day_19__random_improvements.mdwn +++ b/doc/design/assistant/blog/day_19__random_improvements.mdwn @@ -35,7 +35,7 @@ more threads: 1. Uploads new data to every configured remote. Triggered by the watcher thread when it adds content. Easy; just use a `TSet` of Keys to send. -2. Downloads new data from the cheapest remote that has it. COuld be +2. Downloads new data from the cheapest remote that has it. Could be triggered by the merger thread, after it merges in a git sync. Rather hard; how does it work out what new keys are in the tree without scanning it all? Scan |