summaryrefslogtreecommitdiffhomepage
path: root/doc/evidence.mdwn
diff options
context:
space:
mode:
authorJoey Hess <joeyh@joeyh.name>2017-05-02 18:07:27 -0400
committerJoey Hess <joeyh@joeyh.name>2017-05-02 18:07:27 -0400
commite8e389a4bce4f9783ec5a0b57f89843ac00342da (patch)
treed6e7d69f89c539b19f88f610fad433f5bc1027d1 /doc/evidence.mdwn
parent87e0e9cf517d2ca2f9dc1011d1924fb068db78e4 (diff)
downloaddebug-me-e8e389a4bce4f9783ec5a0b57f89843ac00342da.tar.gz
capitalization
Diffstat (limited to 'doc/evidence.mdwn')
-rw-r--r--doc/evidence.mdwn6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/evidence.mdwn b/doc/evidence.mdwn
index 1b44ee0..ae1590b 100644
--- a/doc/evidence.mdwn
+++ b/doc/evidence.mdwn
@@ -3,10 +3,10 @@ It shows what the developer who connected to the server saw, and what the
developer did.
The log file uses an Ed25519 session key that is signed by the developer's
-Gnupg key, so everything the developer did in the session is effectively
-signed by their Gnupg key. It's impossible to generate a log file that
+GnuPG key, so everything the developer did in the session is effectively
+signed by their GnuPG key. It's impossible to generate a log file that
shows a developer doing something other than what they did, unless you
-have the developer's Gnupg private key.
+have the developer's GnuPG private key.
The log file is formatted as a series of JSON objects, and includes both
messages from the user's debug-me, and from the developer's debug-me. See