From 70d53459bf420d502f735227c13bdd3e80f232f0 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Fri, 18 Dec 2020 04:01:22 -0500 Subject: s/command/subcommand/ (12 instances) --- manpages/taler-exchange-offline.1.rst | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) (limited to 'manpages/taler-exchange-offline.1.rst') diff --git a/manpages/taler-exchange-offline.1.rst b/manpages/taler-exchange-offline.1.rst index f92b2898..0ca0ddf3 100644 --- a/manpages/taler-exchange-offline.1.rst +++ b/manpages/taler-exchange-offline.1.rst @@ -34,14 +34,14 @@ REST APIs. The ``download`` subcommand downloads the future public keys from th running exchange. The resulting data serves as input to the ``sign`` and ``show`` subcommands. The ``upload`` subcommand uploads the signatures created with the private master key to the exchange. It handles the output of all subcommands -(except ``download``). The ``download`` and ``upload`` commands must naturally be +(except ``download``). The ``download`` and ``upload`` subcommands must naturally be run "online" and do not require access to the offline key. 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``. @@ -103,15 +103,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. @@ -119,14 +119,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. @@ -138,7 +138,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. @@ -150,7 +150,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. @@ -265,7 +265,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. @@ -360,7 +360,7 @@ Create multiple revocation messages in one pass (offline) $ taler-exchange-offline revoke-signkey $SK revoke-denomkey $DKH > mix.json The outputs ("revoke.json", "mix.json") must be uploaded using the ``upload`` -command to the exchange to actually revoke the keys. +subcommand to the exchange to actually revoke the keys. -- cgit v1.2.3