8000 Spell checking o_O · DaveStein/api.jqueryui.com@a44e1e8 · GitHub
Skip to content

Commit a44e1e8

Browse files
tjvantolltjvantoll
committed
Spell checking o_O
1 parent 83b2f52 commit a44e1e8

File tree

11 files changed

+14
-14
lines changed

11 files changed

+14
-14
lines changed

‎entries/autocomplete.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77

88
<p>This can be used to choose previously selected values, such as entering tags for articles or entering email addresses from an address book. Autocomplete can also be used to populate associated information, such as entering a city name and getting the zip code.</p>
99

10-
<p>You can pull data in from a local or remote source: Local is good for small data sets, e.g., an address book with 50 entries; remote is necessary for big data sets, such as a database with hundreds or millions of entries to select from. To find out more about customizing the data soure, see the documentation for the <a href="#option-source"><code>source</code></a> option.</p>
10+
<p>You can pull data in from a local or remote source: Local is good for small data sets, e.g., an address book with 50 entries; remote is necessary for big data sets, such as a database with hundreds or millions of entries to select from. To find out more about customizing the data source, see the documentation for the <a href="#option-source"><code>source</code></a> option.</p>
1111

1212
<h3>Keyboard interaction</h3>
1313

‎entries/button.xml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,9 @@
33
<title>Button Widget</title>
44
<desc>Themable buttons and button sets.</desc>
55
<longdesc>
6-
<p>Button enhances standard form elements like buttons, inputs and anchors to themable buttons with appropiate hover and active styles.</p>
6+
<p>Button enhances standard form elements like buttons, inputs and anchors to themeable buttons with appropriate hover and active styles.</p>
77

8-
<p>In addition to basic push buttons, radio buttons and checkboxes (inputs of type radio and checkbox) can be converted to buttons. Their associated label is styled to appear as the button, while the underlying input is updated on click. For the association to work properly, give the input an <code>id</code> attribute, and refer to that in the label's <code>for</code> attribute. Don't nest the input inside the label, as that <a href="http://www.paciellogroup.com/blog/2011/07/html5-accessibility-chops-form-control-labeling/">causes accessbility problems</a>.</p>
8+
<p>In addition to basic push buttons, radio buttons and checkboxes (inputs of type radio and checkbox) can be converted to buttons. Their associated label is styled to appear as the button, while the underlying input is updated on click. For the association to work properly, give the input an <code>id</code> attribute, and refer to that in the label's <code>for</code> attribute. Don't nest the input inside the label, as that <a href="http://www.paciellogroup.com/blog/2011/07/html5-accessibility-chops-form-control-labeling/">causes accessibility problems</a>.</p>
99

1010
<p>In order to group radio buttons, Button also provides an additional widget, called Buttonset. Buttonset is used by selecting a container element (which contains the radio buttons) and calling <code>.buttonset()</code>. Buttonset will also provide visual grouping, and therefore should be used whenever you have a group of buttons. It works by selecting all descendants and applying <code>.button()</code> to them. You can enable and disable a button set, which will enable and disable all contained buttons. Destroying a button set also calls each button's <code>destroy</code> method.</p>
1111

‎entries/dialog.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@
7878
<type name="String" />
7979
</option>
8080
<option name="draggable" default="true" example-value="false">
81-
<desc>If set to <code>true</code>, the dialog will be draggable by the title bar. Requires the <a href="/draggable/">jQuery UI Draggable wiget</a> to be included.</desc>
81+
<desc>If set to <code>true</code>, the dialog will be draggable by the title bar. Requires the <a href="/draggable/">jQuery UI Draggable widget</a> to be included.</desc>
8282
<type name="Boolean" />
8383
</option>
8484
<option name="height" default='"auto"' example-value="400">

‎entries/focusable-selector.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
<signature/>
66
<desc>Selects elements which can be focused.</desc>
77
<longdesc>
8-
<p>Some elements are natively focusable, while others require explictly setting a tab index. In all cases, the element must be visible in order to be focusable.</p>
8+
<p>Some elements are natively focusable, while others require explicitly setting a tab index. In all cases, the element must be visible in order to be focusable.</p>
99

1010
<p>Elements of the following type are focusable if they are not disabled: <code>input</code>, <code>select</code>, <code>textarea</code>, <code>button</code>, and <code>object</code>. Anchors are focusable if they have an <code>href</code> or <code>tabindex</code> attribute. <code>area</code> elements are focusable if they are inside a named map, have an <code>href</code> attribute, and there is a visible image using the map. All other elements are focusable based solely on their <code>tabindex</code> attribute and visibility.</p>
1111

‎entries/fold-effect.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
<desc>The size of the fold in pixels.</desc>
1212
</type>
1313
<type name="String">
14-
<desc>A percentage of the element's dimention, e.g., <code>"50%"</code>.</desc>
14+
<desc>A percentage of the element's dimension, e.g., <code>"50%"</code>.</desc>
1515
</type>
1616
</argument>
1717
<argument name="horizFirst" type="Boolean" default="false">

‎entries/jQuery.widget.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -205,7 +205,7 @@
205205
<type name="String"/>
206206
</argument>
207207
<argument name="delay" type="Number" optional="true">
208-
<desc>The number of milliseconds to wait before invoking the function. Deafults to <code>0</code>.</desc>
208+
<desc>The number of milliseconds to wait before invoking the function. Defaults to <code>0</code>.</desc>
209209
</argument>
210210
</method>
211211
<method name="_hoverable">

‎entries/slide-effect.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
<desc>The direction of the effect. Possible values: <code>"left"</code>, <code>"right"</code>, <code>"up"</code>, <code>"down"</code>.</desc>
88
</argument>
99
<argument name="distance" type="Number" default="element's outerWidth">
10-
<desc>The distance of the effect. Defaults to either the height or width of the elemenet depending on the <code>direction</code> argument. Can be set to any integer less than the width/height of the element.</desc>
10+
<desc>The distance of the effect. Defaults to either the height or width of the element depending on the <code>direction</code> argument. Can be set to any integer less than the width/height of the element.</desc>
1111
</argument>
1212
</arguments>
1313
<example>

‎entries/slider.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@
4242
<option name="range" default="false" example-value='true'>
4343
<desc>Whether the slider represents a range.</desc>
4444
<type name="Boolean">
45-
<desc>If set to <code>true</code>, the slider will detect if you have two handles and create a stylable range element between these two.</desc>
45+
<desc>If set to <code>true</code>, the slider will detect if you have two handles and create a styleable range element between these two.</desc>
4646
</type>
4747
<type name="String">
4848
<desc>Either <code>"min"</code> or <code>"max"</code>. A min range goes from the slider min to one handle. A max range goes from one handle to the slider max.</desc>

‎entries/tabbable-selector.xml‎

-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@
55
<signature/>
66
<desc>Selects elements which the user can focus via tabbing.</desc>
77
<longdesc>
8-
<p>Some elements are natively tabbable, while others require explictly setting a positive tab index. In all cases, the element must be visible in order to be tabbable.</p>
8+
<p>Some elements are natively tabbable, while others require explicitly setting a positive tab index. In all cases, the element must be visible in order to be tabbable.</p>
99

10-
<p>Elements of the following type are tabbale if they do not have a negative tab index and are not disabled: <code>input</code>, <code>select</code>, <code>textarea</code>, <code>button</code>, and <code>object</code>. Anchors are focusable if they have an <code>href</code> or positive <code>tabindex</code> attribute. <code>area</code> elements are focusable if they are inside a named map, have an <code>href</code> attribute, and there is a visible image using the map. All other elements are tabbable based solely on their <code>tabindex</code> attribute and visibility.</p>
10+
<p>Elements of the following type are tabbable if they do not have a negative tab index and are not disabled: <code>input</code>, <code>select</code>, <code>textarea</code>, <code>button</code>, and <code>object</code>. Anchors are focusable if they have an <code>href</code> or positive <code>tabindex</code> attribute. <code>area</code> elements are focusable if they are inside a named map, have an <code>href</code> attribute, and there is a visible image using the map. All other elements are tabbable based solely on their <code>tabindex</code> attribute and visibility.</p>
1111

1212
<p><em>Note: Elements with a negative tab index are <a href="/focusable-selector/"><code>:focusable</code></a>, but not <code>:tabbable</code>.</em></p>
1313
</longdesc>

‎entries/tooltip.xml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,15 +3,15 @@
33
<title>Tooltip Widget</title>
44
<desc>Customizable, themeable tooltips, replacing native tooltips.</desc>
55
<longdesc>
6-
<p>Tooltip replaces native tooltips, making them themable as well as allowing various customizations:</p>
6+
<p>Tooltip replaces native tooltips, making them themeable as well as allowing various customizations:</p>
77

88
<ul>
99
<li>Display other content than just the title, like inline footnotes or extra content retrieved via Ajax.</li>
1010
<li>Customize the positioning, e.g., to center the tooltip above elements.</li>
1111
<li>Add extra styling to customize the appearance, for warning or error fields.</li>
1212
</ul>
1313

14-
<p>A fade animation is used by default to show and hide the tooltip, making the appearance a bit more organic, compared to just toggling the visiblity. This can be customized with the <a href="#option-show"><code>show</code></a> and <a href="#option-hide"><code>hide</code></a> options.</p>
14+
<p>A fade animation is used by default to show and hide the tooltip, making the appearance a bit more organic, compared to just toggling the visibility. This can be customized with the <a href="#option-show"><code>show</code></a> and <a href="#option-hide"><code>hide</code></a> options.</p>
1515

1616
<p>The <a href="#option-items"><code>items</code></a> and <a href="#option-content"><code>content</code></a> options need to stay in-sync. If you change one of them, you need to change the other.</p>
1717

0 commit comments

Comments
 (0)