aboutsummaryrefslogtreecommitdiff
path: root/pelican/content/UpgradeToKSNG.md
diff options
context:
space:
mode:
Diffstat (limited to 'pelican/content/UpgradeToKSNG.md')
-rw-r--r--pelican/content/UpgradeToKSNG.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/pelican/content/UpgradeToKSNG.md b/pelican/content/UpgradeToKSNG.md
index c9c6f67..59a3f34 100644
--- a/pelican/content/UpgradeToKSNG.md
+++ b/pelican/content/UpgradeToKSNG.md
@@ -84,7 +84,7 @@ just replace the old package with the new one. Homebrew, on the other
hand, reports the conflict and refuses to proceed until you sort it out.
The following assumes that you already had the Cryptech APT repository
-or Homebrew tap configured; if not, see [BinaryPackages](BinaryPackages).
+or Homebrew tap configured; if not, see [BinaryPackages](BinaryPackages.md).
### Installing cryptech-alpha-ksng package using apt-get on Debian or Ubuntu Linux
@@ -162,7 +162,7 @@ cryptech> masterkey set
If the above procedure somehow goes horribly wrong and bricks your
alpha, you can still recover, but you'll need an ST-LINK programmer.
-There's some discussion of this at [GitRepositories/sw/stm32](GitRepositories/sw/stm32).
+There's some discussion of this at [GitRepositories/sw/stm32](GitRepositories/sw/stm32.md).
Possible sources for the ST-LINK programmer and a suitable cable:
@@ -177,7 +177,7 @@ for it.
The programmer is the important part, you can use any sort of cabling
you like so long as it connects the right pins of the programmer to
-the corresponding pins on the Alpha; the SparkFun cable just happens
+the corresponding pins on the Alpha; the [SparkFun](SparkFun.md) cable just happens
to be a tidy package which matches the relevant SWD headers.
We'll include a more detailed description of the recovery process here