Regenerate and fix spelling

R/parallel.R

@@ -19,7 +19,7 @@
 ##' `hipercow_resources`.
 ##'
 ##' For example, you could request 32 cores with `hipercow_resources`,
-##' and then calll `hipercow_parallel` with `cores_per_process = 4`,
+##' and then call `hipercow_parallel` with `cores_per_process = 4`,
 ##' and hipercow will create a local cluster with 8 processes, each
 ##' of which reporting `4` cores if that process calls
 ##' `hipercow_parallel_get_cores`.

R/task-purge.R

@@ -23,13 +23,13 @@
 ##'
 ##' # Consequences of deletion
 ##'
-##' A nonexhaustive list:
+##' A non-exhaustive list:
 ##'
 ##' * If you delete a task that is part of a [task_retry] chain, then
 ##'   all tasks (both upstream and downstream in that chain) are
 ##'   deleted
 ##' * Once we support task dependencies (mrc-4797), deleting tasks
-##'   will mark any unrun dependent task as impossible, or perhaps
+##'   will mark any not-yet-run dependent task as impossible, or perhaps
 ##'   delete it too, or prevent you from deleting the task; we've not
 ##'   decided yet
 ##' * You may have a bundle that references a task that you delete, in

R/zzz.R

@@ -3,7 +3,7 @@ cache <- new.env(parent = emptyenv())
 ##' The default set of environment variables used for all tasks.
 ##'
 ##' These are chosen to provide the best general experience. The default
-##' variables may be overriden globally by setting the hipercow.default_envvars
+##' variables may be overridden globally by setting the hipercow.default_envvars
 ##' option, or on a per-task and variable basis by assigning a different value
 ##' to the environment variable in question.
 ##'

inst/WORDLIST

@@ -1,22 +1,33 @@
 BitWarden
+BuildQueue
 CRAN's
+CmdStan
 DIDE
 DIDE's
 HPC
 ICT
 InfiniBand
+JDK
+OpenJDK
 OpenMP
+PBS
 R's
 RCS
 RStudio
+RTools
 Rmd
 Rtools
+StackOverflow
+SystemRoot
 ZScaler
 alloc
+azul
+backends
 callr
 chmod
 cli
 cli's
+cmdstanr
 codecov
 com
 conan
@@ -37,14 +48,19 @@ lockfile
 macOS
 mountname
 mountpoint
+mrc
 pkgdepends
 redis
 redux
 reestablished
 renv
 rfiglet
 rlang
+rrq
+rstan
 src
+stan
+standalone
 std
 supercedes
 th

vignettes/administration.Rmd

@@ -112,7 +112,7 @@ echo Using RTOOLS43_HOME = %RTOOLS43_HOME%
 echo Using JAVA_HOME = %JAVA_HOME%
 ```
 
-These get copied to `C:\Windows` on each cluster node, using the HPC Cluster Manager. You simply select the nodes, right click, "Run Commmand", and look in the history for previous copy commands, to copy the batch files in to %SystemRoot% - hence they are always in the path on every node. You also need to edit the permissions to allow everyone to read the file, by running this on each cluster node:-
+These get copied to `C:\Windows` on each cluster node, using the HPC Cluster Manager. You simply select the nodes, right click, "Run Command", and look in the history for previous copy commands, to copy the batch files in to %SystemRoot% - hence they are always in the path on every node. You also need to edit the permissions to allow everyone to read the file, by running this on each cluster node:-
 
 ```
 cacls %SYSTEMROOT%\setr64_*.bat /e /p everyone:r

vignettes/details.Rmd

@@ -41,7 +41,7 @@ A number, being the maximum size object (in bytes) that we will save when creati
 
 ### `hipercow.default_envvars`
 
-A `hipercow_envvars` object, with environment variables that will be added to every task created. Hipercow sets a few environment variables by default to improve the user experience. These variables can be overriden per-task by passing a `envvars` parameter when creating tasks, or globally by defining this option.
+A `hipercow_envvars` object, with environment variables that will be added to every task created. Hipercow sets a few environment variables by default to improve the user experience. These variables can be overridden per-task by passing a `envvars` parameter when creating tasks, or globally by defining this option.
 
 Environment variables for a task are computed by collecting (in increasing order of preference):