aboutsummaryrefslogtreecommitdiffstats
path: root/actioncable
diff options
context:
space:
mode:
authorMawueli Kofi Adzoe <wallclockbuilder@googlemail.com>2016-02-09 22:35:40 -0700
committerMawueli Kofi Adzoe <wallclockbuilder@googlemail.com>2016-02-09 22:35:40 -0700
commitf2fcd3a000f70cc520b9267e82184ab87fea7f80 (patch)
tree77923f47feaa42868497ddf79259cba7cfb305f0 /actioncable
parent21547fc680f22c99ec4ee55f2bc861cb08bd6af7 (diff)
downloadrails-f2fcd3a000f70cc520b9267e82184ab87fea7f80.tar.gz
rails-f2fcd3a000f70cc520b9267e82184ab87fea7f80.tar.bz2
rails-f2fcd3a000f70cc520b9267e82184ab87fea7f80.zip
Fix tiny grammar.
Diffstat (limited to 'actioncable')
-rw-r--r--actioncable/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/actioncable/README.md b/actioncable/README.md
index 5029f583cb..3ed8a23a29 100644
--- a/actioncable/README.md
+++ b/actioncable/README.md
@@ -188,7 +188,7 @@ can be reached as remote procedure calls via a subscription's `perform` method.
The appearance example was all about exposing server functionality to client-side invocation over the WebSocket connection.
But the great thing about WebSockets is that it's a two-way street. So now let's show an example where the server invokes
-action on the client.
+an action on the client.
This is a web notification channel that allows you to trigger client-side web notifications when you broadcast to the right
streams: