X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=best-pkging-practices.dbk;h=bd2270b6aa106d6c71f2f100a32dd500c60d1306;hb=f7c28267a332a4043fa6f1e8149b4fd98ec26da9;hp=8b03c4771eeabd5950f8cb180f4ce88d0001df11;hpb=7b6908b7523a7a9d36ee0ee7eb9e8a2d27b8f83a;p=developers-reference.git

diff --git a/best-pkging-practices.dbk b/best-pkging-practices.dbk
index 8b03c47..bd2270b 100644
--- a/best-pkging-practices.dbk
+++ b/best-pkging-practices.dbk
@@ -1912,13 +1912,13 @@ coherent set of packages that can evolve over time. It achieves this by
 depending on all the packages of the set. Thanks to the power of APT, the
 meta-package maintainer can adjust the dependencies and the user's system
 will automatically get the supplementary packages. The dropped packages
-that were automaticaly installed will be also be marked as removal
+that were automatically installed will be also be marked as removal
 candidates (and are even automatically removed by <command>aptitude</command>).
 <systemitem role="package">gnome</systemitem> and
 <systemitem role="package">linux-image-amd64</systemitem> are two examples
 of meta-packages (built by the source packages
 <systemitem role="package">meta-gnome2</systemitem> and
-<systemitem role="package">linux-latest</systemitem>)
+<systemitem role="package">linux-latest</systemitem>).
 </para>
 <para>
 The long description of the meta-package must clearly document its purpose