Permalink
Browse files

Docs: correct spelling of "receive"

  • Loading branch information...
jaspermdegroot committed Jul 7, 2012
1 parent 979dc5c commit db572dc85022677f635b5103ca1c5daa5ead673f
Showing with 9 additions and 9 deletions.
  1. +5 −5 docs/api/events-nav.html
  2. +4 −4 docs/api/events.html
View
@@ -360,7 +360,7 @@ <h2>Page change events</h2>
<p>Navigating between pages in the application is usually accomplished through a call to <code>$.mobile.changePage()</code>. This function is responsible for making sure that the page we are navigating to is loaded and inserted into the DOM, and then kicking off the transition animations between the current active page, and the page the caller wants to to make active. During this process, which is usually asynchronous, changePage() will fire off 2 events. The first is <code>pagebeforechange</code>. The second event depends on the success or failure of the change request. It will either be <code>pagechange</code> or <code>pagechangefailed</code>.</p>
<dl>
<dt><code>pagebeforechange</code></dt>
- <dd>This event is triggered prior to any page loading or transition. Callbacks can prevent execution of the changePage() function by calling preventDefault on the event object passed into the callback. The callback also recieves a data object as its 2nd arg. The data object has the following properties:
+ <dd>This event is triggered prior to any page loading or transition. Callbacks can prevent execution of the changePage() function by calling preventDefault on the event object passed into the callback. The callback also receives a data object as its 2nd arg. The data object has the following properties:
<ul>
<li><code>toPage</code> (object or string)
<ul>
@@ -410,7 +410,7 @@ <h2>Page transition events</h2>
<p>Page transitions are used to animate the change from the current active page (fromPage) to a new page (toPage). Events are triggered before and after these transitions so that observers can be notified whenever pages are shown or hidden. The events triggered are as follows:</p>
<dl>
<dt><code>pagebeforeshow</code></dt>
- <dd>Triggered on the "toPage" we are transitioning to, before the actual transition animation is kicked off. Callbacks for this event will recieve a data object as their 2nd arg. This data object has the following properties on it:
+ <dd>Triggered on the "toPage" we are transitioning to, before the actual transition animation is kicked off. Callbacks for this event will receive a data object as their 2nd arg. This data object has the following properties on it:
<ul>
<li><code>prevPage</code> (object)
<ul>
@@ -421,7 +421,7 @@ <h2>Page transition events</h2>
</dd>
<dt><code>pagebeforehide</code></dt>
- <dd>Triggered on the "fromPage" we are transitioning away from, before the actual transition animation is kicked off. Callbacks for this event will recieve a data object as their 2nd arg. This data object has the following properties on it:
+ <dd>Triggered on the "fromPage" we are transitioning away from, before the actual transition animation is kicked off. Callbacks for this event will receive a data object as their 2nd arg. This data object has the following properties on it:
<ul>
<li><code>nextPage</code> (object)
<ul>
@@ -433,7 +433,7 @@ <h2>Page transition events</h2>
</dd>
<dt><code>pageshow</code></dt>
- <dd>Triggered on the "toPage" after the transition animation has completed. Callbacks for this event will recieve a data object as their 2nd arg. This data object has the following properties on it:
+ <dd>Triggered on the "toPage" after the transition animation has completed. Callbacks for this event will receive a data object as their 2nd arg. This data object has the following properties on it:
<ul>
<li><code>prevPage</code> (object)
<ul>
@@ -444,7 +444,7 @@ <h2>Page transition events</h2>
</dd>
<dt><code>pagehide</code></dt>
- <dd>Triggered on the "fromPage" after the transition animation has completed. Callbacks for this event will recieve a data object as their 2nd arg. This data object has the following properties on it:
+ <dd>Triggered on the "fromPage" after the transition animation has completed. Callbacks for this event will receive a data object as their 2nd arg. This data object has the following properties on it:
<ul>
<li><code>nextPage</code> (object)
<ul>
View
@@ -370,7 +370,7 @@ <h2>Page transition events</h2>
<p>Page transitions are used to animate the change from the current active page (fromPage) to a new page (toPage). Events are triggered before and after these transitions so that observers can be notified whenever pages are shown or hidden. The events triggered are as follows:</p>
<dl>
<dt><code>pagebeforeshow</code></dt>
- <dd>Triggered on the "toPage" we are transitioning to, before the actual transition animation is kicked off. Callbacks for this event will recieve a data object as their 2nd arg. This data object has the following properties on it:
+ <dd>Triggered on the "toPage" we are transitioning to, before the actual transition animation is kicked off. Callbacks for this event will receive a data object as their 2nd arg. This data object has the following properties on it:
<ul>
<li><code>prevPage</code> (object)
<ul>
@@ -381,7 +381,7 @@ <h2>Page transition events</h2>
</dd>
<dt><code>pagebeforehide</code></dt>
- <dd>Triggered on the "fromPage" we are transitioning away from, before the actual transition animation is kicked off. Callbacks for this event will recieve a data object as their 2nd arg. This data object has the following properties on it:
+ <dd>Triggered on the "fromPage" we are transitioning away from, before the actual transition animation is kicked off. Callbacks for this event will receive a data object as their 2nd arg. This data object has the following properties on it:
<ul>
<li><code>nextPage</code> (object)
<ul>
@@ -393,7 +393,7 @@ <h2>Page transition events</h2>
</dd>
<dt><code>pageshow</code></dt>
- <dd>Triggered on the "toPage" after the transition animation has completed. Callbacks for this event will recieve a data object as their 2nd arg. This data object has the following properties on it:
+ <dd>Triggered on the "toPage" after the transition animation has completed. Callbacks for this event will receive a data object as their 2nd arg. This data object has the following properties on it:
<ul>
<li><code>prevPage</code> (object)
<ul>
@@ -404,7 +404,7 @@ <h2>Page transition events</h2>
</dd>
<dt><code>pagehide</code></dt>
- <dd>Triggered on the "fromPage" after the transition animation has completed. Callbacks for this event will recieve a data object as their 2nd arg. This data object has the following properties on it:
+ <dd>Triggered on the "fromPage" after the transition animation has completed. Callbacks for this event will receive a data object as their 2nd arg. This data object has the following properties on it:
<ul>
<li><code>nextPage</code> (object)
<ul>

6 comments on commit db572dc

@jaspermdegroot

This comment has been minimized.

Show comment
Hide comment
@jaspermdegroot

jaspermdegroot Jul 7, 2012

Member

@agcolom - Shouldn't that events-nav.html file be removed? Looks like a deprecated version.

Member

jaspermdegroot replied Jul 7, 2012

@agcolom - Shouldn't that events-nav.html file be removed? Looks like a deprecated version.

@agcolom

This comment has been minimized.

Show comment
Hide comment
@agcolom

agcolom Jul 7, 2012

Member

@ugomobi You probably know more than me on that one. Have you found a page that was pointing to this one? (I haven't but haven't checkd everything)

Member

agcolom replied Jul 7, 2012

@ugomobi You probably know more than me on that one. Have you found a page that was pointing to this one? (I haven't but haven't checkd everything)

@jaspermdegroot

This comment has been minimized.

Show comment
Hide comment
@jaspermdegroot

jaspermdegroot Jul 7, 2012

Member

@agcolom

It's an old version of events.html. I checked and there are no links to that page in the docs. I found it by accident when I did a search for "recieve".

Member

jaspermdegroot replied Jul 7, 2012

@agcolom

It's an old version of events.html. I checked and there are no links to that page in the docs. I found it by accident when I did a search for "recieve".

@MauriceG

This comment has been minimized.

Show comment
Hide comment
@MauriceG

MauriceG Jul 7, 2012

Contributor

Hi!
I've also found that page some weeks ago and left it as is.
It sems it's still under construction.
Take look at the commit history. May @scottjehl or @toddparker know more.
Maurice

Contributor

MauriceG replied Jul 7, 2012

Hi!
I've also found that page some weeks ago and left it as is.
It sems it's still under construction.
Take look at the commit history. May @scottjehl or @toddparker know more.
Maurice

@jaspermdegroot

This comment has been minimized.

Show comment
Hide comment
@jaspermdegroot

jaspermdegroot Jul 7, 2012

Member

@MauriceG - Smart thinking to look at the commit history. It looks like I suggested to remove someone's work in progress :(

Member

jaspermdegroot replied Jul 7, 2012

@MauriceG - Smart thinking to look at the commit history. It looks like I suggested to remove someone's work in progress :(

@jaspermdegroot

This comment has been minimized.

Show comment
Hide comment
@jaspermdegroot

jaspermdegroot Jul 8, 2012

Member

Note: I have cherry-picked this commit into 1.1-stable.

Member

jaspermdegroot replied Jul 8, 2012

Note: I have cherry-picked this commit into 1.1-stable.

Please sign in to comment.