From 8615f8b5c8bee0d32518bdc33f02faf68284ed94 Mon Sep 17 00:00:00 2001 From: Yves Senn Date: Sat, 19 Dec 2015 14:42:09 +0100 Subject: docs, follow up to #22699. [ci skip] --- actioncable/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'actioncable') diff --git a/actioncable/README.md b/actioncable/README.md index d3902f53d1..32f49c215f 100644 --- a/actioncable/README.md +++ b/actioncable/README.md @@ -16,7 +16,7 @@ WebSockets open to your application if they use multiple browser tabs or devices 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, +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 or to both of these channels. At the very least, a consumer should be subscribed to one channel. @@ -395,7 +395,7 @@ bundle exec puma -p 28080 cable/config.ru ``` The above will start a cable server on port 28080. Remember to point your client-side setup against that using something like: -`App.cable = Cable.createConsumer("ws://basecamp.dev:28080")`. +`App.cable = ActionCable.createConsumer("ws://basecamp.dev:28080")`. ### In app -- cgit v1.2.3