summaryrefslogtreecommitdiffhomepage
path: root/debug-me.cabal
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 /debug-me.cabal
parent87e0e9cf517d2ca2f9dc1011d1924fb068db78e4 (diff)
downloaddebug-me-e8e389a4bce4f9783ec5a0b57f89843ac00342da.tar.gz
capitalization
Diffstat (limited to 'debug-me.cabal')
-rw-r--r--debug-me.cabal4
1 files changed, 2 insertions, 2 deletions
diff --git a/debug-me.cabal b/debug-me.cabal
index ffeefed..d3043a5 100644
--- a/debug-me.cabal
+++ b/debug-me.cabal
@@ -17,13 +17,13 @@ Description:
so they can immediately see and interact with the problem. Making your
problem their problem gets it fixed fast.
.
- A debug-me session is logged and signed with the developer's Gnupg
+ A debug-me session is logged and signed with the developer's GnuPG
key, producing a chain of evidence of what they saw and what they did.
So the developer's good reputation is leveraged to make debug-me secure.
.
When you start debug-me without any options, it will connect to a debug-me
server, and print out an url that you can give to the developer to get
- them connected to you. Then debug-me will show you their Gnupg key and who
+ them connected to you. Then debug-me will show you their GnuPG key and who
has signed it. If the developer has a good reputation, you can proceed
to let them type into your console in a debug-me session. Once the
session is done, the debug-me server will email you the signed