fix broken links

dndrks · dndrks · commit 9d9e3889ef16 · 2024-01-08T15:25:02.000-05:00
diff --git a/aleph/at1.md b/aleph/at1.md
@@ -10,7 +10,7 @@ permalink: /aleph/tutorial-1/
 
 After Tutorial 0 you may well think ‘this is cool, but i want to <insert cool thing here>’, and that is totally expected and encouraged! This tutorial is aimed to help you build your own network of operators and connect them to a dsp MODULE to do interesting things.
 
-Firstly, it’s probably a good idea to point out that bees is being constantly improved, and it’s good to check you’ve got the most up-to-date version once in a while. Go to the aleph updates page and you’ll see a link to the aleph github with the newest known-working version of bees & all official modules. Instructions for updating are included at that location. The whole process shouldn't take more than 5 minutes.
+Firstly, it’s probably a good idea to point out that bees is being constantly improved, and it’s good to check you’ve got the most up-to-date version once in a while. Go to the aleph updates page and you’ll see a link to the aleph GitHub with the newest known-working version of bees & all official modules. Instructions for updating are included at that location. The whole process shouldn't take more than 5 minutes.
 
 ### Connections
 
diff --git a/aleph/debug.md b/aleph/debug.md
@@ -34,7 +34,7 @@ Attach the output of the debug process above .
 
 ## Tracking Issues
 
-Known issues are logged and tracked via the [Aleph github page](https://github.com/monome/aleph/issues).
+Known issues are logged and tracked via the [Aleph GitHub page](https://github.com/monome/aleph/issues).
 
 See here for a list of known issues and requested improvements.
 
diff --git a/aleph/devapp.md b/aleph/devapp.md
@@ -31,7 +31,7 @@ Download and install AVR Studio from Atmel's site. You will need to sign up for
 
 ## Github
 
-Note that in order to share your creations with the Aleph community you'll need to clone and fork the Aleph github repo. see [Forking](/docs/aleph/forking) for details.
+Note that in order to share your creations with the Aleph community you'll need to clone and fork the Aleph GitHub repo. see [Forking](/docs/aleph/forking) for details.
 
 ## Overview
 
@@ -43,7 +43,7 @@ Creating your own application allows you to radically alter the functionality of
 
 ## app/mix
 
-The code on github is extensively inline commented. Here's a guide to the files:
+The code on GitHub is extensively inline commented. Here's a guide to the files:
 
 ### config.mk
 
diff --git a/aleph/devbees.md b/aleph/devbees.md
@@ -33,7 +33,7 @@ An operator is a control module that can be dynamically created within Bees. It
 
 ### Github
 
-Note that in order to share your creations with the Aleph community you'll need to clone and fork the Aleph github repo. see [Forking](/docs/aleph/forking) for details.
+Note that in order to share your creations with the Aleph community you'll need to clone and fork the Aleph GitHub repo. see [Forking](/docs/aleph/forking) for details.
 
 ## op: FADE
 
diff --git a/aleph/forking.md b/aleph/forking.md
@@ -6,9 +6,9 @@ permalink: /aleph/forking/
 
 # Aleph: Forking
 
-This is an example of how to fork the Aleph repo, change something, and submit a request for your changes to be pulled upstream to monome/aleph. Some naming and workflow conventions are to taste, and `user` is your own github username.
+This is an example of how to fork the Aleph repo, change something, and submit a request for your changes to be pulled upstream to monome/aleph. Some naming and workflow conventions are to taste, and `user` is your own GitHub username.
 
-Create a fork of monome/aleph on github by clicking the “fork” button on the upper right of the repo page. There should now be a new repo on your github page called user/aleph.
+Create a fork of monome/aleph on GitHub by clicking the “fork” button on the upper right of the repo page. There should now be a new repo on your GitHub page called user/aleph.
 
 Now, the terminal commands go something like this:
 
diff --git a/norns/compiling.md b/norns/compiling.md
@@ -73,8 +73,8 @@ code for `maiden` lives [elsewhere](https://github.com/monome/maiden)
 
 the git repository `/home/we/norns` is set up to point at the main
 norns repo on github. by default the copy of the code that's on the
-monome github is nicknamed `origin`. to pull the latest changes on
-github down and merge them into the local copy, we run:
+monome GitHub is nicknamed `origin`. to pull the latest changes on
+GitHub down and merge them into the local copy, we run:
 
 ```bash
 we@norns:~/norns$ git pull origin main
@@ -84,7 +84,7 @@ Already up-to-date.
 we@norns:~/norns$
 ```
 
-if there are a bunch of changes up on github that haven't been pulled
+if there are a bunch of changes up on GitHub that haven't been pulled
 yet, this will show you a summary of changes as well.
 
 we also need to make sure that the submodules are all up to
diff --git a/norns/help/data.md b/norns/help/data.md
@@ -38,16 +38,16 @@ All data that you create with norns -- scripts you've downloaded or created, aud
 
 ### via WiFi
 
-To access the `dust` folder from another computer on the same wifi network, follow the steps in the [wifi + files: transfer](../wifi-files/#transfer) docs.
+To access the `dust` folder from another computer on the same wifi network, follow the steps in the [wifi + files: transfer](/docs/norns/wifi-files/#transfer) docs.
 
-To back up or restore your `dust` folder, follow the steps in the [wifi + files: backup](../wifi-files/#backup) docs.
+To back up or restore your `dust` folder, follow the steps in the [wifi + files: backup](/docs/norns/wifi-files/#backup) docs.
 
 ### via USB
 
 wifi is the most straightforward way to back up your norns. These instructions are provided for times when you are unable to connect norns to wifi (no dongle, no network, etc).
 {: .label}
 
-If you have a standard norns, connect it to a second computer via [serial](../advanced-access/#serial). If you have a shield, host a hotspot for it and connect it to a second computer via [ssh](../advanced-access/#ssh). Then, insert a USB stick into norns.
+If you have a standard norns, connect it to a second computer via [serial](/docs/norns/advanced-access/#serial). If you have a shield, host a hotspot for it and connect it to a second computer via [ssh](/docs/norns/advanced-access/#ssh). Then, insert a USB stick into norns.
 
 - Make sure the USB stick is detected with `ls /media`
 	- you should see `usb` listed, in a different color
@@ -95,10 +95,10 @@ Steps:
   - If you're at this point and running MacOS with [homebrew](https://brew.sh/) installed, try installing `rpiboot` using [these command line instructions](https://github.com/monome/norns-image/blob/main/readme-usbdisk.md#mac-os).  
   - If you're installing for the first time onto a fresh CM3+ using Windows, you'll likely need to install the Raspberry Pi boot drivers and run `rpiboot` before you can image it. Follow [these instructions on the Raspberry Pi site](https://www.raspberrypi.com/documentation/computers/compute-module.html#windows-installer) to make the new CM3+ show up as a USB mass storage device.
 6. Once the flash and validation are complete, disconnect USB. Flip the switch on the norns board back to `run`. Secure the bottom back onto the unit.
-7. Boot norns (if you completed the expansion, it will take a bit longer to start than normal), [add your network](../wifi-files) and [update via SYSTEM  > UPDATE](../wifi-files/#update)
+7. Boot norns (if you completed the expansion, it will take a bit longer to start than normal), [add your network](../wifi-files) and [update via SYSTEM  > UPDATE](/docs/norns/wifi-files/#update)
   - If you perform `SYSTEM > UPDATE` and norns tells you it's `up to date.`, it is! We recommend this step for times when a disk image might not be compiled for an incremental update cycle.
 8. If you have a norns with a 32gb CM3+, you will need to expand the file storage, since the fresh install assumes the lowest capacity (4gb). This only needs to be done once, but it's important after a fresh install -- it lets the system know the capacity of your storage.  
-  - Connect via [SSH](../advanced-access/#ssh) through a terminal.  
+  - Connect via [SSH](/docs/norns/advanced-access/#ssh) through a terminal.  
   - Execute: `sudo raspi-config` (*or* execute: `sudo raspi-config --expand-rootfs; sudo shutdown -r now` to skip to the last step without a GUI)
   - Navigate down to `Advanced Options`.  
   - Select `Expand Filesystem` and select `OK`.  
@@ -109,7 +109,7 @@ Steps:
 
 ### shield {#fresh-shield}
 
-Use [Etcher](https://www.balena.io/Etcher/) or the official [Raspberry Pi Imager](https://www.raspberrypi.com/software/) to flash your SD card, [using these shield-specific instructions](../shield/#flashing-microsd-card). Be sure to use a high quality SD card -- if you have any trouble, please try a different card.
+Use [Etcher](https://www.balena.io/Etcher/) or the official [Raspberry Pi Imager](https://www.raspberrypi.com/software/) to flash your SD card, [using these shield-specific instructions](/docs/norns/shield/#flashing-microsd-card). Be sure to use a high quality SD card -- if you have any trouble, please try a different card.
 
 If Etcher or the Imager do not work for you, or if you prefer to use the command line, see [this guide](https://github.com/monome/norns-image/blob/main/readme-usbdisk.md).
 
@@ -123,7 +123,7 @@ After flashing your SD card, you'll need to expand the filesystem:
 4. Navigate to `Advanced Options` and hit RETURN  
 5. Select `Expand Filesystem` and hit RETURN  
 6. Lots of activity will happen. When it's done, power down and reboot. If you get any errors, reboot again.
-7. [Connect norns to your network](../wifi-files) and [update via SYSTEM  > UPDATE](../wifi-files/#update)
+7. [Connect norns to your network](/docs/norns/wifi-files) and [update via SYSTEM  > UPDATE](/docs/norns/wifi-files/#update)
 8. [Consider changing the default password and address](#change-password)
 
 If you have previously connected to a shield (either by this same IP address or simply `norns.local`) in the past, you may see a warning that the 'remote host identification has changed'. this is because the shield now has a new host key. The error will give you a filepath to your hosts file, but if you are on MacOS you can simply execute `rm -f ~/.ssh/known_hosts` in Terminal to erase the previous hosts file and start fresh.
diff --git a/norns/help/hardware.md b/norns/help/hardware.md
@@ -78,7 +78,7 @@ All standard norns units produced before 2021 have a Compute Module 3 (CM3), wit
 
 ### confirming Compute Module model {#confirm-cm3}
 
-To confirm which chip your norns has installed, [connect via SSH](../advanced-access/#ssh) and execute `pinout`, which will return the name (and a cute illustration!) of your installed Compute Module:
+To confirm which chip your norns has installed, [connect via SSH](/docs/norns//advanced-access/#ssh) and execute `pinout`, which will return the name (and a cute illustration!) of your installed Compute Module:
 
 ![](/docs/norns/image/help-images/pinout.png)
 
@@ -111,7 +111,7 @@ If you are consistently unable to connect your norns to WiFi through the [connec
 
 5. If you are prompted to update the nub's drivers, please do so. Even if there are no updates available, sometimes the simple task of searching for an update resolves connectivity issues. When this process completes, plug the nub back into norns.
 
-6. If norns is still unable to connect to WiFi, connect the power cable to your non-norns computer and follow the `serial` steps outlined [here](../advanced-access/#serial). Once you perform this serial login, try executing `nmtui` for a graphical interface of the WiFi utilities, which may have better luck connecting to a network:
+6. If norns is still unable to connect to WiFi, connect the power cable to your non-norns computer and follow the `serial` steps outlined [here](/docs/norns/advanced-access/#serial). Once you perform this serial login, try executing `nmtui` for a graphical interface of the WiFi utilities, which may have better luck connecting to a network:
    
     ![](/docs/norns/image/terminal-nmtui-main.png)
 
@@ -133,7 +133,7 @@ If you are consistently unable to connect your shield to WiFi through the [conne
 
 1. If your network name has any apostrophes, it might be interpretted as a [*prime*](https://en.wikipedia.org/wiki/Prime_(symbol)), which would cause connection failure. Removing apostrophes from network names has helped resolve most issues with connectivity.
 
-2. Try connecting shield to your router via ethernet and connecting to it from another computer [via SSH](../advanced-access/#ssh).
+2. Try connecting shield to your router via ethernet and connecting to it from another computer [via SSH](/docs/norns/advanced-access/#ssh).
 
 3. In Terminal, execute `nmtui` for a graphical interface of the WiFi utilities, which will provide more information about network connection issues:
    
diff --git a/norns/help/software.md b/norns/help/software.md
@@ -46,7 +46,7 @@ If you have a recurring issue which you believe is hardware or system failure, u
 
 We'll see errors from the running script print to [maiden's REPL](https://monome.org/docs/norns/maiden/#repl). But since maiden only allows us to scroll back through a limited history and occasionally will suppress errors (for example if we're [developing a mod](https://monome.org/docs/norns/community-scripts/#mods)), that sometimes won't be enough.
 
-If we want to see a more encompassing realtime view of error messages from the running script, mods, and SuperCollider, we can log into our our norns directly via [SSH](https://github.com/docs/norns/advanced-access/#ssh) and issue the following command:
+If we want to see a more encompassing realtime view of error messages from the running script, mods, and SuperCollider, we can log into our our norns directly via [SSH](/docs/norns/advanced-access/#ssh) and issue the following command:
 
 ```
 journalctl -f
diff --git a/norns/index.md b/norns/index.md
@@ -103,7 +103,7 @@ Find out more about the current version [at lines](https://l.llllllll.co/norns).
 
 ## contributing
 
-norns is the result of generous contributions by many people, and the ecosystem continues to evolve. We welcome discussion and code to help further the goal of an open, dynamic instrument creation platform. Check out the [github repo](https://github.com/monome/norns). To try out the latest changes to the code, you can read about [compiling norns](../norns/compiling). If you have new functionality you'd like to add, there's also a guide on [extending norns](../norns/extending),
+norns is the result of generous contributions by many people, and the ecosystem continues to evolve. We welcome discussion and code to help further the goal of an open, dynamic instrument creation platform. Check out the [GitHub repo](https://github.com/monome/norns). To try out the latest changes to the code, you can read about [compiling norns](../norns/compiling). If you have new functionality you'd like to add, there's also a guide on [extending norns](../norns/extending).
 
 If your skills include design, instruction, or proofreading, we're also always looking for help with [documentation](https://github.com/monome/docs). Collective efforts have created numerous exceptional projects over the years, and there's more to a project than just code!
 
diff --git a/norns/wifi-files.md b/norns/wifi-files.md
@@ -203,7 +203,7 @@ While you can simply reset this password again via this menu option, we encourag
 
 ### hostname
 
-To change the hostname for maiden access, log in to the norns via [ssh](../advanced-access/#ssh) and execute:
+To change the hostname for maiden access, log in to the norns via [ssh](/docs/norns/advanced-access/#ssh) and execute:
 
 ```
 sudo raspi-config
