MASTER_SHUTDOWN_SHUTDOWN = /etc/condor/shutdown
 {endverbatim}
 
-To activate the shutdown script named "SHUTDOWN", use the =condor_set_shutdown= command with the -exec option.  This command MUST be run while the master is alive.  A shell script like the following may help resolve timing issues; be sure that the user you run it as is privileged (probably root).
+To activate the shutdown script named "SHUTDOWN", use the =condor_set_shutdown= command with the -exec option.  This command must be run each time the master is (re)started by a user with sufficient privilege.  Since start-up times are somewhat variable, you may want to use a retry loop like the one below; make sure that service and condor_set_shutdown are in the PATH.  (If you've automated the start-up of HTCondor, you need to automate running condor_set_shutdown to make this work; if the HTCondor in your VM starts on boot, you could put this in rc.local, for instance.)
 
 {verbatim}
 while ! condor_set_shutdown -exec shutdown; do sleep 1; done
 {endverbatim}
 
-Because of the sleeps and the retries, you can run that shell script fragment immediately after starting (or restarting) the master and not worry about the master not being ready to accept commands.
-
 The script (=/etc/condor/shutdown= in this example) must of course be executable (and have the #! line), and is run by the master as root when the master shuts down.  The following script may be useful as an example to work from.
 
 {verbatim}