From c6cab9b24913e28735a472589c112e9bea7d98db Mon Sep 17 00:00:00 2001
From: taffit <taffit@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Sat, 10 Sep 2011 21:55:25 +0000
Subject: [PATCH] Fix typos spotted while updating the French translation

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@8923 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
 best-pkging-practices.dbk |  4 ++--
 pkgs.dbk                  | 12 ++++++------
 2 files changed, 8 insertions(+), 8 deletions(-)

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
diff --git a/pkgs.dbk b/pkgs.dbk
index 6846e24..4eab6a4 100644
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -841,9 +841,9 @@ fixing them themselves, sending security advisories, and maintaining
 <para>
 When you become aware of a security-related bug in a Debian package, whether or
 not you are the maintainer, collect pertinent information about the problem,
-and promptly contact the security team, preferedly by filing a ticket in
+and promptly contact the security team, preferably by filing a ticket in
 their Request Tracker.
-See <ulink url="http://wiki.debian.org/rt.debian.org#SecurityTeam"></ulink>.
+See <ulink url="http://wiki.debian.org/rt.debian.org#Security_Team"></ulink>.
 Alternatively you may email &email-security-team;.
 <emphasis role="strong">DO NOT UPLOAD</emphasis> any packages for
 <literal>stable</literal> without contacting the team.  Useful information
@@ -1246,7 +1246,7 @@ chapter gives guidelines on what to do in these cases.
 <title>Moving packages</title>
 <para>
 Sometimes a package will change its section.  For instance, a package from the
-`non-free' section might be GPL'd in a later version, in which case the package
+<literal>non-free</literal> section might be GPL'd in a later version, in which case the package
 should be moved to `main' or `contrib'.<footnote><para> See the <ulink
 url="&url-debian-policy;">Debian Policy Manual</ulink> for
 guidelines on what section a package belongs in.  </para> </footnote>
@@ -1874,7 +1874,7 @@ role="package">ftp.debian.org</systemitem>.
 <section id="non-free-buildd">
 <title>Marking non-free packages as auto-buildable</title>
 <para>
-By default packages from non-free are not built by the autobuilder
+By default packages from the <literal>non-free</literal> section are not built by the autobuilder
 network (mostly because the license of the packages could disapprove).
 To enable a package to be build you need to perform the following
 steps:
@@ -1883,13 +1883,13 @@ steps:
 <listitem>
 <para>
 Check whether it is legally allowed and technically possible
-to auto-build the package ;
+to auto-build the package;
 </para>
 </listitem>
 <listitem>
 <para>
 Add <literal>XS-Autobuild: yes</literal> into the header part
-of <filename>debian/control</filename> ;
+of <filename>debian/control</filename>;
 </para>
 </listitem>
 <listitem>
-- 
2.30.2