--- a/ChangeLog	Tue Dec 05 11:02:33 2017 -0500
+++ b/ChangeLog	Sun Dec 10 14:00:43 2017 +0100
@@ -1,3 +1,9 @@
+2017-12-10  Bruno Haible  <bruno@clisp.org>
+
+	doc: Tweak wording.
+	* doc/gnulib-tool.texi (Multiple instances): Talk about "programs", not
+	"binaries".
+
 2017-12-05  Sam Steingold  <sds@gnu.org>
             Bruno Haible  <bruno@clisp.org>
 

--- a/doc/gnulib-tool.texi	Tue Dec 05 11:02:33 2017 -0500
+++ b/doc/gnulib-tool.texi	Sun Dec 10 14:00:43 2017 +0100
@@ -44,7 +44,7 @@
 * Modified imports::            Changing the import specification.
 * Simple update::               Tracking Gnulib development.
 * Source changes::              Impact of Gnulib on your source files.
-* Multiple instances::          Using Gnulib for both a library and a binary
+* Multiple instances::          Using Gnulib for both a library and a program
 * gettextize and autopoint::    Caveat: @code{gettextize} and @code{autopoint} users!
 * Localization::                Handling Gnulib's own message translations.
 * VCS Issues::                  Integration with Version Control Systems.
@@ -452,18 +452,18 @@
 
 
 @node Multiple instances
-@section Using Gnulib for both a library and a binary
+@section Using Gnulib for both a library and a program
 
-Your project might build both a library and some accompanying binaries
+Your project might build both a library and some accompanying programs
 in the same source tree. In that case you might want to use different
-modules for the library than for the binaries. Typically the binaries
+modules for the library than for the programs. Typically the programs
 might want to make use of @code{getopt-posix} or @code{version-etc},
 while the library wants to stay clear of these modules for technical
 or licensing reasons.
 
 Let's assume that your project contains a @file{lib} directory where
 the source of the library resides and a @file{src} directory for the
-sources of the binaries as follows.
+sources of the programs as follows.
 
 @example
 .
@@ -544,8 +544,8 @@
 ...
 @end example
 
-Correspondingly for the binary you will have to add something along
-the lines of to the following:
+Correspondingly for the programs you will have to add something like
+this:
 
 @example
 ...
@@ -559,6 +559,7 @@
 depends on the @option{--lib} option in @command{gnulib-tool}
 invocation.
 
+
 @node gettextize and autopoint
 @section Caveat: @code{gettextize} and @code{autopoint} users