Apply suggestions from code review

Co-authored-by: Lorenz Walthert <[email protected]>

Author: owenjonesuob

vignettes/available-hooks.Rmd

@@ -153,15 +153,18 @@ This means each file will be parsed, but code will not be evaluated - neither
 any explicit code in the file, nor any `@eval` tags within roxygen comments.
 This can be useful if your files contain anything other than
 "simple object declarations" (e.g. [box modules](https://github.com/klmr/box/)
-containing `box::use()` calls).
+containing `box::use()` calls). When `--no-eval` is missing, this means dependencies 
+of the code to evaluate must be available for pre-commit. You may list these as 
+`additional_dependencies:` for the `parsable-roxygen` hook in 
+`.pre-commit-config.yaml`.
 
 Inline R code within roxygen comments (i.e. within backticks) is **not**
-evaluated by this hook, whether or not `--no-eval` is specified.
+evaluated by this hook, whether or not `--no-eval` is specified. You would need to run the `roxygenize` hook for that.
 
       id: parsable-roxygen
       args: [--no-eval]
 
-
+This hook was added in version 0.4.3.9000.
 ## `no-browser-statement`
 
 Guarantees you that you don't accidentally commit code with a