TEST_CODEOWNERS/rails
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Fix typos in Action Cable guide [ci skip]

Browse Source
This commit is contained in:
Prathamesh Sonpatki 2016-02-28 19:42:39 +05:30
parent 4eaaced784
commit 2ff63580fe
1 changed files with 25 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
guides/source/action_cable_overview.md
View File

@ -35,7 +35,7 @@ client-server connection instance established per WebSocket connection.
## Server-Side Components
### Connections
Connections form the foundaton of the client-server relationship. For every WebSocket
Connections form the foundation of the client-server relationship. For every WebSocket
the cable server is accepting, a Connection object will be instantiated. This instance
becomes the parent of all the channel subscriptions that are created from there on.
The Connection itself does not deal with any specific application logic beyond authentication
@ -149,7 +149,7 @@ consumer can act as a subscriber to a given channel any number of times.
For example, a consumer could subscribe to multiple chat rooms at the same time.
(remember that a physical user may have multiple consumers, one per tab/device open to your connection).
A consumer becomes a subscriber, by creating a subscribtion to a given channel:
A consumer becomes a subscriber, by creating a subscription to a given channel:
```coffeescript
# app/assets/javascripts/cable/subscriptions/chat.coffee
# Assumes you've already requested the right to send web notifications
@ -414,7 +414,7 @@ App.cable.subscriptions.create "AppearanceChannel",
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 invokesan action on the client.
where the server invokes 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: