Commit 8f74e736 by Tomas Alabes

Fixed some typos

parent 5e868e42
...@@ -2821,7 +2821,7 @@ define(["eve"], function(eve) { ...@@ -2821,7 +2821,7 @@ define(["eve"], function(eve) {
* Raphael.el * Raphael.el
[ property (object) ] [ property (object) ]
** **
* You can add your own method to elements. This is usefull when you want to hack default functionality or * You can add your own method to elements. This is useful when you want to hack default functionality or
* want to wrap some common transformation or attributes in one method. In difference to canvas methods, * want to wrap some common transformation or attributes in one method. In difference to canvas methods,
* you can redefine element method at any time. Expending element methods wouldn’t affect set. * you can redefine element method at any time. Expending element methods wouldn’t affect set.
> Usage > Usage
...@@ -3068,7 +3068,7 @@ define(["eve"], function(eve) { ...@@ -3068,7 +3068,7 @@ define(["eve"], function(eve) {
* Element.data * Element.data
[ method ] [ method ]
** **
* Adds or retrieves given value asociated with given key. * Adds or retrieves given value associated with given key.
** **
* See also @Element.removeData * See also @Element.removeData
> Parameters > Parameters
...@@ -3177,7 +3177,7 @@ define(["eve"], function(eve) { ...@@ -3177,7 +3177,7 @@ define(["eve"], function(eve) {
- mcontext (object) #optional context for moving handler - mcontext (object) #optional context for moving handler
- scontext (object) #optional context for drag start handler - scontext (object) #optional context for drag start handler
- econtext (object) #optional context for drag end handler - econtext (object) #optional context for drag end handler
* Additionaly following `drag` events will be triggered: `drag.start.<id>` on start, * Additionally following `drag` events will be triggered: `drag.start.<id>` on start,
* `drag.end.<id>` on end and `drag.move.<id>` on every move. When element will be dragged over another element * `drag.end.<id>` on end and `drag.move.<id>` on every move. When element will be dragged over another element
* `drag.over.<id>` will be fired as well. * `drag.over.<id>` will be fired as well.
* *
......
...@@ -1346,7 +1346,7 @@ define(["./raphael.core"], function(R) { ...@@ -1346,7 +1346,7 @@ define(["./raphael.core"], function(R) {
* Paper.renderfix * Paper.renderfix
[ method ] [ method ]
** **
* Fixes the issue of Firefox and IE9 regarding subpixel rendering. If paper is dependant * Fixes the issue of Firefox and IE9 regarding subpixel rendering. If paper is dependent
* on other elements after reflow it could shift half pixel which cause for lines to lost their crispness. * on other elements after reflow it could shift half pixel which cause for lines to lost their crispness.
* This method fixes the issue. * This method fixes the issue.
** **
......
...@@ -2896,7 +2896,7 @@ return /******/ (function(modules) { // webpackBootstrap ...@@ -2896,7 +2896,7 @@ return /******/ (function(modules) { // webpackBootstrap
* Raphael.el * Raphael.el
[ property (object) ] [ property (object) ]
** **
* You can add your own method to elements. This is usefull when you want to hack default functionality or * You can add your own method to elements. This is useful when you want to hack default functionality or
* want to wrap some common transformation or attributes in one method. In difference to canvas methods, * want to wrap some common transformation or attributes in one method. In difference to canvas methods,
* you can redefine element method at any time. Expending element methods wouldn’t affect set. * you can redefine element method at any time. Expending element methods wouldn’t affect set.
> Usage > Usage
...@@ -3143,7 +3143,7 @@ return /******/ (function(modules) { // webpackBootstrap ...@@ -3143,7 +3143,7 @@ return /******/ (function(modules) { // webpackBootstrap
* Element.data * Element.data
[ method ] [ method ]
** **
* Adds or retrieves given value asociated with given key. * Adds or retrieves given value associated with given key.
** **
* See also @Element.removeData * See also @Element.removeData
> Parameters > Parameters
...@@ -3252,7 +3252,7 @@ return /******/ (function(modules) { // webpackBootstrap ...@@ -3252,7 +3252,7 @@ return /******/ (function(modules) { // webpackBootstrap
- mcontext (object) #optional context for moving handler - mcontext (object) #optional context for moving handler
- scontext (object) #optional context for drag start handler - scontext (object) #optional context for drag start handler
- econtext (object) #optional context for drag end handler - econtext (object) #optional context for drag end handler
* Additionaly following `drag` events will be triggered: `drag.start.<id>` on start, * Additionally following `drag` events will be triggered: `drag.start.<id>` on start,
* `drag.end.<id>` on end and `drag.move.<id>` on every move. When element will be dragged over another element * `drag.end.<id>` on end and `drag.move.<id>` on every move. When element will be dragged over another element
* `drag.over.<id>` will be fired as well. * `drag.over.<id>` will be fired as well.
* *
...@@ -7209,7 +7209,7 @@ return /******/ (function(modules) { // webpackBootstrap ...@@ -7209,7 +7209,7 @@ return /******/ (function(modules) { // webpackBootstrap
* Paper.renderfix * Paper.renderfix
[ method ] [ method ]
** **
* Fixes the issue of Firefox and IE9 regarding subpixel rendering. If paper is dependant * Fixes the issue of Firefox and IE9 regarding subpixel rendering. If paper is dependent
* on other elements after reflow it could shift half pixel which cause for lines to lost their crispness. * on other elements after reflow it could shift half pixel which cause for lines to lost their crispness.
* This method fixes the issue. * This method fixes the issue.
** **
......
...@@ -2896,7 +2896,7 @@ return /******/ (function(modules) { // webpackBootstrap ...@@ -2896,7 +2896,7 @@ return /******/ (function(modules) { // webpackBootstrap
* Raphael.el * Raphael.el
[ property (object) ] [ property (object) ]
** **
* You can add your own method to elements. This is usefull when you want to hack default functionality or * You can add your own method to elements. This is useful when you want to hack default functionality or
* want to wrap some common transformation or attributes in one method. In difference to canvas methods, * want to wrap some common transformation or attributes in one method. In difference to canvas methods,
* you can redefine element method at any time. Expending element methods wouldn’t affect set. * you can redefine element method at any time. Expending element methods wouldn’t affect set.
> Usage > Usage
...@@ -3143,7 +3143,7 @@ return /******/ (function(modules) { // webpackBootstrap ...@@ -3143,7 +3143,7 @@ return /******/ (function(modules) { // webpackBootstrap
* Element.data * Element.data
[ method ] [ method ]
** **
* Adds or retrieves given value asociated with given key. * Adds or retrieves given value associated with given key.
** **
* See also @Element.removeData * See also @Element.removeData
> Parameters > Parameters
...@@ -3252,7 +3252,7 @@ return /******/ (function(modules) { // webpackBootstrap ...@@ -3252,7 +3252,7 @@ return /******/ (function(modules) { // webpackBootstrap
- mcontext (object) #optional context for moving handler - mcontext (object) #optional context for moving handler
- scontext (object) #optional context for drag start handler - scontext (object) #optional context for drag start handler
- econtext (object) #optional context for drag end handler - econtext (object) #optional context for drag end handler
* Additionaly following `drag` events will be triggered: `drag.start.<id>` on start, * Additionally following `drag` events will be triggered: `drag.start.<id>` on start,
* `drag.end.<id>` on end and `drag.move.<id>` on every move. When element will be dragged over another element * `drag.end.<id>` on end and `drag.move.<id>` on every move. When element will be dragged over another element
* `drag.over.<id>` will be fired as well. * `drag.over.<id>` will be fired as well.
* *
...@@ -6838,7 +6838,7 @@ return /******/ (function(modules) { // webpackBootstrap ...@@ -6838,7 +6838,7 @@ return /******/ (function(modules) { // webpackBootstrap
* Paper.renderfix * Paper.renderfix
[ method ] [ method ]
** **
* Fixes the issue of Firefox and IE9 regarding subpixel rendering. If paper is dependant * Fixes the issue of Firefox and IE9 regarding subpixel rendering. If paper is dependent
* on other elements after reflow it could shift half pixel which cause for lines to lost their crispness. * on other elements after reflow it could shift half pixel which cause for lines to lost their crispness.
* This method fixes the issue. * This method fixes the issue.
** **
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or sign in to comment