fts: when there is no risk of overlap, use memcpy, not memmove

[gnulib.git] / doc / gnulib-intro.texi

diff --git a/doc/gnulib-intro.texi b/doc/gnulib-intro.texi
index 64faa35..d7bce7a 100644 (file)
--- a/doc/gnulib-intro.texi
+++ b/doc/gnulib-intro.texi
@@ -111,7 +111,7 @@ As of 2011, the list of supported platforms is the following:
 glibc systems.  With glibc 2.8 or newer, they are frequently tested.  With
 glibc 2.3 or newer, they are occasionally tested.
 @item
-MacOS X.  In versions 10.5 and 10.6, it's frequently tested.  In version
+Mac OS X.  In versions 10.5 and 10.6, it's frequently tested.  In version
 10.4, it's rarely tested.
 @item
 FreeBSD 6.0 or newer is occasionally tested.  FreeBSD 5.x is rarely tested.
@@ -304,8 +304,8 @@ against the out-of-memory condition.
 Examples are a module for copying a file --- the portability problems
 relate to the copying of the file's modification time, access rights,
 and extended attributes --- or a module for extracting the tail
-component of a file name --- here the portability to Woe32 requires a
-different API than the classical POSIX @code{basename} function.
+component of a file name --- here the portability to native Windows
+requires a different API than the classical POSIX @code{basename} function.
 
 @subsection Reusable application code