Update spelling

R/rrq_controller.R

@@ -764,7 +764,7 @@ rrq_controller <- R6::R6Class(
     ##' @description Fetch times for tasks at points in their life cycle.
     ##' For each task returns the time of submission, starting
     ##' and completion (not necessarily successfully; this includes
-    ##' errors and interruptions).  If a task has not reacched a point
+    ##' errors and interruptions).  If a task has not reached a point
     ##' yet (e.g., submitted but not run, or running but not finished)
     ##' the time will be `NA`).  Times are returned in unix timestamp
     ##' format in UTC; you can use [redux::redis_time_to_r] to convert

inst/WORDLIST

@@ -1,5 +1,6 @@
 CodeFactor
 HPC
+POSIXt
 Rdata
 Redis
 WIP
@@ -34,6 +35,7 @@ pid
 rds
 redis
 rrq's
+segfaults
 storr
 undeferred
 unpauses

vignettes/rrq.Rmd

@@ -557,7 +557,7 @@ If you use many workers, particularly on different machines, you may not notice
 
 By default, if this happens when your worker is running a task, that task status will forever be stuck in `RUNNING`.
 
-`rrq` provides a simple heartbeat process, if requested, to detect when a worker has disppeared. To do this, we run a second process on each worker that periodically writes to the Redis database on a key that will expire in a time slightly longer than that period, in effect making a [dead man's switch](https://en.wikipedia.org/wiki/Dead_man%27s_switch) - see `rrq::rrq_heartbeat` for details.
+`rrq` provides a simple heartbeat process, if requested, to detect when a worker has disappeared. To do this, we run a second process on each worker that periodically writes to the Redis database on a key that will expire in a time slightly longer than that period, in effect making a [dead man's switch](https://en.wikipedia.org/wiki/Dead_man%27s_switch) - see `rrq::rrq_heartbeat` for details.
 
 To enable the heartbeat, save a worker configuration with the `heartbeat_period` set to some number of seconds. Below we use 2 seconds so that this example runs reasonably quickly, but in practice something like 60 might be slightly less load on your Redis server.
 

vignettes_src/rrq.Rmd

@@ -452,7 +452,7 @@ If you use many workers, particularly on different machines, you may not notice
 
 By default, if this happens when your worker is running a task, that task status will forever be stuck in `RUNNING`.
 
-`rrq` provides a simple heartbeat process, if requested, to detect when a worker has disppeared. To do this, we run a second process on each worker that periodically writes to the Redis database on a key that will expire in a time slightly longer than that period, in effect making a [dead man's switch](https://en.wikipedia.org/wiki/Dead_man%27s_switch) - see `rrq::rrq_heartbeat` for details.
+`rrq` provides a simple heartbeat process, if requested, to detect when a worker has disappeared. To do this, we run a second process on each worker that periodically writes to the Redis database on a key that will expire in a time slightly longer than that period, in effect making a [dead man's switch](https://en.wikipedia.org/wiki/Dead_man%27s_switch) - see `rrq::rrq_heartbeat` for details.
 
 To enable the heartbeat, save a worker configuration with the `heartbeat_period` set to some number of seconds. Below we use 2 seconds so that this example runs reasonably quickly, but in practice something like 60 might be slightly less load on your Redis server.