the example so that a reader can understand it better.
Note current $* misuse in run_rc_command so that a reader who understands
$@ and experiments with its application to run_rc_command isn't confused.
Suggested by: dougb (1st explicitly and 2nd implicitly)
stronger, as suggested by dougb@, but do so in the right context.
I.e., don't fire all the requirements at once in the last section,
but tell each of them where the current topic is most appropriate.
Polish some wording and markup.
${name}, PROVIDE, and rc.conf var prefix.
- Distinguish flags from options when telling why -foo
doesn't belong in $command_args. ${name}_flags can
contain both dashed options and arguments, so saying
"flags" when I mean options was confusing.
Suggested by: dougb
- Be more concise and clear on the requirement of /bin/sh;
the former details weren't really interesting.
- Link to the rc.d section of Porter's Handbook.
- Mention /etc/network.subr.
Suggested by: dougb
