aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJon Moss <maclover7@users.noreply.github.com>2017-03-19 10:34:54 -0400
committerGitHub <noreply@github.com>2017-03-19 10:34:54 -0400
commit8a808d5ca0c1e1e2e256a16da3b4ff9a95bcc525 (patch)
tree7cfbcf9bc2768914ec41bb424af52bd1d71585af
parentecab515b2f486e2edb8e5e6d6624898c28c0f75a (diff)
parent8ee16836982b79a14198c75006672677f1f55947 (diff)
downloadrails-8a808d5ca0c1e1e2e256a16da3b4ff9a95bcc525.tar.gz
rails-8a808d5ca0c1e1e2e256a16da3b4ff9a95bcc525.tar.bz2
rails-8a808d5ca0c1e1e2e256a16da3b4ff9a95bcc525.zip
Merge pull request #28477 from spdawson/patch-3
Remove stray back-end from ActiveJob Basics guide
-rw-r--r--guides/source/active_job_basics.md2
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