From 8a8829c2e16eeb7b0c49b322372ccace025a0629 Mon Sep 17 00:00:00 2001 From: Ivan Borisenko Date: Tue, 18 Aug 2015 21:42:08 +0300 Subject: [PATCH] Module -> mount rename: fix a documentation link --- docs/routing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/routing.md b/docs/routing.md index cf355319..b85d6610 100644 --- a/docs/routing.md +++ b/docs/routing.md @@ -14,7 +14,7 @@ Mithril provides utilities to handle three different aspect of routing: ### Defining routes -To define a list of routes, you need to specify a host DOM element, a default route and a key-value map of possible routes and respective [modules](mithril.module.md) to be rendered. +To define a list of routes, you need to specify a host DOM element, a default route and a key-value map of possible routes and respective [modules](mithril.mount.md) to be rendered. Note: `module` was renamed to `mount`. Documentation will be updated soon. The example below defines three routes, to be rendered in ``. `home`, `login` and `dashboard` are modules. We'll see how to define a module in a bit. @@ -110,4 +110,4 @@ See [`m()`](mithril.md) for more information on virtual elements. ### Redrawing semantics of routing -By default, changing routes causes templates to be re-rendered from scratch. This behavior can be changed either via the [retain flag in a config's context object](mithril.md#persisting-dom-elements-across-route-changes), or the [`m.redraw.strategy("diff")` hint](mithril.redraw.md#changing-redraw-strategy). \ No newline at end of file +By default, changing routes causes templates to be re-rendered from scratch. This behavior can be changed either via the [retain flag in a config's context object](mithril.md#persisting-dom-elements-across-route-changes), or the [`m.redraw.strategy("diff")` hint](mithril.redraw.md#changing-redraw-strategy).