* doc/ref/api-modules.texi (Using Guile Modules): improve wording on example about conflict between local definitions and imported ones --- doc/ref/api-modules.texi | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/ref/api-modules.texi b/doc/ref/api-modules.texi index 05a19cc16..8e0f41c25 100644 --- a/doc/ref/api-modules.texi +++ b/doc/ref/api-modules.texi @@ -113,12 +113,12 @@ Here, the interface specification is @code{(ice-9 popen)}, and the result is that the current module now has access to @code{open-pipe}, @code{close-pipe}, @code{open-input-pipe}, and so on (@pxref{Pipes}). -Note in the previous example that if the current module had already -defined @code{open-pipe}, that definition would be overwritten by the -definition in @code{(ice-9 popen)}. For this reason (and others), there -is a second variation of interface specification that not only names a -module to be accessed, but also selects bindings from it and renames -them to suit the current module's needs. For example: +Note in the previous example that if the current module already defines +@code{open-pipe}, that definition has precedence over the definition in +@code{(ice-9 popen)} we try to import. For this reason (and others), +there is a second variation of interface specification that not only +names a module to be accessed, but also selects bindings from it and +renames them to suit the current module's needs. For example: @cindex binding renamer @lisp -- 2.32.0