1 files changed, 9 insertions, 9 deletions
@@ -130,7 +130,7 @@ If you already have the suite branch,
and want to merge your branch with updates from the archive,
use dgit pull.
-dgit checkout will normally need to aceess the archive server,
+dgit checkout will normally need to access the archive server,
to canonicalise the provided suite name.
The exception is if you specify the canonical name,
and the branch (or tracking branch) already exists.
@@ -146,7 +146,7 @@ commit.
Tagging, signing and actually uploading should be left to dgit push.
-dgit's build operations access the the network,
+dgit's build operations access the network,
to get the -v option right.
See -v, below.
@@ -424,7 +424,7 @@ If this is a problem
-There is only only sub-option:
+There is only one sub-option:
causes dgit to insist that the signature on the .dsc is valid
@@ -436,7 +436,7 @@ If
is prefixed with
-then if it already exists, it will be simply ovewritten,
+then if it already exists, it will be simply overwritten,
no matter its existing contents.
@@ -469,7 +469,7 @@ It may not be useable in a browser.
.BI "dgit print-dpkg-source-ignores"
Prints the -i and -I arguments which must be passed to dpkg-souce
-to cause it to exclude exactly the .git diredcory
+to cause it to exclude exactly the .git directory
and nothing else.
The separate arguments are unquoted, separated by spaces,
and do not contain spaces.
@@ -708,7 +708,7 @@ And it is only effective with
If ref does not start with refs/
-it is taken to to be a branch -
+it is taken to be a branch -
i.e. refs/heads/ is prepended.
@@ -898,7 +898,7 @@ default, in
When doing a build, delete any changes files matching
.IB package _ version _*.changes
before starting. This ensures that
-dgit push (and dgit sbuild) will be able to unambigously
+dgit push (and dgit sbuild) will be able to unambiguously
identify the relevant changes files from the most recent build, even
if there have been previous builds with different tools or options.
The default is not to remove, but
@@ -910,7 +910,7 @@ Note that \fBdgit push-source\fR will always find the right .changes,
regardless of this option.
.BI --build-products-dir= directory
-Specifies where to find and create tarballs, binry packages,
+Specifies where to find and create tarballs, binary packages,
source packages, .changes files, and so on.
By default, dgit uses the parent directory
@@ -1366,7 +1366,7 @@ Default git user.email and user.name for new trees. See
.BR gpg ", " dpkg- "..., " debsign ", " git ", " curl ", " dput ", " LWP::UserAgent
and other subprograms and modules used by dgit are affected by various
-environment variables. Consult the documentaton for those programs
+environment variables. Consult the documentation for those programs
There should be