summaryrefslogtreecommitdiff
path: root/pages/services/email/en.haml
diff options
context:
space:
mode:
authorelijah <elijah@riseup.net>2013-04-04 00:40:55 -0700
committerelijah <elijah@riseup.net>2013-04-04 00:40:55 -0700
commit0c8a49ce32bfd2b1ebd0496fac1e9cfeb7cfc7de (patch)
tree1fc56d2d28daa3f679d41a01196db7d61143e2f4 /pages/services/email/en.haml
parent19362e0cc60e8b5ba2b592836a1459271e89e1e6 (diff)
s/nickid/nicknym
Diffstat (limited to 'pages/services/email/en.haml')
-rw-r--r--pages/services/email/en.haml2
1 files changed, 1 insertions, 1 deletions
diff --git a/pages/services/email/en.haml b/pages/services/email/en.haml
index ff2aa9b..4c79e8e 100644
--- a/pages/services/email/en.haml
+++ b/pages/services/email/en.haml
@@ -12,7 +12,7 @@
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.
- *Opportunistic Content Encryption:* Whenever possible, all outgoing email will be encrypted to all the recipients. Encryption keys will be automatically discovered and verified using the #{link 'LEAP Identity' => 'nickid'} service.
+ *Opportunistic Content Encryption:* Whenever possible, all outgoing email will be encrypted to all the recipients. Encryption keys will be automatically discovered and verified using the #{link 'LEAP Identity' => 'nicknym'} service.
*Client-encrypted Mail Storage:* Incoming clear-text mail will get encrypted to the user's public key, stored in their cloud storage space, and sync'ed locally for direct access by a mail client.