Entries and pages: Replace AJAX with Ajax

Fixes gh-214

Author: Gabriel Schulhof

entries/dialog.xml

@@ -15,7 +15,7 @@
 
 		<p>You can open a dialog programmatically by calling the <a href="/jQuery.mobile.changePage/"><strong>$.mobile.changePage</strong></a> method:</p>
 <pre><code><![CDATA[
-// Dialog loaded via AJAX
+// Dialog loaded via Ajax
 $.mobile.changePage( "path/to/dialog.html", { role: "dialog" } );
 
 // Dialog present in a multipage document

entries/loader.xml

@@ -2,10 +2,10 @@
 <?xml-stylesheet type="text/xsl" href="../entries2html.xsl" ?>
 <entry name="loader" namespace="fn" type="widget" widgetnamespace="mobile" event-prefix="loading">
 	<title>Loader Widget</title>
-	<desc>Handles the task of displaying the loading dialog when jQuery Mobile pulls in content via AJAX. </desc>
+	<desc>Handles the task of displaying the loading dialog when jQuery Mobile pulls in content via Ajax. </desc>
 	<longdesc>
 		<h2>The Loader Widget</h2>
-		<p>The loader widget handles the task of displaying the loading dialog when jQuery Mobile pulls in content via AJAX. It can also be displayed manually for custom loading actions using the <code>$.mobile.loading</code> helper method (See the global method docs).</p>
+		<p>The loader widget handles the task of displaying the loading dialog when jQuery Mobile pulls in content via Ajax. It can also be displayed manually for custom loading actions using the <code>$.mobile.loading</code> helper method (See the global method docs).</p>
 		<p>To configure the loading dialog globally the following settings can be defined on its prototype during the <code>mobileinit</code> event.</p> Below are the defaults:
 
 <pre><code><![CDATA[

entries/pagecontainer.xml

@@ -43,8 +43,8 @@
 ]]></code></pre>
 		<iframe src="/resources/pagecontainer/example1.html" style="width:100%;height:200px;border:0px;"></iframe>
 
-		<h3>HTTP-analogous navigation via AJAX</h3>
-		<p>jQuery Mobile allows you to replace the browser's standard HTTP navigation with AJAX-based navigation. It overrides the browser's default link handling behavior. It intercepts clicks on anchors containing links to other documents and upon each such click it checks whether the document can be retrieved via AJAX. A link has to meet the following criteria in order for the document to which it links to be retrieved via AJAX:
+		<h3>HTTP-analogous navigation via Ajax</h3>
+		<p>jQuery Mobile allows you to replace the browser's standard HTTP navigation with Ajax-based navigation. It overrides the browser's default link handling behavior. It intercepts clicks on anchors containing links to other documents and upon each such click it checks whether the document can be retrieved via Ajax. A link has to meet the following criteria in order for the document to which it links to be retrieved via Ajax:
 			<ol>
 				<li>The global configuration option <code>$.mobile.linkBindingEnabled</code> must be <code>true</code>.</li>
 				<li>The click event's default must not be prevented and it must be a left-click.</li>
@@ -60,10 +60,10 @@
 				<li>The link must be to the same domain or it must be to a permitted cross-domain-request destination.</li>
 			</ol>
 		</p>
-		<p>If these criteria are met jQuery Mobile retrieves the document via AJAX. It is important to realize that, while the document is retrieved in its entirety, only the first jQuery Mobile page is displayed. The header and the rest of the body are discarded. Thus, it is not possible to retrieve a multi-page document via AJAX, nor is it possible to execute scripts located in the header.</p>
+		<p>If these criteria are met jQuery Mobile retrieves the document via Ajax. It is important to realize that, while the document is retrieved in its entirety, only the first jQuery Mobile page is displayed. The header and the rest of the body are discarded. Thus, it is not possible to retrieve a multi-page document via Ajax, nor is it possible to execute scripts located in the header.</p>
 
-		<p>After AJAX retrieval, jQuery Mobile displays the page via a transition. The transition can be specified on the link that opens the page using the <code>data-transition</code> attribute. If no transition is specified, then <code>$.mobile.defaultPageTransition</code> is used or, if the incoming page is a dialog, then <code>$.mobile.defaultDialogTransition</code> is used. <strong>Note: The dialog widget is deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0.</strong></p>
-		<p>If the browser supports the <code>replaceState</code> API the location bar is updated such that it displays the URL of the document that was retrieved via AJAX. This latter step has the following implication for site/application design: Since the user can copy the URL of a page other than the start page, the application must be designed such that it can start from any of its pages. The best way to achieve this is to include jQuery Mobile and your application code in the header for all the pages of the site/application, and ensure initial state consistency during the <code>pagecreate</code> event.</p>
+		<p>After Ajax retrieval, jQuery Mobile displays the page via a transition. The transition can be specified on the link that opens the page using the <code>data-transition</code> attribute. If no transition is specified, then <code>$.mobile.defaultPageTransition</code> is used or, if the incoming page is a dialog, then <code>$.mobile.defaultDialogTransition</code> is used. <strong>Note: The dialog widget is deprecated as of jQuery Mobile 1.4.0 and will be removed in 1.5.0.</strong></p>
+		<p>If the browser supports the <code>replaceState</code> API the location bar is updated such that it displays the URL of the document that was retrieved via Ajax. This latter step has the following implication for site/application design: Since the user can copy the URL of a page other than the start page, the application must be designed such that it can start from any of its pages. The best way to achieve this is to include jQuery Mobile and your application code in the header for all the pages of the site/application, and ensure initial state consistency during the <code>pagecreate</code> event.</p>
 	</longdesc>
 
 	<added>1.4</added>
@@ -423,7 +423,7 @@ $( ":mobile-pagecontainer" ).on( "pagecontainershow", function( event, ui ) {
 					</desc>
 				</property>
 				<property name="data" default="undefined">
-					<desc>The data to send with an AJAX page request.</desc>
+					<desc>The data to send with an Ajax page request.</desc>
 					<type name="Object">
 						<desc></desc>
 					</type>

pages/global-config.html

@@ -78,7 +78,7 @@ <h2>Configurable options</h2>
 	<div class="warning"><strong>Deprecated</strong> in 1.4 - use <code>$.mobile.hoverDelay</code> instead.</dd>
 	<br />
 	<dt id="defaultDialogTransition"><code>defaultDialogTransition</code> <em>string</em>, default: 'pop'</dt>
-	<dd>Set the default transition for dialog changes that use AJAX. Set to 'none' for no transitions.
+	<dd>Set the default transition for dialog changes that use Ajax. Set to 'none' for no transitions.
 	<div class="warning"><strong>Deprecated</strong> in 1.4.</div>
 		<p>When using pages styled as dialogs (<code>data-role="page" data-dialog="true"</code>), if you wish for them to have a different transition than regular pages, you must specify the transition on the link that opens them by adding the attribute <code>data-transition="pop"</code> to the link. "pop" is just an example. You may specify any transition you wish, such as "slide", "flip", or "none".</p>
 		<p>Similarly, when calling the <a href="/pagecontainer/">pagecontainer</a>'s <code>change()</code> method, you must also specify the transition explicitly, if you wish it to be different from the <code>$.mobile.defaultPageTransition</code>: