path: root/dgit-user.7.pod
diff options
authorIan Jackson <>2017-01-04 01:27:41 +0000
committerIan Jackson <>2017-01-12 01:23:07 +0000
commite2c606b8a204d68f96047ebe3b21e7274839ea66 (patch)
tree771a372dc235eb0c92290f8599c0d5d99437b6f1 /dgit-user.7.pod
parent791b5fe6f1ae18b11277f8bb5bc83d8029c57503 (diff)
dgit-user(7): Fix some more typos
Signed-off-by: Ian Jackson <>
Diffstat (limited to 'dgit-user.7.pod')
1 files changed, 3 insertions, 3 deletions
diff --git a/dgit-user.7.pod b/dgit-user.7.pod
index 08647c6..d7b6109 100644
--- a/dgit-user.7.pod
+++ b/dgit-user.7.pod
@@ -197,7 +197,7 @@ or upstream's git history.
But for many packages the real git history
does not exist,
or has not been published in a dgitish form.
-So yuu may find that the history is a rather short
+So you may find that the history is a rather short
history invented by dgit.
dgit histories often contain automatically-generated commits,
@@ -349,7 +349,7 @@ The proper solution
is to build the package for all the architectures you
have enabled.
You'll need a chroot for each of the secondary architectures.
-This iw somewhat tiresome,
+This is somewhat tiresome,
even though Debian has excellent tools for managing chroots.
C<sbuild-createchroot> from the sbuild package is a
good starting point.
@@ -362,7 +362,7 @@ If neither of those are an option,
your desperate last resort is to try
using the same version number
as the official package for your own package.
-(The verseion is controlled by C<debian/changelog> - see above).
+(The version is controlled by C<debian/changelog> - see above).
This is not ideal because it makes it hard to tell what is installed,
and because it will mislead and confuse apt.