From eca811ec09db5be4892461ad46cd44e904025497 Mon Sep 17 00:00:00 2001 From: Rob Austein Date: Sun, 14 Feb 2021 22:14:27 +0000 Subject: Still more borked links --- pelican/content/AlphaBoardComponents.md | 2 +- pelican/content/DevBridgeBoard.md | 2 +- pelican/content/DisasterRecovery.md | 2 +- pelican/content/ProjectStatus.md | 4 ++-- pelican/content/UpgradeToKSNG.md | 2 +- pelican/content/Upgrading.md | 2 +- 6 files changed, 7 insertions(+), 7 deletions(-) (limited to 'pelican') diff --git a/pelican/content/AlphaBoardComponents.md b/pelican/content/AlphaBoardComponents.md index 614e416..3dfd1fa 100644 --- a/pelican/content/AlphaBoardComponents.md +++ b/pelican/content/AlphaBoardComponents.md @@ -6,7 +6,7 @@ This document contains a list of component level description and requirements fo The document is to be used as a BOM (Bill Of Materials) and PCB design requirement description for discussing with PCB designers on what we want to have designed. -The block diagram for the Alpha board can be seen at: [wiki:Hardware] +The block diagram for the Alpha board can be seen at: [Hardware](Hardware) The Alpha board basically consists of three major sub systems: diff --git a/pelican/content/DevBridgeBoard.md b/pelican/content/DevBridgeBoard.md index baadc97..efef738 100644 --- a/pelican/content/DevBridgeBoard.md +++ b/pelican/content/DevBridgeBoard.md @@ -5,7 +5,7 @@ Modified: 2021-02-14 17:30 # dev-bridge board -In the process of developing the [wiki:AlphaBoardComponents] design, the project has made what is known as the "dev-bridge board". +In the process of developing the [AlphaBoardComponents](AlphaBoardComponents) design, the project has made what is known as the "dev-bridge board". This is a board, 100x70 mm, with about 2/3 of the components intended to be on the Alpha design. What is missing is basically the FPGA and it's supporting circuits. diff --git a/pelican/content/DisasterRecovery.md b/pelican/content/DisasterRecovery.md index 277b2ab..08bfd6f 100644 --- a/pelican/content/DisasterRecovery.md +++ b/pelican/content/DisasterRecovery.md @@ -21,7 +21,7 @@ PIN: ### Recovering from a bad bootloader install Well, now you've done it. You'll need to buy an ST-LINK programmer. -See [wiki:UsingSTLink]. +See [UsingSTLink](UsingSTLink). ## Oh no, I'm locked out of my device diff --git a/pelican/content/ProjectStatus.md b/pelican/content/ProjectStatus.md index 3e468b8..fb59d88 100644 --- a/pelican/content/ProjectStatus.md +++ b/pelican/content/ProjectStatus.md @@ -13,8 +13,8 @@ Date: 2016-12-15 22:44 * AlphaBoardStrategy * AlphaBoardComponents * [Core Git Repository](http://trac.cryptech.is/wiki/GitRepositories/core) -* [wiki:Hardware] -* [wiki:DevBridgeBoard] +* [Hardware](Hardware) +* [DevBridgeBoard](DevBridgeBoard) ## Pilot Project diff --git a/pelican/content/UpgradeToKSNG.md b/pelican/content/UpgradeToKSNG.md index e061fcf..186c6e9 100644 --- a/pelican/content/UpgradeToKSNG.md +++ b/pelican/content/UpgradeToKSNG.md @@ -83,7 +83,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 [[wiki:BinaryPackages]]. +or Homebrew tap configured; if not, see [BinaryPackages](BinaryPackages). ### Installing cryptech-alpha-ksng package using apt-get on Debian or Ubuntu Linux diff --git a/pelican/content/Upgrading.md b/pelican/content/Upgrading.md index fd3ed34..76139c7 100644 --- a/pelican/content/Upgrading.md +++ b/pelican/content/Upgrading.md @@ -49,7 +49,7 @@ your Alpha, see DisasterRecovery. ## Upgrading from 'ksng' A few intrepid users are already testing the 'ksng' development branch, -using the instructions at [wiki:UpgradeToKSNG]. In this case, and with future +using the instructions at [UpgradeToKSNG](UpgradeToKSNG). In this case, and with future upgrades, it it not necessary to either wipe the keystore or upgrade the bootloader. -- cgit v1.2.3