Skip to content

Commit 1b6d0c3

Browse files
committed
Remember how to write correct markdown
1 parent fb5b1b5 commit 1b6d0c3

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/configure.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
1. [Mixins](#mixins)
55
1. [Init methods](#init-methods)
66
1. [Ready methods](#ready-methods)
7-
1. [Init vs. Ready](#init-vs-ready)
7+
1. [Init vs. ready methods](#init-vs-ready-methods)
88
1. [Destroy methods](#destroy-methods)
99

1010
After creating a component, wire moves the component through its [lifecycle](concepts.md#component-lifecycle). During the *configure* lifecycle step, you can set properties on the component, and then during the *initialize* step that follows, you can invoke initialization methods to do further configuration, before [connections](connections.md) are made between components.
@@ -171,9 +171,9 @@ define({
171171
});
172172
```
173173

174-
# Init vs. Ready
174+
# Init vs. ready methods
175175

176-
While (init methods)[#init-methods] and (ready methods)[#ready-methods) sound similar (and they are), there is an important difference: their order in the component lifecycle. In short, a component's init methods are executed earlier than its ready methods.
176+
While [init methods](#init-methods) and [ready methods](#ready-methods) sound similar (and they are), there is an important difference: their order in the component lifecycle. In short, a component's init methods are executed earlier than its ready methods.
177177

178178
To be more specific, init methods are executed *before* a component is allowed to be dereferenced--any attempt to dereference it will return a pending promise. This gives a component a chance to setup any necessary state or do any necessary work before any other components are allowed to inject or make connections to it.
179179

0 commit comments

Comments
 (0)