applied a patch for carsten niehaus (fixes some typos)

1 files changed, 9 insertions, 9 deletions

diff --git a/docs/usermanual/i18n.sgm b/docs/usermanual/i18n.sgm
index faa0b03..0c52392 100644
--- a/docs/usermanual/i18n.sgm
+++ b/docs/usermanual/i18n.sgm
@@ -5,13 +5,13 @@
 		as possible.  In this chapter the process of translating &opie; and its
 		documentation is explained.
 	</para>
 	<para>
 		To ensure that &opie; can be used by as many people as possible the
 		&opie;-project aims to be translated in as many languages as possible. Of
-		course, as there are so many different languages, there is always a lot
+		course, as there are so many different languages, there is always a lot of
 		work to do. Furthermore, &opie; evolves and thus most likely there are
 		translations for applications which should be updated. In this tutorial
 		you will learn how to help &opie; to be available in as many languages as
 		possible and see how easy it is to give something very much respected to
 		the open-source community.
 	</para>
@@ -51,32 +51,32 @@
 	</para>
 </section> 
 
 <section>
 	<title>Styleguide</title> 
 	<para>
-		To ensure a high quality of the translations the translatiors have to keep certain things
+		To ensure a high quality of the translations the translators have to keep certain things
 		in mind.
 	</para>
 	<itemizedlist mark='opencircle'>
 		<listitem>
 		<para>
 			The applications do not speak to the user. This means that for example it should not
 			be <errortext>I didn't find the file!</errortext> but <errortext>File not found!</errortext>.
 		</para>
 		</listitem>
 		<listitem>
 		<para>
-			Try not to use exclamationmarks. If the users sees them to often the ! looses it function
-			as a amplifier of a warning.
+			Try not to use exclamation marks. If the users see them to often the ! looses it function
+			as an amplifier of a warning.
 		</para>
 		</listitem>
 		<listitem>
 		<para>
-			Don't put a space in front of a punctuation mark. So write eg "this is a demonstation!" instead
-			of "this is a demonstation !".
+			Don't put a space in front of a punctuation mark. So write eg "this is a demonstration!" instead
+			of "this is a demonstration !".
 		</para>
 		</listitem>
 	</itemizedlist>
 </section>
 
 <section>
@@ -114,26 +114,26 @@
 		If you choose to use an editor like VIM instead of the prefered tool
 		-Linguist- you have to remove that mark and add the translated string
 		between the two translation-tags.
 	</para>
 	<para>
 		It might happen that you see <emphasis>type="obsolete"</emphasis> in a
-		.ts-file. You should not translate these stings as they do no longer appear in the
+		.ts-file. You should not translate these strings as they do no longer appear in the
 		application. The translationcoordinator removes those strings from time to time. In
 		Linguist those strings are grey and not translatable.
 	</para>
 </section> 
 
 <section>
 	<title>Filetypes</title>
 	<para>
 		As a translator one needs to know three different filetypes.
 		
 		<filename class='extension'>ts</filename>
 		.ts-files are the most important files for translators.  In these files are all strings which
-		need to be translated and the translations themselfs.  All .ts-files are located in 
+		need to be translated and the translations themselves.  All .ts-files are located in 
 		<filename class='directory'>OPIEDIR/i18n/xx</filename> while xx is a languagecode (eg. de or de).  
 		In theory .ts-files are the only ones a translator needs to know.
 		
 		<filename class='extension'>pro</filename>
 		Every application has a .pro-file from which the Makefiles are generated.  As a translator
 		you need to check if in every .pro-file is a line for the language you want to translate to.  
@@ -183,13 +183,13 @@
 			If you find a string like "Form1" contact the translation coordinator. These strings
 			should not be in the translationfiles. You don't need to translate them.
 		</para>
 		</listitem>
 		<listitem>
 		<para>
-			If you check you translation and see an un-translated string even though your translationfile
+			If you check your translation and see an un-translated string even though your translation file
 			is 100% translated use the bug tracking system and/or contact the author of that application
 			directly so that this bug is fixed.
 		</para>
 		</listitem>
 	</itemizedlist>
 	</para>