documentation style: there is no "the restricted command"

[dgit.git] / dgit-downstream-dsc.7.pod

diff --git a/dgit-downstream-dsc.7.pod b/dgit-downstream-dsc.7.pod
index fcbce05871acb33fbb4707ce30425049d3fa6d4a..91d9023c2892f447cb97eb0e8ef1a9245eacfe96 100644 (file)
--- a/dgit-downstream-dsc.7.pod
+++ b/dgit-downstream-dsc.7.pod
@@ -121,8 +121,8 @@ but in most installations this is not needed.
 If there is no or little distinction between
 (i) developers who are entitled to upload (push) and
 (ii) repository administrators,
-then a it is sufficient to provide a
-git server with a unix account for each user who will pushing,
+then it is sufficient to provide a
+git server with a unix account for each user who will be pushing,
 perhaps using ssh restricted commands.
 
 =item Debian-format archive (repository)
@@ -216,7 +216,7 @@ yet a git repository for a particular package.
 
 If you always have a git repository for every package in your archive,
 perhaps because you never use dput/dupload, and always dgit push,
-Set C<git-check> to B<true>.
+set C<git-check> to B<true>.
 
 Otherwise, set C<git-check> to a url prefix - ideally, https.
 dgit clone will try to fetch
@@ -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 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.