path: root/dgit-maint-debrebase.7.pod
diff options
authorPaul Hardy <>2019-01-09 22:35:39 -0800
committerIan Jackson <>2019-03-01 18:06:21 +0000
commit9e94228f893936a65dea1a05758e523dc7e7d22f (patch)
treeb59901925a3843950fa2d8235ed6db6b94672c6f /dgit-maint-debrebase.7.pod
parent89ddee481cef0bbe0e8f094be134625a8dccf3d2 (diff)
documentation: typo suggestions from Paul Hardy
Signed-off-by: Paul Hardy <>
Diffstat (limited to 'dgit-maint-debrebase.7.pod')
1 files changed, 3 insertions, 3 deletions
diff --git a/dgit-maint-debrebase.7.pod b/dgit-maint-debrebase.7.pod
index 4996e6a..b91ed16 100644
--- a/dgit-maint-debrebase.7.pod
+++ b/dgit-maint-debrebase.7.pod
@@ -376,7 +376,7 @@ release:
Pass I<--stat> just to see the list of changed files, which is useful
-to determine whether there are any new or deleted files to may need
+to determine whether there are any new or deleted files that may need
accounting for in your copyright file.
If you obtained a tarball from upstream, you are ready to try a build.
@@ -451,7 +451,7 @@ In some cases where you used B<git debrebase convert-from-gbp> since
the last upload, it is not possible for dgit to make your history
fast-forwarding from the history on B<dgit-repos>. In such cases you
will have to pass I<--overwrite> to dgit. git-debrebase will normally
-tell you if this is will be needed.
+tell you if this will be needed.
Right before uploading, if you did not just already do so, you might
want to have git-debrebase(1) shuffle your branch such that the Debian
@@ -559,7 +559,7 @@ In the simplest case,
-If that fails, because your branch and the NMUers work represent
+If that fails, because your branch and the NMUers' work represent
divergent branches of development, you have a number of options. Here
we describe the two simplest.