From 00db0b1ec06e97453bac9106b243be146fc71ac8 Mon Sep 17 00:00:00 2001 From: Christopher Venning Date: Tue, 16 Jun 2015 16:15:42 -0400 Subject: [PATCH] Fixed typos in doc links --- docs/mithril.component.md | 2 +- docs/mithril.redraw.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/mithril.component.md b/docs/mithril.component.md index 05d5cda6..4e26d0b0 100644 --- a/docs/mithril.component.md +++ b/docs/mithril.component.md @@ -513,7 +513,7 @@ There are a few other technical caveats when nesting components: 1. Nested component views must return either a virtual element or another component. Returning an array, a string, a number, boolean, falsy value, etc will result in an error. -2. Nested components cannot change `m.redraw.strategy` from the controller constructor (but they can from event handlers). It's recommended that you use the [`ctx.retain`](mithril.md#persising-dom-elements-across-route-changes) flag instead of changing the redraw strategy in controller constructors. +2. Nested components cannot change `m.redraw.strategy` from the controller constructor (but they can from event handlers). It's recommended that you use the [`ctx.retain`](mithril.md#persisting-dom-elements-across-route-changes) flag instead of changing the redraw strategy in controller constructors. 3. The root DOM element in a component's view must not be changed during the lifecycle of the component, otherwise undefined behavior will occur. In other words, don't do this: diff --git a/docs/mithril.redraw.md b/docs/mithril.redraw.md index 88ef3f45..ee0f0e51 100644 --- a/docs/mithril.redraw.md +++ b/docs/mithril.redraw.md @@ -126,7 +126,7 @@ Common reasons why one might need to change redraw strategy are: Note that the redraw strategy is a global setting that affects the entire template trees of all components on the page. In order to prevent redraws in *some parts* of an application, but not others, see [subtree directives](mithril.render.md#subtree-directives) -You can also configure individual elements to always be diffed, instead of recreated from scratch (even across route changes), by using the [`ctx.retain` flag](mithril.md#persising-dom-elements-across-route-changes). If you need to persist DOM state across route changes, it's recommended that you use the `ctx.retain` flag instead of `m.redraw.strategy("diff")`. +You can also configure individual elements to always be diffed, instead of recreated from scratch (even across route changes), by using the [`ctx.retain` flag](mithril.md#persisting-dom-elements-across-route-changes). If you need to persist DOM state across route changes, it's recommended that you use the `ctx.retain` flag instead of `m.redraw.strategy("diff")`. ---