diff --git a/vignettes/Catch_errors.Rmd b/vignettes/Catch_errors.Rmd
index 1e35143c..311ff454 100644
--- a/vignettes/Catch_errors.Rmd
+++ b/vignettes/Catch_errors.Rmd
@@ -157,7 +157,7 @@ knitr::opts_chunk$set(
 ```
 
 
-On occasion functions will return `warning` message that either boarder on (or should be treated as) error messages if they influence the veracity of the simulation results. Such examples may include models that appear to 'converge' but do so with non-nonsensical parameter estimates (e.g., negative variances, non-positive definite correlation matrices, maximum iterations reached in an numerical searching algorithm, etc). However, because such issues are non-fatal third-party software (i.e., functions not written by the developer of the simulation) may simply raise a `warning` message for further inspection, whereas in a Monte Carlo simulation experiment such issues should generally be treated as invalid (though their frequency of occurrence should still be tracked, as is the default in `SimDesign`).
+On occasion functions will return `warning` message that either border on (or should be treated as) error messages if they influence the veracity of the simulation results. Such examples may include models that appear to 'converge' but do so with non-nonsensical parameter estimates (e.g., negative variances, non-positive definite correlation matrices, maximum iterations reached in an numerical searching algorithm, etc). However, because such issues are non-fatal third-party software (i.e., functions not written by the developer of the simulation) may simply raise a `warning` message for further inspection, whereas in a Monte Carlo simulation experiment such issues should generally be treated as invalid (though their frequency of occurrence should still be tracked, as is the default in `SimDesign`).
 
 To resolve this issue, and to avoid using a more nuclear option such as setting `option(warn=2)` to treat *all* warnings as errors in the simulation, the function `manageWarnings()` can be used to explicit convert known warning message strings into errors that disrupt the code execution while allowing other warning messages to continue to be raised.