aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJon Moss <maclover7@users.noreply.github.com>2016-02-08 19:58:42 -0500
committerJon Moss <maclover7@users.noreply.github.com>2016-02-08 19:58:42 -0500
commit43e902a65fbdf81a09fa498e34568eb32c84fe52 (patch)
tree7ec1b04c71a7d9c1193124ca9715c0c341d68e6c
parent783858c8e150eb0f98d7e5d893e492ee08998662 (diff)
parent3f184cab489618aed0b2969ad7893ee3bdd7a843 (diff)
downloadrails-43e902a65fbdf81a09fa498e34568eb32c84fe52.tar.gz
rails-43e902a65fbdf81a09fa498e34568eb32c84fe52.tar.bz2
rails-43e902a65fbdf81a09fa498e34568eb32c84fe52.zip
Merge pull request #23567 from kamipo/fix_typo
Fix typo [ci skip]
-rw-r--r--actioncable/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/actioncable/README.md b/actioncable/README.md
index 7f7a830e6c..5029f583cb 100644
--- a/actioncable/README.md
+++ b/actioncable/README.md
@@ -17,7 +17,7 @@ The client of a WebSocket connection is called the consumer.
Each consumer can in turn subscribe to multiple cable channels. Each channel encapsulates
a logical unit of work, similar to what a controller does in a regular MVC setup. For example,
-you could have a `ChatChannel` and a `AppearancesChannel`, and a consumer could be subscribed to either
+you could have a `ChatChannel` and an `AppearancesChannel`, and a consumer could be subscribed to either
or to both of these channels. At the very least, a consumer should be subscribed to one channel.
When the consumer is subscribed to a channel, they act as a subscriber. The connection between