Typo correction for d-i i18n and l10n Guide

[Tapio Lehtonen <tale@iki.fi>]

*** localization-config.xml-original	2005-12-31 12:45:25.025627784 +0200
--- localization-config.xml	2005-12-31 12:45:42.065123016 +0200
***************
*** 8,14 ****
  
  <para>
  <classname>localization-config</classname> is a package aimed to
! pre-configure language/country-relaed settings in various Debian
  packages, depending on the locale settings of the installed system.
  </para>
  
--- 8,14 ----
  
  <para>
  <classname>localization-config</classname> is a package aimed to
! pre-configure language/country-related settings in various Debian
  packages, depending on the locale settings of the installed system.
  </para>
  
*** gettext-tools.xml-original	2005-12-31 13:22:20.985695475 +0200
--- gettext-tools.xml	2005-12-31 13:22:44.472234929 +0200
***************
*** 53,59 ****
      <para>
        Gtranslator is roughly the equivalent of KBabel for users of the
        Gnome environment. Of course, it can be used outside the Gnome
!       environment with the same drawback than KBabel.
      </para>
      <para>
        However, it is not well suited for &d-i; translations as
--- 53,59 ----
      <para>
        Gtranslator is roughly the equivalent of KBabel for users of the
        Gnome environment. Of course, it can be used outside the Gnome
!       environment with the same drawback as KBabel.
      </para>
      <para>
        However, it is not well suited for &d-i; translations as
*** methods-advices.xml-original	2005-12-31 12:46:58.586874423 +0200
--- methods-advices.xml	2005-12-31 12:48:07.159794203 +0200
***************
*** 26,32 ****
  
  <para>
  If a translation team exists for a language, translators should
! <emphasis>work with them</emphasis>. Theu should first check the
  <email>debian-l10n-&lt;language&gt;</email> mailing list where
  &lt;language&gt; is the language name in English
  (e.g. <email>debian-l10n-polish</email>,
--- 26,32 ----
  
  <para>
  If a translation team exists for a language, translators should
! <emphasis>work with them</emphasis>. They should first check the
  <email>debian-l10n-&lt;language&gt;</email> mailing list where
  &lt;language&gt; is the language name in English
  (e.g. <email>debian-l10n-polish</email>,
***************
*** 130,136 ****
  </title>
  
  <para>
! Packages involves in the various levels of &d-i; translations are
  constantly changing, which sometimes induces string changes.
  </para>
  
--- 130,136 ----
  </title>
  
  <para>
! Packages involved in the various levels of &d-i; translations are
  constantly changing, which sometimes induces string changes.
  </para>
  
*** svn-basics.xml-original	2005-12-31 13:19:15.836976841 +0200
--- svn-basics.xml	2005-12-31 13:21:26.765684475 +0200
***************
*** 12,18 ****
  
  <para>
  Official Debian developers will probably use the same login than their
! Debian login, but will to go through the account creation process
  anyway. Non Debian developers should be aware that the login they
  will choose on &alioth; will be followed by "-guest". This has
  absolutely no meaning of any kind of <emphasis>second class
--- 12,18 ----
  
  <para>
  Official Debian developers will probably use the same login than their
! Debian login, but must go through the account creation process
  anyway. Non Debian developers should be aware that the login they
  will choose on &alioth; will be followed by "-guest". This has
  absolutely no meaning of any kind of <emphasis>second class
***************
*** 246,252 ****
  user@host:~/level1-po>
  </screen>
  <para>
! If the translation file already exists, then just update the locale copy:
  </para>
  <screen>
  user@host:~/level1-po> kbabel fr.po
--- 246,252 ----
  user@host:~/level1-po>
  </screen>
  <para>
! If the translation file already exists, then just update the local copy:
  </para>
  <screen>
  user@host:~/level1-po> kbabel fr.po
***************
*** 273,279 ****
  </screen>
  <para>
  The user will then be dropped in a file editor (either
! <command>vi</command> of any other file editor pointed by the EDITOR
  variable. The changelog message can be then filled in the
  editor. Saving it and exiting the editor will trigger the commit
  action to the <acronym>SVN</acronym> repository.
--- 273,279 ----
  </screen>
  <para>
  The user will then be dropped in a file editor (either
! <command>vi</command> or any other file editor pointed by the EDITOR
  variable. The changelog message can be then filled in the
  editor. Saving it and exiting the editor will trigger the commit
  action to the <acronym>SVN</acronym> repository.