From 354b1a10c1ac7bffb00bf5f5b201ae8f3b64fceb Mon Sep 17 00:00:00 2001 From: suren shrestha Date: Thu, 4 Aug 2016 14:51:14 +0545 Subject: [PATCH] Update render.md --- docs/render.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/render.md b/docs/render.md index 66f131cf..067c1471 100644 --- a/docs/render.md +++ b/docs/render.md @@ -35,7 +35,7 @@ In contrast, traversing a javascript data structure has a much more predictable ### Differences from other API methods -`m.render()` method is internally called by [`m.mount()`](mount.md), [`m.route()`](route.md), [`m.redraw()`](redraw.md) and `[m.request()](request.md)`. It is not called by [`m.prop()`](prop.md) +`m.render()` method is internally called by [`m.mount()`](mount.md), [`m.route()`](route.md), [`m.redraw()`](redraw.md) and [`m.request()`](request.md). It is not called by [`m.prop()`](prop.md) Unlike with `m.mount()` and `m.route()`, a vnode tree rendered via `m.render()` does not auto-redraw in response to view events, `m.redraw()` calls or `m.request()` calls. It is a low level mechanism suitable for library authors who wish to manually control rendering instead of relying on Mithril's built-in auto-redrawing system.