summaryrefslogtreecommitdiff
path: root/pages/services/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/en.haml
parent19362e0cc60e8b5ba2b592836a1459271e89e1e6 (diff)
s/nickid/nicknym
Diffstat (limited to 'pages/services/en.haml')
-rw-r--r--pages/services/en.haml2
1 files changed, 1 insertions, 1 deletions
diff --git a/pages/services/en.haml b/pages/services/en.haml
index 56787f3..b7ad664 100644
--- a/pages/services/en.haml
+++ b/pages/services/en.haml
@@ -1,6 +1,6 @@
%h1.first User Services
-%p LEAP's multi-year plan to secure everyday communication breaks down into discrete services, to be rolled out one at a time. When we introduce a new service, integrated support will be added to both the user-facing #{link 'client'} and the server-side #{link 'platform'}. All communication content will be client-side encrypted, and as much of the metadata as possible. Most importantly, all LEAP services will be based on our plan for #{link 'federated secure identity' => 'nickid'} and #{link 'unmappable routing' => 'routing'}.
+%p LEAP's multi-year plan to secure everyday communication breaks down into discrete services, to be rolled out one at a time. When we introduce a new service, integrated support will be added to both the user-facing #{link 'client'} and the server-side #{link 'platform'}. All communication content will be client-side encrypted, and as much of the metadata as possible. Most importantly, all LEAP services will be based on our plan for #{link 'federated secure identity' => 'nicknym'} and #{link 'unmappable routing' => 'routing'}.
%h2 Roadmap