From 6a84234cd220eeef9fa5a24721079d45d9375a81 Mon Sep 17 00:00:00 2001
From: Corinna Vinschen <corinna@vinschen.de>
Date: Wed, 18 Aug 2010 15:28:15 +0000
Subject: [PATCH] 	* pathnames.sgml (pathnames-win32-api): Try to use a
 more clear wording.

---
 winsup/doc/ChangeLog      | 4 ++++
 winsup/doc/pathnames.sgml | 6 ++++--
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog
index 0b1a8c688..d8f398ac0 100644
--- a/winsup/doc/ChangeLog
+++ b/winsup/doc/ChangeLog
@@ -1,3 +1,7 @@
+2010-08-18  Corinna Vinschen  <corinna@vinschen.de>
+
+	* pathnames.sgml (pathnames-win32-api): Try to use a more clear wording.
+
 2010-08-13  Corinna Vinschen  <corinna@vinschen.de>
 
 	* faq-programming.xml (faq.programming.win32-api): Remove simplicity.
diff --git a/winsup/doc/pathnames.sgml b/winsup/doc/pathnames.sgml
index da8e4c1a2..03c4ba087 100644
--- a/winsup/doc/pathnames.sgml
+++ b/winsup/doc/pathnames.sgml
@@ -373,7 +373,7 @@ pathnames.</para>
 <para>When a Cygwin application is started, the Win32 idea of the current
 working directory (CWD) is set to an invalid directory.  This works around
 the problem that the Win32 CWD is locked in a way which restricts POSIX
-functionality.  However, the side effect is that a call to, say,
+functionality.  However, the side effect is that a call to, for instance,
 <function>CreateFile ("foo", ...);</function> will fail, since the Win32
 notion of the CWD is <emphasis>not</emphasis> the same as the Cygwin notion
 of the CWD.</para>
@@ -386,7 +386,9 @@ you have two choices.</para>
 <itemizedlist spacing="compact">
   <listitem>
     <para>Either you call <function>SetCurrentDirectory</function> before
-    calling <function>CreateFile</function>.</para>
+    calling the Win32 function which requires a valid Win32 CWD
+    (<function>CreateFile</function>, <function>CreateProcess</function>,
+    etc).</para>
   </listitem>
   <listitem>
     <para>Or you compile your application as native Win32 (mingw) executable,