Start adding back links that were lost in translation, updated as appropriate.

This is by no means a complete overhaul, just a fix for the most
obviously broken links in the Installation pages.

3 files changed, 26 insertions, 22 deletions

diff --git a/README.md b/README.md
index 7a0c6d4d..5079eb9e 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@ toolkit under the same BSD-style license, now moved to GitHub.
 ## Documentation
 
 There's a
-[pile of find documentation salvaged from the old wiki](doc/)
+[pile of documentation salvaged from the old wiki](doc/)
 in the doc/ subdirectory: see the README in that directory for details.
 
 Be warned that the existing documentation is for the "old-trunk"
diff --git a/doc/00.RPKI.md b/doc/00.RPKI.md
index 9aae6d0b..b932536d 100644
--- a/doc/00.RPKI.md
+++ b/doc/00.RPKI.md
@@ -3,32 +3,32 @@
 This collection of tools implements both the production (CA) and relying party
 (RP) sides of an RPKI environment.
 
-The Subversion repository for the entire project is available for (read-only)
-anonymous access at <https://subvert-rpki.hactrn.net/>.
-
-If you just want to browse the code you might find the [Trac source code
-browser interface](http://trac.rpki.net/browser/) more convenient.
+Source code for the entire project is available on [GitHub](https://github.com/dragonresearch/rpki.net).
 
 ## Download and Install
 
 Full source code is available, as are binary packages for a few platforms.
 
-See the installation instructions for how to download the code and install it
-once you've downloaded it.
+See the [installation instructions](01.RPKI.Installation.md) for how
+to download the code and install it once you've downloaded it.
 
 ## Relying Party Tools
 
 If you operate routers and want to use RPKI data to help secure them, you
-should look at the relying party tools.
+should look at the [relying party tools](05.RPKI.RP.md).
 
 ## CA Tools
 
 If you control RPKI resources and need an engine let you request certificates,
-issue ROAs, or issue certificates to other entities, you should look at the CA
-tools.
+issue ROAs, or issue certificates to other entities, you should look at the
+[CA tools](11.RPKI.CA.md).
 
 ## Thanks
 
-This work was funded from 2006 through 2008 by [ARIN](http://www.arin.net/),
-in collaboration with the other Regional Internet Registries. Current work is
-funded by [DHS](http://www.dhs.gov/).
+From 2006 through 2008, this work was funded by [ARIN](http://www.arin.net/).
+
+From 2009 through 2016, this work was funded by [DHS](http://www.dhs.gov/).
+
+Special thanks to Michael Elkins, who wrote the web GUI and generally
+served as a second brain and second set of eyeballs on a long list of
+thorny technical problems.
diff --git a/doc/01.RPKI.Installation.md b/doc/01.RPKI.Installation.md
index 87b99829..4af682a3 100644
--- a/doc/01.RPKI.Installation.md
+++ b/doc/01.RPKI.Installation.md
@@ -3,14 +3,17 @@
 There are a few different ways to install the RPKI code, depending on what the
 platform on which you're trying to install.
 
-  * On Ubuntu 12.04 LTS ("Precise Pangolin"), Ubuntu 14.04 ("Trusty Tahir"), or Debian 7 ("Wheezy"), you can use Debian binary packages. 
+## Debian and Ubuntu
 
-## Simple RPKI Cacha Install
+On Ubuntu 16.04 LTS ("Xenial") or Debian 8 ("Jessie"), you can use
+[Debian binary packages](02.RPKI.Installation.DebianPackages.md).
 
-if you want to install a simple RPKI cache to feed routers from a Ubuntu 14.04
+## Simple RPKI Cache Install
+
+If you want to install a simple RPKI cache to feed routers from a Ubuntu 14.04
 system, here is a one page ten minute recipe.
 
-## install a CA and a cache on a Ubuntu 14.04 with a rootd CA
+## Install a CA and a cache on a Ubuntu 14.04 with a rootd CA
 
 If you want to install a CA and a cache on a Ubuntu 14.04 with a rootd CA,
 here is a one page hack. It will take less than an hour.
@@ -23,15 +26,16 @@ CA.
 
 ## FreeBSD
 
-On FreeBSD, you can use FreeBSD ports.
+On FreeBSD, you can use [FreeBSD ports](03.RPKI.Installation.FreeBSDPorts.md).
 
 ## Other Platforms
 
 On all other platforms, or on the above platforms if the pre-packaged versions
-don't suit your needs, you will have to install from source code.
+don't suit your needs, you will have to
+[install from source code](04.RPKI.Installation.FromSource.md).
 
 Once you've finished installing the code, you will need to configure it. Since
 CAs are generally also relying parties (if only so that they can check the
 results of their own actions), you will generally want to start by configuring
-the relying party tools, then configure the CA tools if you're planning to use
-them.
+[the relying party tools](05.RPKI.RP.md), then configure [the CA tools](11.RPKI.CA.md)
+if you're planning to use them.