1 files changed, 9 insertions, 9 deletions
diff --git a/pelican/content/CoretestHashesNovena.md b/pelican/content/CoretestHashesNovena.md
index fbc40c6..9a8ab57 100644
--- a/pelican/content/CoretestHashesNovena.md
+++ b/pelican/content/CoretestHashesNovena.md
@@ -13,7 +13,7 @@ Cryptech subsystem on a Novena PVT1 development board.
 
 <img src="http://bunniefoo.com/novena/pvt1_release/novena_pvt1e_top_sm.jpg">
 
-It is a small single-board Linux PC, which happens to include a Xilinx [Spartan-6 FPGA]. This, together with the TerasIC [http://trac.cryptech.is/wiki/CoretestHashesC5G Cyclone 5 GX](http://www.xilinx.com/products/silicon-devices/fpga/spartan-6/lx.html), is what we are using to develop and test the Cryptech cores.
+It is a small single-board Linux PC, which happens to include a Xilinx [Spartan-6 FPGA](http://www.xilinx.com/products/silicon-devices/fpga/spartan-6/lx.html). This, together with the TerasIC [Cyclone 5 GX](http://trac.cryptech.is/wiki/CoretestHashesC5G), is what we are using to develop and test the Cryptech cores.
 
 The Novena includes an HDMI adapter and two USB ports, so you can plug in a monitor, keyboard, and mouse, and have a graphical desktop environment. However, I prefer to run it headless, and ssh to it. To ssh to the Novena, you need to know its IP address, which means you need to either statically configure it, or you need to assign it an address in your DHCP server.
 
@@ -41,31 +41,31 @@ of the SHA-1 and SHA-2 hash functions from the host computer via an
 I2C serial bus. The subsystem consists of:
 
 
-- [browser:/core/sha1 sha1]: A HW implementation of the SHA-1 hash function.
+- [sha1](browser:/core/sha1): A HW implementation of the SHA-1 hash function.
 
 
 
-- [browser:/core/sha256 sha256]: A HW implementation of the SHA-256 hash
+- [sha256](browser:/core/sha256): A HW implementation of the SHA-256 hash
 
   function.
 
 
-- [browser:/core/sha512 sha512]: A HW implementation of the SHA-512 hash
+- [sha512](browser:/core/sha512): A HW implementation of the SHA-512 hash
 
   function.
 
 
-- [browser:/core/coretest coretest]: A command parser that accepts read/write
+- [coretest](browser:/core/coretest): A command parser that accepts read/write
 
   commands from a host, executes the commands and sends the response.
 
 
-- [browser:/core/i2c i2c]: A serial interface that connects coretest to the
+- [i2c](browser:/core/i2c): A serial interface that connects coretest to the
 
   host.
 
 
-- [browser:/core/novena novena]: A top-level wrapper that connects all
+- [novena](browser:/core/novena): A top-level wrapper that connects all
 
  the cores, and connects i2c to external pins as well as clk and
  reset. This repo also contains userland software that talks to
@@ -112,7 +112,7 @@ Step-by-step installation:
 
 Well, not quite.  You will need to convince the ISE that you have a license.
 
-On the page [http://www.xilinx.com/products/design-tools/ise-design-suite/ise-webpack.htm](http://www.xilinx.com/products/design-tools/ise-design-suite/ise-webpack.htm) click on the `Licensing Solutions` link.  On the resulting page, expand the section `Obtain a license for Free or Evaluation product`.  To download the ISE Webpack, you should have created an account, so now you can go to the Licensing Site and use that account to create a Certificate Based License.
+On the page [http://www.xilinx.com/products/design-tools/ise-design-suite/ise-webpack.htm] click on the `Licensing Solutions` link.  On the resulting page, expand the section `Obtain a license for Free or Evaluation product`.  To download the ISE Webpack, you should have created an account, so now you can go to the Licensing Site and use that account to create a Certificate Based License.
 
 You do not need to go through the HostID dance, just say Do It.  You will then receive a certificate in email (not an X.509 certificate) which you will be able to use.  Then start the ISE Webpack by issuing the command `ise`.  Go to the Help menu and `Manage Licenses`.  Use the resulting new License Manager window to install the .lic file.  This process is complex and flakey.
 
@@ -217,7 +217,7 @@ The expected build time should be something like 5 and 10 minutes, depending on
 Some measured build times for the design:
 
 
-    - 5,30 minutes on MacbookPro 2013 with tools in 64-bit SUSE Linux in VM
+    - 5,30 minutes on [MacbookPro](MacbookPro.md) 2013 with tools in 64-bit SUSE Linux in VM
     - 9,20 minutes on AMD A10-6800K with tools in Windows 7 in Virtualbox VM with one CPU core and 4 GByte RAM.