"commercial software" -> "proprietary software"

diff --git a/gettext-tools/doc/ChangeLog b/gettext-tools/doc/ChangeLog
index a11ccde505aa9a7edda4b1bbc897dcd38a8038d0..7877fb88639e51f2ebbf5b0bdfc1ee38a9da289a 100644 (file)
--- a/gettext-tools/doc/ChangeLog
+++ b/gettext-tools/doc/ChangeLog
@@ -1,3 +1,9 @@
+2007-08-18  Bruno Haible  <bruno@clisp.org>
+
+       * gettext.texi (Why): Don't oppose commercial software to free
+       software.
+       Reported by Kaloian Doganov <kaloian@doganov.org>.
+
 2007-06-30  Bruno Haible  <bruno@clisp.org>
 
        * gettext.texi: Fix English typo.

diff --git a/gettext-tools/doc/gettext.texi b/gettext-tools/doc/gettext.texi
index 3d6ab696c2df54ce823bcaca5e7e69a37ecf8d3d..c5e629a980beca4ef5a01dbce7e76f597d729467 100644 (file)
--- a/gettext-tools/doc/gettext.texi
+++ b/gettext-tools/doc/gettext.texi
@@ -529,7 +529,7 @@ Please include the manual's edition number and update date in your messages.
 
 Usually, programs are written and documented in English, and use
 English at execution time to interact with users.  This is true
-not only of GNU software, but also of a great deal of commercial
+not only of GNU software, but also of a great deal of proprietary
 and free software.  Using a common language is quite handy for
 communication between developers, maintainers and users from all
 countries.  On the other hand, most people are less comfortable with