summaryrefslogtreecommitdiff
path: root/manpages
diff options
context:
space:
mode:
Diffstat (limited to 'manpages')
-rw-r--r--manpages/taler-auditor-offline.1.rst26
1 files changed, 13 insertions, 13 deletions
diff --git a/manpages/taler-auditor-offline.1.rst b/manpages/taler-auditor-offline.1.rst
index 92485e49..e8a9a41d 100644
--- a/manpages/taler-auditor-offline.1.rst
+++ b/manpages/taler-auditor-offline.1.rst
@@ -37,14 +37,14 @@ The resulting data serves as input to the ``sign`` and ``show`` subcommands.
The ``upload`` subcommand uploads the signatures created with the private key to
the exchange. It handles the output of all subcommands (except ``download``).
-The ``download`` and ``upload`` commands must naturally be run "online" and do not
+The ``download`` and ``upload`` subcommands must naturally be run "online" and do not
require access to the auditor's private key, which should be kept offline.
All other subcommands are intended to be run "offline". However, especially
-when testing, it is of course possible to run the commands online as well.
+when testing, it is of course possible to run the subcommands online as well.
Generally, subcommands read inputs (beyond command-line arguments)
from ``stdin``. However, they may also consume outputs of previous
-subcommands. The outputs of multiple commands is automatically combined,
+subcommands. The outputs of multiple subcommands is automatically combined,
and if not consumed the final output is printed to ``stdout``.
@@ -106,15 +106,15 @@ Subcommands
download
--------
-This command must be run online. It downloads future signing and denomination
+This subcommand must be run online. It downloads future signing and denomination
keys with the associated meta data from the exchange and outputs the resulting
-JSON (for consumption by subsequent commands, or to stdout).
+JSON (for consumption by subsequent subcommands, or to stdout).
show
----
-This command outputs information about future signing and denomination keys for
+This subcommand outputs information about future signing and denomination keys for
manual checking against the business-approved fee structure, lifetimes and
other parameters.
@@ -122,14 +122,14 @@ It consumes the output of the ``download`` subcommand, either from ``stdin`` or
directly.
Its output always goes to ``stdout`` for human consumption (not in JSON). It
-is usually a bad idea (but possible) to combine ``show`` with other commands,
+is usually a bad idea (but possible) to combine ``show`` with other subcommands,
except maybe for testing.
sign
----
-This command signs information about future signing and denomination keys.
+This subcommand signs information about future signing and denomination keys.
It consumes the output of the ``download`` subcommand, either from ``stdin`` or
directly.
@@ -141,7 +141,7 @@ present in the input, in a format suitable for the ``upload`` subcommand.
revoke-denomination
-------------------
-This command signs a revocation message for a denomination key.
+This subcommand signs a revocation message for a denomination key.
The hash of the denomination public key must be given in the usual
base32-encoding as the first and only argument to the subcommand.
@@ -153,7 +153,7 @@ in a format suitable for the ``upload`` subcommand.
revoke-signkey
--------------
-This command signs a revocation message for an exchange online signing key.
+This subcommand signs a revocation message for an exchange online signing key.
The online signing public key must be given in the usual
base32-encoding as the first and only argument to the subcommand.
@@ -268,7 +268,7 @@ It outputs the signature affirming the wire fees, in a format suitable for the
upload
------
-This subcommand uploads outputs from other commands (except ``download`` and ``show``)
+This subcommand uploads outputs from other subcommands (except ``download`` and ``show``)
to the exchange. Note that it is possible that some uploads succeed, while others
fail, as the operation is not atomic.
@@ -320,9 +320,9 @@ Security considerations
=======================
The **taler-auditor-offline** tool assumes that it is run on a high-security
-system, especially for the ``sign`` command.
+system, especially for the ``sign`` subcommand.
-The auditor should first use the ``show`` command on the offline system to
+The auditor should first use the ``show`` subcommand on the offline system to
check that the keys being signed are acceptable. This process requires
manual work: the auditor should check with the exchange operator that
the keys (and meta data) matches that previously seen by the