X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=dgit-sponsorship.7.pod;h=2e6f82d95071c74cc55033b03a73f56a15111aae;hb=ea47dd8b3dcb8528e8fdfa7bd86bb890d2ca79d7;hp=3fbdac8651f7e15db0499740d3db1aad0aadeeed;hpb=63a98f62bafff974fcc080d8a4db8d34fafd0a8b;p=dgit.git

diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod
index 3fbdac86..2e6f82d9 100644
--- a/dgit-sponsorship.7.pod
+++ b/dgit-sponsorship.7.pod
@@ -9,7 +9,7 @@ and
 a sponsoring DD (or DM)
 can collaborate and publish using git.
 
-The sponsor must to be intending to use dgit for the upload.
+The sponsor must be intending to use dgit for the upload.
 (If the sponsor does not use dgit,
 it is not possible to properly publish
 a sponsee's git branch.)
@@ -315,7 +315,7 @@ to dgit push for every successive upload.
 This disables a safety catch which would normally spot
 situations where changes are accidentally lost.
 When your sponsee is sending you source packages -
-perhaps multiple source pacakges with the same version number -
+perhaps multiple source packages with the same version number -
 these safety catches are inevitably ineffective.
 
 =head1 SEE ALSO