X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit.7;h=cbf91b90e8d15d70f57b0108e2c27dba08ba6095;hp=f594093b36e041ed4bfbe93cf5d5b1a4d55c6b3b;hb=ef5cfec1b71cc39d1077d8822e739e4cf1a8a36d;hpb=e917ad10a9459a78561be1576801fea4cb0ce082

diff --git a/dgit.7 b/dgit.7
index f594093b..cbf91b90 100644
--- a/dgit.7
+++ b/dgit.7
@@ -32,8 +32,9 @@ normally the dgit-repos repo for the package will be accessible via
 the remote name `origin'.
 
 dgit push will also make signed tags called
-.BI debian/ version
-(a la DEP-14) and push them to dgit-repos.  These are used at the
+.BI archive/debian/ version
+(with version encoded 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
@@ -48,7 +49,7 @@ branch) whose tree is identical to the unpacked source upload.
 Uploads not made by dgit are represented in git by commits which are
 synthesised by dgit.  The tree of each such commit corresponds to the
 unpacked source; there is an origin commit with the contents, and a
-psuedo-merge from last known upload - that is, from the contents of
+pseudo-merge from last known upload - that is, from the contents of
 the dgit/suite branch.
 
 dgit expects repos that it works with to have a