os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix a typo and some markup nits

Browse source
This commit is contained in:
Yaroslav Tykhiy 2006-10-26 17:09:29 +00:00
parent d3b1240703
commit 84a463560e
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=28947
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
en_US.ISO8859-1/articles/rc-scripting/article.sgml
View file

@ -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