Use markdown.

diff --git a/examples/step-1/doc/intro.dox b/examples/step-1/doc/intro.dox
index bc704d07a9d4836074dbf869bd2f1ab4a3355cdd..42a52dff3621875913c06532629cee21e70142be 100644 (file)
--- a/examples/step-1/doc/intro.dox
+++ b/examples/step-1/doc/intro.dox
@@ -186,9 +186,9 @@ are worthwhile browsing through before you start any large-scale programming:
   that has fewer bugs?".
 
 - You will benefit from becoming a better programmer. An excellent
-  resource to this end is the book "<a
-  href="https://en.wikipedia.org/wiki/Code_Complete">Code
-  Complete</a>" by Steve McConnell @code CodeComplete . It's already
+  resource to this end is the book
+  [Code Complete](https://en.wikipedia.org/wiki/Code_Complete)
+  by Steve McConnell @cite CodeComplete . It's already
   a few years old, with the last edition published in 2004, but it has
   lost none of its appeal as a guide to good programming practices,
   and some of the principal developers use it as a group reading