updated email page

1 files changed, 25 insertions, 2 deletions

diff --git a/pages/services/email/en.md b/pages/services/email/en.md
index 95353b7..0eeff99 100644
--- a/pages/services/email/en.md
+++ b/pages/services/email/en.md
@@ -11,7 +11,7 @@ For example, there is no standard for ensuring secure relay between mail provide
 
 The LEAP approach to email is to support communication with the legacy email infrastructure while also adding optional layers to the protocol that bring email more in line with modern security practices. This strategy allows for a gradual transition from existing email to secure email. In the short term, there are immediate benefits to a user's security when they adopt LEAP email. In the long term, as more service providers adopt the LEAP platform, email among these service providers gains even more protection.
 
-Above all else, our focus is on creating a user experience that is as easy and troublefree as possible while still ensuring a very high level of security.
+Above all else, our focus is on creating a user experience that is as easy and trouble-free as possible while still ensuring a very high level of security.
 
 ## How it works
 
@@ -59,6 +59,7 @@ In the long term, we plan to adopt one of several different schemes for [securel
 
 ## Limitations
 
+* Missing features: the initial release will not support email aliases, email forwarding, or multiple accounts simultaneously.
 * You cannot use LEAP email from a web browser. It requires the Bitmask application to run.
 * The Bitmask application currently requires a compatible provider. We have plans in the future to semi-support commercial providers like gmail. This would provide the user with much less protection than when they use a LEAP provider, but will still greatly enhance their email security.
 * Because all data is synced, if a user has one of their devices compromised, then the attacker has access to all their data. This is obvious, but worth mentioning.
@@ -66,4 +67,26 @@ In the long term, we plan to adopt one of several different schemes for [securel
 * We do not plan to support key revocation. Instead, we plan to migrate to shorter and shorter lived keys, as practical.
 * With the current implementation, a compromised or nefarious service provider can still gather incoming messages that are not encrypted and meta-data routing information. As more users and providers adopt secure email, many of these problems will go away.
 
-For more details, please see [known limitations](limitations).
\ No newline at end of file
+For more details, please see [known limitations](limitations).
+
+## Related projects
+
+There are numerous other projects working on the next generation of secure email. In our view, it is not possible to do secure email alone, it requires new protocols for handing key validation, secure transport, and meta-data protection. We will continue our efforts to reach out to these groups to explore areas of cooperation.
+
+Free software projects
+
+* [mailpile.is](http://mailpile.is/) - Python email client with a web interface, optimized searching, and support for OpenPGP.
+* [mailiverse.com](https://mailiverse.com) - HTML5 app. Sparse on details.
+
+Mixed proprietary and free software projects
+
+* [mega.co.nz](https://mega.co.nz/) - Mega has announced plans for web-based encrypted email, but no details yet. In-browser javascript client will reportedly be open source, backend not.
+
+Proprietary projects
+
+* [parley.co](http://parley.co) - Proprietary OpenPGP client and service.
+* [startmail.com](https://startmail.com/) - No details yet.
+
+Initiatives
+
+* Ubiquitous Encrypted Email - A private, invite-only mailing list to discuss new ways to make encrypted email commonplace.
\ No newline at end of file