Merge pull request #65 from microMolvi/typo-fixes

fix multiple minor typos

LDP/guide/docbook/Linux-Dictionary/I.xml

@@ -6380,7 +6380,7 @@ Internet
 </glossterm>
 <glossdef>
 <para>
-A worldwide network of networks. It si also the network of networks that connects more than three million computers (called hosts). The Internet is the virtual space in which users send and receive email, login to remote computers (telnet), browse databases of information (gopher, World Wide Web, WAIS), and send and receive programs (ftp) contained on these computers. From Glossary of Distance Education and Internet Terminology
+A worldwide network of networks. It is also the network of networks that connects more than three million computers (called hosts). The Internet is the virtual space in which users send and receive email, login to remote computers (telnet), browse databases of information (gopher, World Wide Web, WAIS), and send and receive programs (ftp) contained on these computers. From Glossary of Distance Education and Internet Terminology
 <ulink url="http://www.tldp.org/LDP/Linux-Dictionary/html/index.html">http://www.tldp.org/LDP/Linux-Dictionary/html/index.html</ulink>
 </para>
 </glossdef>

LDP/howto/docbook/Apache-WebDAV-LDAP-HOWTO.xml

@@ -616,7 +616,7 @@ has access to this folder.
   </Limit>
 </screen>
 </para>
-<para>Basically we are limiting the PUT POST DELETE PROPPATH MKCOL COPY MOVE LOCK and UNLOCK to an individual who has the UID of 334455. Everone else will be able to use the methods GET and PROPFIND on the resources, but not any other method.</para>
+<para>Basically we are limiting the PUT POST DELETE PROPPATH MKCOL COPY MOVE LOCK and UNLOCK to an individual who has the UID of 334455. Everyone else will be able to use the methods GET and PROPFIND on the resources, but not any other method.</para>
 
 
 </sect2>

LDP/howto/docbook/Linux+Windows-HOWTO/Linux+Windows-HOWTO.sgml

@@ -929,7 +929,7 @@ bash> e2fsck /dev/hda2
 		<para>Linux uses separate clocks for each of these.  On a linux only system, the hardware clock is usually set to UTC (Universal Time Coordinate), the network standard.  The network and file operations clock are usually just views of the hardware clock by linux.  For display, linux usually shifts the hardware clock according to the timezone and date.</para>
 		<para>Since Windows supports only one clock, you must decide (unless you live in Greenwich England) whether to set the hardware clock to local time or UTC.</para>
 		<para>If you use UTC, you will have to mentally convert the time displayed by Windows to local time.</para>
-		<para>If you use local time, some network activity may become confused.  International email problems are most commonly reported.  Mail sent from Berlin at 1300 local time may be stored a second later in New York at 1200 UTC where it awaits a channel to its San Francisco destination.  To save space, the New York host may delete mail that could not be sent in a reasonable time of 30min.  If the Berlin mail was unclear that ti was sent at 1300 Berlin time, or if the New York host is unwilling to do the conversion, the email may be lost as undliverable after 1 hour (1300 - 1200).</para>
+		<para>If you use local time, some network activity may become confused.  International email problems are most commonly reported.  Mail sent from Berlin at 1300 local time may be stored a second later in New York at 1200 UTC where it awaits a channel to its San Francisco destination.  To save space, the New York host may delete mail that could not be sent in a reasonable time of 30min.  If the Berlin mail was unclear that it was sent at 1300 Berlin time, or if the New York host is unwilling to do the conversion, the email may be lost as undliverable after 1 hour (1300 - 1200).</para>
 	</listitem>
 </itemizedlist>
 

LDP/howto/docbook/Program-Library-HOWTO.sgml

@@ -470,7 +470,7 @@ telling you what dependencies are detected and which SOs are loaded
 in what order.
 Setting LD_DEBUG to ``bindings'' displays information
 about symbol binding, setting it to ``libs'' displays the
-library search paths, and setting ti to ``versions'' displays the
+library search paths, and setting it to ``versions'' displays the
 version depdendencies.
 </para>
 <para>

LDP/howto/docbook/XFree86-Second-Mouse.sgml

@@ -66,7 +66,7 @@ protocol</emphasis> and the <emphasis>mouse device</emphasis>. Wherever
 possible, I try to provide appropriate examle. 
 </para>
 <para>
-The instructions for X are divided into two sections, one fro XFree version 3 and one
+The instructions for X are divided into two sections, one for XFree version 3 and one
 for XFree 4. The format of the XF86Config file has significantly changed between
 versions and requires slightly different approach. In XFree 3.x, the second
 mouse has to appear in an <emphasis>Xinput</emphasis> section, which has

LDP/howto/linuxdoc/SPARC-HOWTO.sgml

@@ -539,7 +539,7 @@ FLOPPY=/dev/fd0
 PATH=/path_to_big_package_to_compile
 
 #
-# this section si meant to 
+# this section is meant to 
 # test the CDROM and floppy drives
 # comment what you do not need to
 # test

LDP/ldpwn/20041222.xml

@@ -48,7 +48,7 @@ reviewed internally by IBM.</para></listitem>
 <listitem><para>Avy Alkalay put together the old Font HOWTO and the FDU
 HOWTO and did a great deal of rewriting in the new <ulink
 url="http://avi.alkalay.net/linux/docs/font-howto/font-howto.tar.gz">FONT
-HOWTO</ulink>.  At the request of the author, teh FDU HOWTO will be
+HOWTO</ulink>.  At the request of the author, the FDU HOWTO will be
 removed to the Obsolete section.</para></listitem>
 
 <listitem><para>.</para></listitem>

LDP/retired/Ldap-Implementation-HOWTO/section-dns.sgml

@@ -17,7 +17,7 @@ Then, if you want ldap to override your local dns server, you have to make sure
 If not, you will have a nice recursive lookup going. -- You want to look up a host, it's not in files, so we try to contact the ldap server, whose ip we don't know, so we try to look it up in files, where we cannot find it, so we try to contact the ldap server -- get the point? You could bypass this problem entirely by referring to your ldap server with an ip number instead of a hostname (in <FILENAME>/etc/ldap.conf</FILENAME>, that is.)</PARA>
 </SECT3>
 <SECT3><TITLE>Schema</TITLE>
-<PARA>The schema used for this, and similar services, can be found in RFC 2307. Entries used for mapping names to ipnumbers are in an objectclass <EMPHASIS>ipHost</EMPHASIS>. The name part of the mapping is given ni the attribute <EMPHASIS>cn</EMPHASIS>, while the ip part lives in <EMPHASIS>ipHostNumber</EMPHASIS>.
+<PARA>The schema used for this, and similar services, can be found in RFC 2307. Entries used for mapping names to ipnumbers are in an objectclass <EMPHASIS>ipHost</EMPHASIS>. The name part of the mapping is given in the attribute <EMPHASIS>cn</EMPHASIS>, while the ip part lives in <EMPHASIS>ipHostNumber</EMPHASIS>.
 A typical ldif entry would therefore look like this:</PARA>
 <PARA><PROGRAMLISTING FORMAT="LINESPECIFIC">
 dn: cn=somehostname.mydomain.com,ou=Network,o=YourOrg,c=NL