[skip vbump] Update docs (from roxygen2 warnings)

Author: llrs-roche

R/qenv-within.R

@@ -4,7 +4,7 @@
 #' `within` accepts only inline expressions (both simple and compound) and allows to substitute `expr`
 #' with `...` named argument values.
 #' Functions that trigger side effects like `options` or `set.seed` can be linked to specific objects for further code retrieval (with `get_code`), but only through `eval_code` where code input as `character`. `within` works on `expressions` that do not preserve comments, hence you can not use `# @linksto` tag explained in `get_code`.
-#' @alias within
+#' @aliases within
 #' @section Using language objects with `within`:
 #' Passing language objects to `expr` is generally not intended but can be achieved with `do.call`.
 #' Only single `expression`s will work and substitution is not available. See examples.

R/utils-get_code_dependency.R

@@ -365,7 +365,7 @@ move_functions_after_arrow <- function(ans, functions) {
 #' Static code analysis may be insufficient to determine which objects are created or modified by such a function call.
 #' The `@linksto` comment tag is introduced to mark a call as having a (side) effect on one or more objects.
 #' With this tag a complete object dependency structure can be established.
-#' Read more about side effects and the usage of `@linksto` tag in [`get_code_dependencies()`] function.
+#' Read more about side effects and the usage of `@linksto` tag in [`get_code()`] function.
 #'
 #' @param pd `data.frame`;
 #'  one of the results of `utils::getParseData()` split into subsets representing individual calls;