wording

Author: HenrikBengtsson

.github/workflows/R-CMD-check.yaml

@@ -38,7 +38,7 @@ jobs:
       _R_CHECK_SUGGESTS_ONLY_: true
       _R_CHECK_THINGS_IN_TEMP_DIR_: true
       _R_CHECK_TESTS_NLINES_: 300
-      RCMDCHECK_ERROR_ON: warning
+      RCMDCHECK_ERROR_ON: error
       ## Specific to futures
       R_FUTURE_CONNECTIONS_ONMISUSE: "error[details=TRUE]"
       R_FUTURE_GLOBALENV_ONMISUSE: "error"

README.md

@@ -50,7 +50,7 @@ environments. For instance, by running P2P workers in a sandboxed
 virtual machine (VM), in a sandboxed Linux container
 (e.g. [Apptainer], [Docker] and [Podman]), or via dedicated sandboxing
 tools (e.g. [Bubblewrap], [Firejail], and macOS `sandbox-exec`), you
-can mitigate some of the risk that malicious code can access the host
+can mitigate some of the risk of malicious code accessing the host
 machine where your personal data lives.
 
 

vignettes/future.p2p-10-getting-started.md

@@ -68,7 +68,7 @@ environments. For instance, by running P2P workers in a sandboxed
 virtual machine (VM), in a sandboxed Linux container
 (e.g. [Apptainer], [Docker] and [Podman]), or via dedicated sandboxing
 tools (e.g. [Bubblewrap], [Firejail], and macOS `sandbox-exec`), you
-can mitigate some of the risk that malicious code can access the host
+can mitigate some of the risk of malicious code accessing the host
 machine where your personal data lives.