X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=best-pkging-practices.dbk;h=2316f195ce1a4af156f43836091c6bd32d1294a1;hb=ee1ac48aaa5c3c252a4b7733df537a67d19a827d;hp=575a80fc3f9e7d66a799e7d210a53de0b6985671;hpb=44eb45b95a52172ea6f9a25ae62e9793daa42eb4;p=developers-reference.git
diff --git a/best-pkging-practices.dbk b/best-pkging-practices.dbk
index 575a80f..2316f19 100644
--- a/best-pkging-practices.dbk
+++ b/best-pkging-practices.dbk
@@ -1630,9 +1630,9 @@ incrementing the version number, so there can be no guarantee that a pristine
tarball is identical to what upstream currently
distributing at any point in time. All that can be expected is that it is
identical to something that upstream once did distribute.
-If a difference arises later (say, if upstream notices that he wasn't using
-maximal compression in his original distribution and then
-re-gzips it), that's just too bad. Since there is no good
+If a difference arises later (say, if upstream notice that they weren't using
+maximal compression in their original distribution and then
+re-gzip it), that's just too bad. Since there is no good
way to upload a new .orig.tar.{gz,bz2,xz} for the same version, there is not even any
point in treating this situation as a bug. This makes it
possible to use checksums to easily verify that all changes between Debian's
@@ -1688,7 +1688,7 @@ that you must remove before uploading.
In these cases the developer must construct a suitable .orig.tar.{gz,bz2,xz}
-file himself. We refer to such a tarball as a repackaged upstream
+file themselves. We refer to such a tarball as a repackaged upstream
source. Note that a repackaged upstream source is different from a
Debian-native package. A repackaged source still comes with Debian-specific
changes in a separate .diff.gz or .debian.tar.{gz,bz2,xz}
@@ -1856,7 +1856,7 @@ of meta-packages (built by the source packages
The long description of the meta-package must clearly document its purpose
-so that the user knows what he will lose if he removes the package. Being
+so that the user knows what they will lose if they remove the package. Being
explicit about the consequences is recommended. This is particularly
important for meta-packages which are installed during initial
installation and that have not been explicitly installed by the user.