X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fdev%2Fi18n.texi;h=876f359bff996e274b66d9b3356d2561692af379;hb=f790dbda9d498eef9c9c0a49078adbeecf768d56;hp=3ab86c3d2ec349fb85267ac934bb7c721d9eb304;hpb=3bbb4370239deb29ebbf813d258aef6249e2a431;p=pspp

diff --git a/doc/dev/i18n.texi b/doc/dev/i18n.texi
index 3ab86c3d2e..876f359bff 100644
--- a/doc/dev/i18n.texi
+++ b/doc/dev/i18n.texi
@@ -27,7 +27,7 @@ It's rarely, if ever, necessary to interrogate the system to find out
 the values of the 3 locales.
 However it's important to be aware of the source (destination) locale
 when reading (writing) string data.
-When transfering data between a source and a destination, the appropriate
+When transferring data between a source and a destination, the appropriate
 recoding must be performed.
 
 
@@ -47,7 +47,7 @@ report generated by pspp.  Non-data related strings (Eg: ``Page number'',
 @subsection The data locale
 This locale is the one associated with the data being analysed with pspp.
 The only important aspect of this locale is the character encoding.
-@footnote {It might also be desirable for the LC_COLLATE category to be used for the purposes of sorting data.}
+@footnote{It might also be desirable for the LC_COLLATE category to be used for the purposes of sorting data.}
 The dictionary pertaining to the data contains a field denoting the encoding.
 Any string data stored in a @union{value} will be encoded in the
 dictionary's character set.