fixes.xml: use more precise wording in some phrases

1 files changed, 7 insertions, 7 deletions

diff --git a/doc/guide/files/fixes.xml b/doc/guide/files/fixes.xml
index 89c410c9968..77ccbee3450 100644
--- a/doc/guide/files/fixes.xml
+++ b/doc/guide/files/fixes.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: fixes.xml,v 1.165 2021/11/08 22:21:33 gutteridge Exp $ -->
+<!-- $NetBSD: fixes.xml,v 1.166 2021/11/09 17:41:27 gutteridge Exp $ -->
 
 <chapter id="fixes"> <?dbhtml filename="fixes.html"?>
 <title>Making your package work</title>
@@ -1516,16 +1516,16 @@ pre-configure:
     <para>There are further similar REPLACE variables available, e.g.,
     <varname>REPLACE_AWK</varname> for packages containing awk scripts,
     and <varname>REPLACE_R</varname> for R. These two, like the others
-    noted above, are defined centrally in
+    noted above, have their actions defined centrally in
     <filename>mk/configure/replace-interpreter.mk</filename>. Other
-    languages define these variables within their own dedicated part of
-    the tree, e.g., PHP defines <varname>REPLACE_PHP</varname> in
-    <filename>lang/php/phpversion.mk</filename>, and Python defines
-    <varname>REPLACE_PYTHON</varname> in
+    languages define the actions of these variables within their own
+    dedicated part of the tree, e.g., <varname>REPLACE_PHP</varname> is
+    actioned in <filename>lang/php/phpversion.mk</filename>, and
+    <varname>REPLACE_PYTHON</varname> is actioned in
     <filename>lang/python/application.mk</filename>. For other languages,
     consult the mk files found within their specific directories (the
     naming convention varies).</para>
-    
+
     <para>Currently, special handling for other languages varies
     in pkgsrc.  If a compiler package provides a
     <filename>buildlink3.mk</filename> file, include that, otherwise