fixing links

archive/v0.1.5/practices.html

@@ -54,7 +54,7 @@
 <p>This is in stark contrast to the ActiveRecord pattern of other frameworks, where model entities are largely object representations of database entities and these entities are manipulated in controllers in an ad-hoc field-by-field fashion, and the &quot;committed&quot; via a <code>save</code> method.</p>
 <p>Because Mithril encourages all entity logic to be done in the model layer, it&#39;s idiomatic to create modules with model-level classes that deal specifically with relationship between entities, when there isn&#39;t already a model entity that can logically hold the relational business logic.</p>
 <p>Models are also responsible for centralizing tasks such as filtering of entity lists and validation routines, so that access to these methods is available across the application.</p>
-<p>DOM manipulation should be done in the view via <a href="mithril"><code>m()</code> and <code>config</code></a>. Controllers may explicitly call <a href="mithril.redraw"><code>m.redraw</code></a>, but, if possible, it&#39;s preferable to abstract this into a service which integrates w/ Mithril&#39;s auto-redrawing system (see. <a href="mithril.computation"><code>m.startComputation</code> / <code>m.endComputation</code></a>)</p>
+<p>DOM manipulation should be done in the view via <a href="mithril.html"><code>m()</code> and <code>config</code></a>. Controllers may explicitly call <a href="mithril.redraw.html"><code>m.redraw</code></a>, but, if possible, it&#39;s preferable to abstract this into a service which integrates w/ Mithril&#39;s auto-redrawing system (see. <a href="mithril.computation.html"><code>m.startComputation</code> / <code>m.endComputation</code></a>)</p>
 <hr>
 <h2 id="file-separation">File Separation</h2>
 <p>The examples in this site usually conflate different MVC layers together for the sake of readability, but normally it&#39;s recommended that each layer on a module be in different files. For example:</p>