aboutsummaryrefslogtreecommitdiff
path: root/doc/documentation
diff options
context:
space:
mode:
authorng0 <ng0@n0.is>2018-02-03 11:28:16 +0000
committerng0 <ng0@n0.is>2018-02-03 11:28:16 +0000
commit0218f6180cea86da27b9ebd7354f57bddcfc6888 (patch)
treee0fcae442228762ea97fd8e988db55101086728a /doc/documentation
parent1c2e854307c0bfae10cf3057ffcbd18a922ccab9 (diff)
simple -> uncomplicated
Diffstat (limited to 'doc/documentation')
-rw-r--r--doc/documentation/chapters/user.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/documentation/chapters/user.texi b/doc/documentation/chapters/user.texi
index 1a30a7336d..73c66196ad 100644
--- a/doc/documentation/chapters/user.texi
+++ b/doc/documentation/chapters/user.texi
@@ -597,12 +597,12 @@ Also, the calculation is deliberately expensive, to deter people from
doing this just for fun (as the actual revocation operation is expensive
for the network, not for the peer performing the revocation).
-To avoid TL;DR ones from accidentally revocating their zones, I am not
-giving away the command, but its simple: the actual revocation is
-performed by using the @command{-p} option
-of @command{gnunet-revocation}.
-
+@c FIXME: The Manual should give away the command using an example that is
+@c very likely to never exist.
+To avoid TL;DR ones from accidentally revocating their zones, we are not
+giving away the command, but it is uncomplicated: the actual revocation is
+performed by using the @command{-p} option of @command{gnunet-revocation}.
@node What's Next?
@subsection What's Next?