summaryrefslogtreecommitdiff
path: root/pages/services/en.haml
diff options
context:
space:
mode:
authorelijah <elijah@riseup.net>2013-02-18 00:34:50 -0800
committerelijah <elijah@riseup.net>2013-02-18 00:34:50 -0800
commit9c4e765c8fe972a4a9f49c3de7991b3925ddb97c (patch)
tree79b890154416ac382c27cf3b52a7640fd59a7995 /pages/services/en.haml
parentfbf8d08dcc0045ab436dbd9e82d2715e1ba902a4 (diff)
updated the nickid page
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 94f8a01..56787f3 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' => 'identity'} 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' => 'nickid'} and #{link 'unmappable routing' => 'routing'}.
%h2 Roadmap