X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit.7;h=a9886563eae90110f0f560bb2f73ed17fed3adf7;hp=b3a112c42c9e96867c7d7093e26295642e5608cc;hb=31995d0c8b6212275829a7e432821d5d94633ef5;hpb=4e7ab600625c292cf5d5c29682961896ee9f3021

diff --git a/dgit.7 b/dgit.7
index b3a112c4..a9886563 100644
--- a/dgit.7
+++ b/dgit.7
@@ -31,10 +31,10 @@ However, it is perfectly fine to have other branches in dgit-repos;
 normally the dgit-repos repo for the package will be accessible via
 the remote name `origin'.
 
-dgit push will also (by default) make signed tags called
+dgit push will also make signed tags called
 .BI debian/ version
-and push them to dgit-repos, but nothing depends on these tags
-existing.
+(a la DEP-14) and push them to dgit-repos.  These are used at the
+server to authenticate pushes.
 
 dgit push can operate on any commit which is a descendant of the
 current dgit/suite tip in dgit-repos.
@@ -64,7 +64,7 @@ You need to retain these tarballs in the parent directory for dgit
 build and dgit push.
 
 dgit repositories could be cloned with standard (git) methods. The
-only exception is that for sourcefull builds / uploads the orig
+only exception is that for sourceful builds / uploads the orig
 tarball(s) need to be present in the parent directory.
 
 To a user looking at the archive, changes pushed using dgit look like