summaryrefslogtreecommitdiff
path: root/app/views/pages/technology/platform
diff options
context:
space:
mode:
authorelijah <elijah@riseup.net>2012-08-26 23:35:24 -0700
committerelijah <elijah@riseup.net>2012-08-26 23:35:24 -0700
commite59409bc9a496a7e5bff7ffff3c3eba44d2f08c5 (patch)
treee8b9323571db81f73307f0794b4dde17a75cec58 /app/views/pages/technology/platform
parentcb2c6b5ec372e4aa0eee18d7259f43e2239a9244 (diff)
clean up use of h1 headings.
Diffstat (limited to 'app/views/pages/technology/platform')
-rw-r--r--app/views/pages/technology/platform/en.haml4
1 files changed, 2 insertions, 2 deletions
diff --git a/app/views/pages/technology/platform/en.haml b/app/views/pages/technology/platform/en.haml
index 871122a..44bbce9 100644
--- a/app/views/pages/technology/platform/en.haml
+++ b/app/views/pages/technology/platform/en.haml
@@ -1,10 +1,10 @@
-%h2.first git clone leap-platform
+%h1.first git clone leap-platform
%p The LEAP Provider Platform is the server-side part of LEAP that is run by service providers. It consists of a set of complementary packages and recipes to automate the maintenance of LEAP services in a hardened GNU/Linux environment. Our goal is to make it painless for service providers and ISPs to deploy a secure communications platform.
%p The LEAP Platform is essentially a git repository of puppet recipes, with a few scripts to help with bootstrapping and deployment. A service provider who wants to deploy LEAP services will clone or fork this repository, edit the main configuration file to specify which services should run on which hosts, and run scripts to deploy this configuration.
-%h2 More providers, please
+%h1 More providers, please
%p We believe that the best way to defend the right to whisper is to bring encryption technology into wider adoption. Despite growing awareness of the importance of communication security, users who attempt to adopt better practices still have few places they can turn.