From a67a10796e911c9111da240f90033ee5e3aba2d6 Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Date: Thu, 6 Jun 2019 10:06:30 -0400
Subject: [PATCH] about: avoid clunky "up- and downloaded" construction

This also happens to fix a bit of the text that is actually incorrect:
the policies about uploads and downloads are different, and can't be
described together.
---
 dist/templates/about/about.html.hbs | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/dist/templates/about/about.html.hbs b/dist/templates/about/about.html.hbs
index 6b287c1..6e5d998 100644
--- a/dist/templates/about/about.html.hbs
+++ b/dist/templates/about/about.html.hbs
@@ -33,13 +33,16 @@
     <p>
         Traditionally, these pieces of information have always been distributed
         together. On <span class="brand">keys.openpgp.org</span>, they are
-        treated differently:
+        treated differently.  While anyone can upload all parts of any OpenPGP key
+        to <span class="brand">keys.openpgp.org</span>, our keyserver
+        will only retain and publish certain parts under certain
+        conditions:
     </p>
 
     <p>
-        The technical data of keys can be freely up- and downloaded on
-        <span class="brand">keys.openpgp.org</span>.  It consists of technical
-        information only, which can't be used to identify its owner.
+        Any valid technical data will be stored and freely redistributed.
+        Anyone can download these parts at any time as they contain only
+        technical information which can't be used to directly identify a person.
         Good OpenPGP software can use <span class="brand">keys.openpgp.org</span>
         to keep this information up to date for any key that it knows about.
         This helps OpenPGP users maintain secure and reliable communication.