Docs(entries): Fix typos.

Closes gh-827.

Author: ericcarraway

entries/contents.xml

@@ -50,7 +50,7 @@ $( "p" )
 ]]></html>
   </example>
   <example>
-    <desc>Change the background colour of links inside of an iframe.</desc>
+    <desc>Change the background color of links inside of an iframe.</desc>
     <code><![CDATA[
 $( "#frameDemo" ).contents().find( "a" ).css( "background-color", "#BADA55" );
 ]]></code>

entries/jQuery.ajax.xml

@@ -318,7 +318,7 @@ jqxhr.always(function() {
     <p><strong>As of jQuery 1.5</strong>, jQuery's Ajax implementation includes <a href="/jQuery.ajaxPrefilter/">prefilters</a>, <a href="/jQuery.ajaxTransport/">transports</a>, and converters that allow you to extend Ajax with a great deal of flexibility.</p>
 
     <h4 id="using-converters">Using Converters</h4>
-    <p><code>$.ajax()</code> converters support mapping data types to other data types. If, however, you want to map a custom data type to a known type (e.g <code>json</code>), you must add a correspondance between the response Content-Type and the actual data type using the <code>contents</code> option:</p>
+    <p><code>$.ajax()</code> converters support mapping data types to other data types. If, however, you want to map a custom data type to a known type (e.g <code>json</code>), you must add a correspondence between the response Content-Type and the actual data type using the <code>contents</code> option:</p>
     <pre><code>
 $.ajaxSetup({
   contents: {
@@ -332,7 +332,7 @@ $.ajaxSetup({
   }
 });
     </code></pre>
-    <p>This extra object is necessary because the response Content-Types and data types never have a strict one-to-one correspondance (hence the regular expression).</p>
+    <p>This extra object is necessary because the response Content-Types and data types never have a strict one-to-one correspondence (hence the regular expression).</p>
     <p>To convert from a supported type (e.g <code>text</code>, <code>json</code>) to a custom data type and back again, use another pass-through converter:</p>
     <pre><code>
 $.ajaxSetup({

entries/jQuery.ajaxTransport.xml

@@ -48,7 +48,7 @@ function( status, statusText, responses, headers ) {}
     <ul>
       <li><code>status</code> is the HTTP status code of the response, like  200 for a typical success, or 404 for when the resource is not found.</li>
       <li><code>statusText</code> is the statusText of the response.</li>
-      <li><code>responses</code> (Optional) is An object containing dataType/value that contains the response in all the formats the transport could provide (for instance, a native XMLHttpRequest object would set reponses to <code>{ xml: XMLData, text: textData }</code> for a response that is an XML document)</li>
+      <li><code>responses</code> (Optional) is An object containing dataType/value that contains the response in all the formats the transport could provide (for instance, a native XMLHttpRequest object would set responses to <code>{ xml: XMLData, text: textData }</code> for a response that is an XML document)</li>
       <li><code>headers</code> (Optional) is a string containing all the response headers if the transport has access to them (akin to what <code>XMLHttpRequest.getAllResponseHeaders()</code> would provide).</li>
     </ul>
     <p>Just like prefilters, a transport's factory function can be attached to a specific dataType:</p>

entries/on.xml

@@ -34,7 +34,7 @@
   <longdesc>
     <p>The <code>.on()</code> method attaches event handlers to the currently selected set of elements in the jQuery object. As of jQuery 1.7, the <code>.on()</code> method provides all functionality required for attaching event handlers. For help in converting from older jQuery event methods, see <a href="/bind/"><code>.bind()</code></a>,  <a href="/delegate/"><code>.delegate()</code></a>, and <a href="/live/"><code>.live()</code></a>. To remove events bound with <code>.on()</code>, see <a href="/off/"><code>.off()</code></a>. To attach an event that runs only once and then removes itself, see <a href="/one/"><code>.one()</code></a></p>
     <h2 id="event-names">Event names and namespaces</h2>
-    <p>Any event names can be used for the <code>events</code> argument. jQuery will pass through the browser's standard JavaScript event types, calling the <code>handler</code> function when the browser generates events due to user actions such as <code>click</code>. In addition, the <a href="/trigger/"><code>.trigger()</code></a> method can trigger both standard browser event names and custom event names to call attached handlers. Event names should only contain alphanumerics, underscore, and colon chraracters.</p>
+    <p>Any event names can be used for the <code>events</code> argument. jQuery will pass through the browser's standard JavaScript event types, calling the <code>handler</code> function when the browser generates events due to user actions such as <code>click</code>. In addition, the <a href="/trigger/"><code>.trigger()</code></a> method can trigger both standard browser event names and custom event names to call attached handlers. Event names should only contain alphanumerics, underscore, and colon characters.</p>
     <p>An event name can be qualified by <em>event namespaces</em> that simplify removing or triggering the event. For example, <code>"click.myPlugin.simple"</code> defines both the myPlugin and simple namespaces for this particular click event. A click event handler attached via that string could be removed with <code>.off("click.myPlugin")</code> or <code>.off("click.simple")</code> without disturbing other click handlers attached to the elements. Namespaces are similar to CSS classes in that they are not hierarchical; only one name needs to match. Namespaces beginning with an underscore are reserved for jQuery's use.</p>
     <p>In the second form of <code>.on()</code>, the <code>events</code> argument is a plain object. The keys are strings in the same form as the <code>events</code> argument with space-separated event type names and optional namespaces. The value for each key is a function (or <code>false</code> value) that is used as the <code>handler</code> instead of the final argument to the method. In other respects, the two forms are identical in their behavior as described below.</p>
     <h2 id="direct-and-delegated-events">Direct and delegated events</h2>