aboutsummaryrefslogtreecommitdiffstats
path: root/doc/getting-started.md
diff options
context:
space:
mode:
authorGuilhem Moulin <guilhem@fripost.org>2019-12-14 21:33:41 +0100
committerGuilhem Moulin <guilhem@fripost.org>2019-12-14 21:33:46 +0100
commit185e9458dc836f3ef4052c9dcb5a76c07a212589 (patch)
tree364b7bfeb4f730e045603f9a654a7b74c09933de /doc/getting-started.md
parent6982b9c6a01b9c121f7510ec9439d4d75cf0b96f (diff)
typofix
Closes: #946727.
Diffstat (limited to 'doc/getting-started.md')
-rw-r--r--doc/getting-started.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/getting-started.md b/doc/getting-started.md
index da8f116..c497ec6 100644
--- a/doc/getting-started.md
+++ b/doc/getting-started.md
@@ -24,7 +24,7 @@ While most bidirectional synchronisation software (such as [OfflineIMAP])
are able to handle a mail storage in Maildir format, *InterIMAP is
not*. Instead, InterIMAP needs an [IMAP4rev1] server on *both* peers
to synchronize. This may sound like a severe limitation at first, but by
-seeing both local and remote mail storage though the same “IMAP lens”,
+seeing both local and remote mail storage through the same “IMAP lens”,
InterIMAP is able to take advantage of the abstraction layer and
perform significant optimizations, yielding [much faster](benchmark.html)
synchronization.