X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=l10n.dbk;h=92bf3b99ba40c7c4b9bc89ea27d37cf02e423a09;hb=e81cdebedab690ef881d87af6f533e51c026565c;hp=c3c7f569b634bd786bae78c8a15b9d2a624bc6a4;hpb=a52b7e8c084a73282543e5e870ae8c68ed2abcb1;p=developers-reference.git

diff --git a/l10n.dbk b/l10n.dbk
index c3c7f56..92bf3b9 100644
--- a/l10n.dbk
+++ b/l10n.dbk
@@ -18,7 +18,7 @@ According to <ulink
 url="http://&www-debian-org;/doc/manuals/intro-i18n/">Introduction to
 i18n</ulink> from Tomohiro KUBOTA, I18N (internationalization) means
 modification of a software or related technologies so that a software can
-potentially handle multiple languages, customs, and so on in the world.  while
+potentially handle multiple languages, customs, and so on in the world,  while
 L10N (localization) means implementation of a specific language for an already
 internationalized software.
 </para>
@@ -33,7 +33,7 @@ character encodings is a really hard problem.
 <para>
 Setting aside the i18n problems, where no general guideline can be given, there
 is actually no central infrastructure for l10n within Debian which could be
-compared to the dbuild mechanism for porting.  So most of the work has to be
+compared to the buildd mechanism for porting.  So most of the work has to be
 done manually.
 </para>
 <section id="l10n-handling">