1 files changed, 17 insertions, 17 deletions
diff --git a/guide/overview.html b/guide/overview.html
index 4e5743f..1c6f842 100644
--- a/guide/overview.html
+++ b/guide/overview.html
@@ -62,26 +62,26 @@ That’s where <span class="emphasis"><em>Asciidoc</em></span> comes in.</p><p>T
 to be separate from source. It will generate HTML, PDF, man pages and
 more from the documentation you write in the <span class="emphasis"><em>doc/src/</em></span> folder in
 your repository.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_running_tests"></a>3.4. Running tests</h2></div></div></div><p>Erlang.mk supports a lot of different testing and static
-analysis tools.</p><p>The <a class="link" href="shell.html" title="Chapter 16. Erlang shell">make shell</a>
-<a class="xref" href="shell.html" title="Chapter 16. Erlang shell">Chapter 16, <em>Erlang shell</em></a> command allows you
+analysis tools.</p><p>The <a class="link" href="shell.html" title="Chapter 17. Erlang shell">make shell</a>
+<a class="xref" href="shell.html" title="Chapter 17. Erlang shell">Chapter 17, <em>Erlang shell</em></a> command allows you
 to test your project manually. You can automate these
-unit tests with <a class="link" href="eunit.html" title="Chapter 17. EUnit">EUnit</a>
-<a class="xref" href="eunit.html" title="Chapter 17. EUnit">Chapter 17, <em>EUnit</em></a> and test
-your entire system with <a class="link" href="ct.html" title="Chapter 18. Common Test">Common Test</a>
-<a class="xref" href="ct.html" title="Chapter 18. Common Test">Chapter 18, <em>Common Test</em></a>.
-<a class="link" href="coverage.html" title="Chapter 19. Code coverage">Code coverage</a>
-<a class="xref" href="coverage.html" title="Chapter 19. Code coverage">Chapter 19, <em>Code coverage</em></a> can of course
+unit tests with <a class="link" href="eunit.html" title="Chapter 18. EUnit">EUnit</a>
+<a class="xref" href="eunit.html" title="Chapter 18. EUnit">Chapter 18, <em>EUnit</em></a> and test
+your entire system with <a class="link" href="ct.html" title="Chapter 19. Common Test">Common Test</a>
+<a class="xref" href="ct.html" title="Chapter 19. Common Test">Chapter 19, <em>Common Test</em></a>.
+<a class="link" href="coverage.html" title="Chapter 20. Code coverage">Code coverage</a>
+<a class="xref" href="coverage.html" title="Chapter 20. Code coverage">Chapter 20, <em>Code coverage</em></a> can of course
 be enabled during tests.</p><p>Erlang.mk comes with features to make your life easier when
-setting up and using <a class="link" href="ci.html" title="Chapter 20. Continuous integration">Continuous integration</a>
-<a class="xref" href="ci.html" title="Chapter 20. Continuous integration">Chapter 20, <em>Continuous integration</em></a>.</p><p>On the static analysis side of things, Erlang.mk comes with
-support for <a class="link" href="dialyzer.html" title="Chapter 21. Dialyzer">Dialyzer</a>
-<a class="xref" href="dialyzer.html" title="Chapter 21. Dialyzer">Chapter 21, <em>Dialyzer</em></a> and <a class="link" href="xref.html" title="Chapter 22. Xref">Xref</a>
-<a class="xref" href="xref.html" title="Chapter 22. Xref">Chapter 22, <em>Xref</em></a>,
+setting up and using <a class="link" href="ci.html" title="Chapter 21. Continuous integration">Continuous integration</a>
+<a class="xref" href="ci.html" title="Chapter 21. Continuous integration">Chapter 21, <em>Continuous integration</em></a>.</p><p>On the static analysis side of things, Erlang.mk comes with
+support for <a class="link" href="dialyzer.html" title="Chapter 22. Dialyzer">Dialyzer</a>
+<a class="xref" href="dialyzer.html" title="Chapter 22. Dialyzer">Chapter 22, <em>Dialyzer</em></a> and <a class="link" href="xref.html" title="Chapter 23. Xref">Xref</a>
+<a class="xref" href="xref.html" title="Chapter 23. Xref">Chapter 23, <em>Xref</em></a>,
 to perform success typing analysis and cross referencing
-of the code.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_need_more"></a>3.5. Need more?</h2></div></div></div><p>Not convinced yet? You can read about <a class="link" href="why.html" title="Chapter 25. Why Erlang.mk">why you should use Erlang.mk</a>
-<a class="xref" href="why.html" title="Chapter 25. Why Erlang.mk">Chapter 25, <em>Why Erlang.mk</em></a>
-and its <a class="link" href="history.html" title="Chapter 26. Short history">history</a>
-<a class="xref" href="history.html" title="Chapter 26. Short history">Chapter 26, <em>Short history</em></a>. And if you’re still not
+of the code.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_need_more"></a>3.5. Need more?</h2></div></div></div><p>Not convinced yet? You can read about <a class="link" href="why.html" title="Chapter 26. Why Erlang.mk">why you should use Erlang.mk</a>
+<a class="xref" href="why.html" title="Chapter 26. Why Erlang.mk">Chapter 26, <em>Why Erlang.mk</em></a>
+and its <a class="link" href="history.html" title="Chapter 27. Short history">history</a>
+<a class="xref" href="history.html" title="Chapter 27. Short history">Chapter 27, <em>Short history</em></a>. And if you’re still not
 convinced after that, it’s OK! The world would be boring if
 everyone agreed on everything all the time.</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="getting_started.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="updating.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div>
 </main>