|author||Ian Jackson <firstname.lastname@example.org>||2019-01-11 21:37:22 +0000|
|committer||Ian Jackson <email@example.com>||2019-03-01 18:06:21 +0000|
documentation style: there is no "the restricted command"
I see "ssh restricted command" as a feature. There is no command provided; alternatively one could argue that the user is to provide a script, which they will configure as the restricted command, in which case "to make writing the ssh restricted command script|implementation" or something, but that seems wordy. Signed-off-by: Ian Jackson <firstname.lastname@example.org>
1 files changed, 1 insertions, 1 deletions
diff --git a/dgit-downstream-dsc.7.pod b/dgit-downstream-dsc.7.pod
index 73c10cf..91d9023 100644
@@ -312,7 +312,7 @@ Either don't do that, or set up B<dgit-repos-server>.
When a user who can push runs dgit,
dgit uses ssh to access the git server.
-To make the ssh restricted command easier,
+To make use of ssh restricted command easier,
and for the benefit of dgit-repos-server,
dgit's ssh commands
each start with a parseable commentish rune.