diff --git a/docs/best-practices.md b/docs/best-practices.md index 7faf81aa..abf67ab1 100644 --- a/docs/best-practices.md +++ b/docs/best-practices.md @@ -38,7 +38,7 @@ class SafeFetchTask(Task): retry_current_job() ``` -Remember to add the base recurring jobs as explained in [Jobs maintenance](jobs-maintenance.md) to have `retry` jobs actuallt requeued. +Remember to add the base recurring jobs as explained in [Jobs maintenance](jobs-maintenance.md) to have `retry` jobs actually requeued. ## Using your own base Task class @@ -75,4 +75,4 @@ class BaseTask(Task): if self.retry_on_http_error: retry_current_job() -``` \ No newline at end of file +``` diff --git a/docs/jobs.md b/docs/jobs.md index ffc25a81..7fe243aa 100644 --- a/docs/jobs.md +++ b/docs/jobs.md @@ -103,7 +103,7 @@ A regular Python logging object that should be used in your task code. It will m * `connections` -A lazy-loaded object containing the worker's connections to MongoDB and Redis. You can implement your own connection factories to instanciate other services lazily. +A lazy-loaded object containing the worker's connections to MongoDB and Redis. You can implement your own connection factories to instantiate other services lazily. * `run_task(path, params)` diff --git a/docs/queues.md b/docs/queues.md index c388a9ef..8864fc20 100644 --- a/docs/queues.md +++ b/docs/queues.md @@ -20,7 +20,7 @@ There are 4 types of raw queues. The type of a queue is determined by a suffix i * ```_sorted_set``` : The most powerful MRQ queue type, stored in a Redis ZSET. Allows you to order (and re-order) the tasks to be dequeued. Like ```_set```, task parameters will be unique. * ```_timed_set``` : A special case of ```_sorted_set```, where tasks are sorted with a UNIX timestamp. This means you can schedule tasks to be executed at a precise time in the future. -Raw queues need a special entry in the configuration to unserialize their "raw" parameters in a regular dict of parameters. They also need to be linked to a regular queue ("default" if none) for providing visibility and retries, after they are dequeued from the raw queue. +Raw queues need a special entry in the configuration to deserialize their "raw" parameters in a regular dict of parameters. They also need to be linked to a regular queue ("default" if none) for providing visibility and retries, after they are dequeued from the raw queue. This is an example of raw queue configuration: