Skip to content

Commit bcd156a

Browse files
authored
minor typos
1 parent 437a56c commit bcd156a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/0.8/Components.md.hbs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ In many situations, you want to encapsulate behaviour and markup into a single r
55

66
First, you need to **create the component** with {{{createLink 'Ractive.extend()'}}}, which allows you to define a template, initialisation behaviour, default data, and so on. (If you're not familiar with Ractive.extend() you should read that page first.)
77

8-
* [Initiliasation Options](#init)
8+
* [Initialisation Options](#init)
99
* [Binding](#binding)
1010
* [Events](#events)
1111
* [The \{{>content}} Directive](#content)
@@ -18,7 +18,7 @@ Most of the normal Ractive {{{ createLink 'options' 'initialisation options' }}}
1818

1919
### onconstruct *`Function`*
2020

21-
`onconstruct` fires a single time immediately after the instance is created and will be passed all the data that will initialize the particular component.
21+
`onconstruct` fires a single time immediately after the instance is created and will be passed all the data that will initialise the particular component.
2222
This could include setting/changing partials, adding decorators, adding other subcomponents, or anything you would use to initialise a normal Ractive instance.
2323

2424
### onconfig *`Function`*
@@ -110,7 +110,7 @@ Then the resulting output would be
110110
Very complex example for such a simple idea but this could drastically effect you.
111111

112112

113-
init is called after the extended component has been initialized
113+
init is called after the extended component has been initialised
114114

115115
```js
116116
var MyWidget = Ractive.extend({

0 commit comments

Comments
 (0)