* faq-using.xml: Fix typos.

* ntsec.sgml: Ditto.
	* pathnames.sgml: Ditto.
	* setup2.sgml: Ditto.
	* setup-net.sgml: Ditto.
	(setup-dir): Drop paragraph on Unix/DOS file mode.

winsup/doc/ChangeLog

@@ -1,3 +1,12 @@
+2012-02-04  Corinna Vinschen  <corinna@vinschen.de>
+
+	* faq-using.xml: Fix typos.
+	* ntsec.sgml: Ditto.
+	* pathnames.sgml: Ditto.
+	* setup2.sgml: Ditto.
+	* setup-net.sgml: Ditto.
+	(setup-dir): Drop paragraph on Unix/DOS file mode.
+
 2012-01-29  Corinna Vinschen  <corinna@vinschen.de>
 
 	* new-features.sgml (ov-new1.7.10): Add tzset.

winsup/doc/faq-using.xml

@@ -650,7 +650,7 @@ of this is perl's configuration script, which wants
 tell the difference between files with just different case, so the
 configuration fails.
 </para>
-<para>To help with this problem, Cygwin supports casesensitivity
+<para>To help with this problem, Cygwin supports case sensitivity
 starting with Cygwin 1.7.0.  For a detailed description how to use that
 feature see the Cygwin User's Guilde at
 <ulink url="http://cygwin.com/cygwin-ug-net/using-specialnames.html">http://cygwin.com/cygwin-ug-net/using-specialnames.html</ulink>.

winsup/doc/ntsec.sgml

@@ -14,7 +14,7 @@ default.</para>
 be necessarily short.  If you want to learn more about the Windows security
 model, see the <ulink url="http://msdn.microsoft.com/en-us/library/aa374860(VS.85).aspx">Access Control</ulink> article in MSDN documentation.</para>
 
-<para>POSIX concepts and specificially the POSIX security model are not
+<para>POSIX concepts and in particular the POSIX security model are not
 discussed here, but assumed to be understood by the reader.  If you
 don't know the POSIX security model, search the web for beginner
 documentation.</para>

winsup/doc/pathnames.sgml

@@ -22,7 +22,7 @@ appear as subdirectories (for example, you might buy a new disk and
 make it be the <filename>/disk2</filename> directory).</para>
 
 <para>Because many programs written to run on UNIX systems assume
-the existance of a single unified POSIX file system structure, Cygwin
+the existence of a single unified POSIX file system structure, Cygwin
 maintains a special internal POSIX view of the Win32 file system
 that allows these programs to successfully run under Windows.  Cygwin
 uses this mapping to translate from POSIX to Win32 paths as
@@ -223,7 +223,7 @@ filenames bypasses the mount table.
 </para>
 
 <para>If you want to see the current set of mount points valid in your
-session, you can invoking the Cygwin tool <command>mount</command> without
+session, you can invoke the Cygwin tool <command>mount</command> without
 arguments:</para>
 
 <example id="pathnames-mount-ex">
@@ -288,8 +288,8 @@ on a system are subsumed.  The mount options of the cygdrive prefix is
 used for all file access through the cygdrive prefixed drives.  For instance,
 assuming the cygdrive mount options are <literal>binary,posix=0</literal>,
 then any file <literal>/cygdrive/x/file</literal> will be opened in
-binary mode by default (mount option <literal>binary</literal>, and the case
-of the filename doesn't matter (mount option <literal>posix=0</literal>.
+binary mode by default (mount option <literal>binary</literal>), and the case
+of the filename doesn't matter (mount option <literal>posix=0</literal>).
 </para>
 
 <para>The cygdrive prefix flags are also used for all UNC paths starting with
@@ -363,9 +363,9 @@ bypass the information given in the Cygwin mount table.</para>
 
 <para>When accessing files using native Win32 paths as above, Cygwin uses a
 default setting for the mount flags.  All paths using DOS notation will be
-treated as caseinsensitive, and permissions are just faked as if the
+treated as case insensitive, and permissions are just faked as if the
 underlying drive is a FAT drive.  This also applies to NTFS and other
-filesystems which usually are capable of casesensitivity and storing
+filesystems which usually are capable of case sensitivity and storing
 permissions.</para>
 
 </sect2>

winsup/doc/setup-net.sgml

@@ -87,12 +87,6 @@ for programs such as <command>crond</command> and <command>sshd</command>.
 If you do not have the necessary permissions, but still want to use these
 programs, consult the Cygwin mailing list archives about others' experiences.
 
-</para>
-<para>
-The <literal>Default Text File Type</literal> should be left on
-<literal>Unix</literal> (that is, <literal>\n</literal>) unless you
-have a very good reason to switch it to 
-<literal>DOS</literal> (that is, <literal>\r\n</literal>).
 </para>
 </sect2>
 
@@ -150,7 +144,7 @@ setup.exe homepage</ulink>.
 The chooser is the most complex part of <command>setup.exe</command>. 
 Packages are grouped into categories, and one package may belong to multiple 
 categories (assigned by the volunteer package maintainer). Each package
-can be found under any of those categories in the heirarchial chooser view.
+can be found under any of those categories in the hirarchial chooser view.
 By default, <command>setup.exe</command>
 will install only the packages in the <literal>Base</literal> category
 and their dependencies, resulting in a minimal Cygwin installation.

winsup/doc/setup2.sgml

@@ -417,7 +417,7 @@ UTF-16 encoding to store filename information.  Not all characters
 from the Unicode character set are available in a singlebyte or doublebyte
 charset.  While Cygwin has a workaround to access files with unusual
 characters (see <xref linkend="pathnames-unusual"></xref>), a better
-workaround is to use always the UTF-8 character set.i</para>
+workaround is to use always the UTF-8 character set.</para>
 
 <para><emphasis>UTF-8 is the only multibyte character set which can represent
 every Unicode character.</emphasis></para>
@@ -490,7 +490,7 @@ environment, if it's different from the UTF-8 charset.</para>
 
 <note><para>Per POSIX, the name of an environment variable should only
 consist of valid ASCII characters, and only of uppercase letters, digits, and
-the underscore for maximum portablilty.</para></note>
+the underscore for maximum portabilty.</para></note>
 
 <para>Symbolic links, too, may pose a problem when switching charsets on
 the fly.  A symbolic link contains the filename of the target file the