Update minor typo

diff --git a/Installation.md b/Installation.md
index 951fd04607992e695088a72d63ad22e8dedc88c4..cfedf6ddd8a724b83cc13f5e6d6e289333328520 100644 (file)
--- a/Installation.md
+++ b/Installation.md
@@ -39,7 +39,7 @@ This will create the repo checkout in the directory *~/code/*.
 16. If you enabled the documentation building process in the *build-farm.conf*, then you can try to build it with `./run_build --test --verbose=2 --only-steps=configure,make-doc`.  For documentation generation to succeed, it will require extra packages to be installed to support xml, xslt, pdf, and a few other things. Please see the comments on the [Building Documentation](./BuildingDocs.html) page.
 17. If you can get past each of these steps, then your build farm system meets the minimum requirements.
 18. The official process can be kicked off by running `/home/farm/code/run_cron --run-all`.  This will run the default build configuration, keep track of the git repository status, and upload the build results to the server.
 16. If you enabled the documentation building process in the *build-farm.conf*, then you can try to build it with `./run_build --test --verbose=2 --only-steps=configure,make-doc`.  For documentation generation to succeed, it will require extra packages to be installed to support xml, xslt, pdf, and a few other things. Please see the comments on the [Building Documentation](./BuildingDocs.html) page.
 17. If you can get past each of these steps, then your build farm system meets the minimum requirements.
 18. The official process can be kicked off by running `/home/farm/code/run_cron --run-all`.  This will run the default build configuration, keep track of the git repository status, and upload the build results to the server.

-19. Once that command runs with no complaints, add it to the **farm** user crontab.  You can run it at whatever frequency you choose, I suggest 2 hours.  If a previous instantiation is still running, the script will detect the lockfile and exit so as not to step on each other. **Caution** Cron provides a highly sanitized environment to the run_cron script. Depending on your cron version you may supply a `PATH=…` line in your crontab, or you need to call a wrapper script around `run_cron`:
+19. Once that command runs with no complaints, add it to the **farm** user crontab.  You can run it at whatever frequency you choose, I suggest 2 hours.  If a previous instantiation is still running, the script will detect the lockfile and exit so as not to step on each other. **Caution:** Cron provides a highly sanitized environment to the `run_cron` script. Depending on your Cron version you may supply a `PATH=...` line in your crontab, or you need to call a wrapper script around `run_cron`:

 
     ````
     #!/bin/bash
 
     ````
     #!/bin/bash