diff options
| author | Guilhem Moulin <guilhem@fripost.org> | 2020-01-29 12:21:59 +0100 |
|---|---|---|
| committer | Guilhem Moulin <guilhem@fripost.org> | 2020-01-29 12:21:59 +0100 |
| commit | 98a580c5a6f9dd2f2b2ca103a9c6df9f0f77b0d1 (patch) | |
| tree | 730edd0c0a57e0ca305e58c8452201f705a9010c /doc/getting-started.md | |
| parent | 97b077be640071363918a0a27b0acfddd114ff1a (diff) | |
| parent | 4bab81b1ccde90990620c157c274e2b2c7831b9f (diff) | |
Merge tag 'upstream/0.5' into debian
Upstream version 0.5
Diffstat (limited to 'doc/getting-started.md')
| -rw-r--r-- | doc/getting-started.md | 2 |
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. |