RetailCRM-Mirror/select2
1
0
Fork 0
mirror of synced 2024-11-25 14:26:03 +03:00
Code Issues Projects Releases Wiki Activity

Merge pull request #3041 from minddust/fix-typos

Browse Source 
Fix typos
This commit is contained in:
Kevin Brown 2015-02-13 09:21:16 -05:00
commit d51570e1fe
2 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/announcements-4.0.html
View File

@ -34,7 +34,7 @@ slug: announcements-4.0
</p>
<p>
This release contains many breaking changes, but easy-upgrade pathes have
This release contains many breaking changes, but easy-upgrade paths have
been created as well as helper modules that will allow for backwards
compatibility to be maintained with past versions of Select2. Upgrading
<em>will</em> require you to read the release notes carefully, but the
@ -273,7 +273,7 @@ $("select").select2({
<p>
In past versions of Select2, choices were displayed in the order that
they were selected. In cases where Select2 was used on a
<code>&lt;select&gt;</code> element, the order that the server recieved
<code>&lt;select&gt;</code> element, the order that the server received
the selections did not always match the order that the choices were
displayed, resulting in confusion in situations where the order is
important.
@ -392,7 +392,7 @@ function (ArrayData, Utils) {
<p>
<a href="http://select2.github.io/select2/#data">In the past</a>, any time
you wanted to hook Select2 up to a diferent data source you would be
you wanted to hook Select2 up to a different data source you would be
required to implement custom <code>query</code> and
<code>initSelection</code> methods. This allowed Select2 to determine the
initial selection and the list of results to display, and it would handle

10
docs/options.html
View File

@ -115,7 +115,7 @@ $("select").select2({
<a href="announcements-4.0.html#amd-builds">viewing the 4.0 release notes</a>.
Select2 automatically loads some modules when the adapters are being
automatically constructed, so those who are using Select2 with a custom
AMD build using their own system will need to specify the pathes that are
AMD build using their own system will need to specify the paths that are
generated to the Select2 modules.
</p>
@ -353,7 +353,7 @@ placeholder: {
<tr>
<td>Anything else</td>
<td>
The value of the <code>width</code> option is diretly set as the width of the container.
The value of the <code>width</code> option is directly set as the width of the container.
</td>
</tr>
</tbody>
@ -455,7 +455,7 @@ language: {
<p>
When an option is displayed after it has been selected, it is passed
through a formatting function that determines what is displayed. By
default, the function only retuns the <code>text</code> key of the data
default, the function only returns the <code>text</code> key of the data
object.
</p>
@ -501,7 +501,7 @@ language: {
<p>
When an option is displayed after it has been selected, it is passed
through a formatting function that determines what is displayed. By
default, the function only retuns the <code>text</code> key of the data
default, the function only returns the <code>text</code> key of the data
object.
</p>
@ -867,7 +867,7 @@ matcher: function (params, data) {
displaying the dropdown below the container. Select2 will display above
the container if there is not enough space below the container, but there
is enough space above it. You are also not limited to displaying the
drodown within the parent container, which means Select2 will render
dropdown within the parent container, which means Select2 will render
correctly inside of modals and other small containers.
</p>