Skip to content

readme typos #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 9, 2013
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ link, the trigger would be fired on the ```<a>``` element. This, of course,
bubbles up, but allows you to easily listen only for events on particular tags.

Every event also sends as its first parameter, the element itself, in case you
were listing at a higher level in the chain, you still would have easy access to
were listening at a higher level in the chain, you still would have easy access to
the relevant node.


Expand All @@ -112,7 +112,7 @@ A single argument is sent with this event and is the jQuery object for the node:

### ```eldarion-ajax:success```

This is the event that is triggered once the server receives a successful
This is the event that is triggered once the browser receives a successful
response (status code 200) from the server. You can handle this in order to
provide your own processors if the ones that ship by default do not meet your
needs.
Expand All @@ -128,7 +128,7 @@ the JSON data from the server:

### ```eldarion-ajax:error```

This event sends a request for 400, 404, and 500 status codes.
This event is triggered for 400, 404, and 500 status codes.


### ```eldarion-ajax:complete```
Expand Down