aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--en_US.ISO8859-1/articles/rc-scripting/article.sgml6
1 files changed, 3 insertions, 3 deletions
diff --git a/en_US.ISO8859-1/articles/rc-scripting/article.sgml b/en_US.ISO8859-1/articles/rc-scripting/article.sgml
index ef5974dc34..75f7926254 100644
--- a/en_US.ISO8859-1/articles/rc-scripting/article.sgml
+++ b/en_US.ISO8859-1/articles/rc-scripting/article.sgml
@@ -398,9 +398,9 @@ run_rc_command "$1"</programlisting>
<function>set_rcvar</function> is that different operating
systems adopted different conventions for it. Namely,
&os; sticks to the
- <envar><replaceable>name</replaceable>_enable</envar>
+ <envar>${name}_enable</envar>
scheme while NetBSD uses just
- <envar><replaceable>name</replaceable></envar> variables.
+ <envar>${name}</envar> variables in its &man.rc.conf.5;.
For example, our script will be controlled by
<envar>dummy_enable</envar> in &os; and by <envar>dummy</envar>
in NetBSD.</para>
@@ -574,7 +574,7 @@ run_rc_command "$1"</programlisting>
<envar>${name}_program</envar> from &man.rc.conf.5; or
the script itself even if <envar>command</envar> is
unset. In that case, the special properties of
- <envar>${name}_program</envar> are lost, and it becames
+ <envar>${name}_program</envar> are lost, and it becomes
an ordinary variable your script can use for its own
purposes. However, the sole use of
<envar>${name}_program</envar> is discouraged because