diff options
| author | Simon Dawson <spdawson@gmail.com> | 2017-03-19 08:34:47 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-03-19 08:34:47 +0000 |
| commit | 8ee16836982b79a14198c75006672677f1f55947 (patch) | |
| tree | 2be49da5eee930b408f14bad5309d8c058c557f6 | |
| parent | 9cc2f50f9cc3191fd796af68d09826c67c02a572 (diff) | |
| download | rails-8ee16836982b79a14198c75006672677f1f55947.tar.gz rails-8ee16836982b79a14198c75006672677f1f55947.tar.bz2 rails-8ee16836982b79a14198c75006672677f1f55947.zip | |
Remove stray back-end from ActiveJob Basics guide
The hyphenated form "back-end" only appears once in this guide; elsewhere, the un-hyphenated form "backend" is used consistently.
| -rw-r--r-- | guides/source/active_job_basics.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/active_job_basics.md b/guides/source/active_job_basics.md index c65d1e6de5..b58ca61848 100644 --- a/guides/source/active_job_basics.md +++ b/guides/source/active_job_basics.md @@ -114,7 +114,7 @@ For enqueuing and executing jobs in production you need to set up a queuing back that is to say you need to decide for a 3rd-party queuing library that Rails should use. Rails itself only provides an in-process queuing system, which only keeps the jobs in RAM. If the process crashes or the machine is reset, then all outstanding jobs are lost with the -default async back-end. This may be fine for smaller apps or non-critical jobs, but most +default async backend. This may be fine for smaller apps or non-critical jobs, but most production apps will need to pick a persistent backend. ### Backends |