fix broken links, these already existed

Author: marionbarker

docs/browser/bb-errors.md

@@ -832,7 +832,7 @@ Make sure you only delete `Match-Secrets`. Do NOT delete the repository of the a
 
 When building Loop, LoopCaregiver, LoopFollow or Trio:
 
-* If you just revoked a [Distrbution Certificate](#revoke-extra-distribution-certificate) - please do not delete your `Match-Secrets`
+* If you just revoked a [Distrbution Certificate](#revoke-distribution-certificate) - please do not delete your `Match-Secrets`
 * Make sure you have `ENABLE_NUKE_CERTS` set to true
 * The next time you try to build, the information in Match-Secrets is used to remove invalid profiles
     * A new Distribution Certificate and new profiles will be generated and your Match-Secrets will be updated

docs/browser/bb-update.md

@@ -461,15 +461,6 @@ Click inside the box under **Test Details**. Insert the text you want to see on
 
 In this example, the branch and commit number are included followed by an indication that this version includes the customizations preferred by this person. Your test details can be as simple as "Use this for Charlie".
 
-!!! tip "Commit Number"
-    If your build includes customizations, your commit number will not match what the developer expects to see if you need to ask for help.
-
-    Use this section [Customization and SHA-1](edit-browser.md#customization-and-sha-1) to determine the SHA-1 before customization.
-
-## No Longer Needed
-
-This section contains the old directions to manually renew certificates. It is no longer needed with the automatic certificate renewal method found in `Loop 3.6.0` and newer versions.
-
 ## Renew Certificate
 
 Manual certificate renewal is not longer required if you added the `Variable` `ENABLE_NUKE_CERTS`. See [Add Variable](prepare-fork.md#add-variable){: target="_blank" }.

docs/build/build-errors.md

@@ -406,13 +406,6 @@ This is very similar to the steps for the WatchApp Entitlements Error but you ne
 ![img/device-support-files.jpg](img/device-support-files.jpg){width="750"}
 {align="center"}
 
-
-### No Such Module 'LoopKit' or Similar Message
-
-**Error Message:** If you see a **Cartfile failure** and several other red errors (in particular saying there is "no such module 'LoopKit'").
-
-**Solution**: Read the [Carthage Error](build-errors.md#carthage-error) section above.
-
 ### Developer License Update (PLA Update)
 
 **Error message:** `The Apple Developer Program License Agreement has been updated,  In order to access certain membership resources, you must accept the latest license agreement`.  

docs/build/xcode-settings.md

@@ -31,8 +31,6 @@ Some people have their macOS privacy settings configured so that *Xcode* does no
 
 Yes, watchOS simulators are required to build Loop. If Xcode asks if you want to download them - say yes. It's slow but you cannot build Loop without the simulator.
 
-*   Refer to [New with Xcode 14](../build/build-errors.md#new-with-xcode-14){: target="_blank" } for more information
-
 ## Command Line Tools
 
 The very first time you open Xcode it may install a package of command line tools. Wait patiently until it finishes.  The command line tools may have installed without asking.

docs/troubleshooting/pod-pairing.md

@@ -100,7 +100,7 @@ Hopefully, your pod pairing continues uneventfully at this point. You'll press t
 
 The DASH pod can be left in the tray and placed right next to the phone. If the first attempt to pair shows the "No pods found" message, place the tray on top of the phone or move the pod a little further away from the phone, then try again.
 
-If you see the [Verbose Message, Hard to Interpret](#verbose-message-hard-to-interpret) Pairing exception message as shown in the link above, you need to toggle Bluetooth on the phone:
+If you see an error message indicating a Bluetooth issue, you need to toggle Bluetooth on the phone:
 
 * In your phone settings, turn off Bluetooth
 * Turn on Bluetooth

docs/version/development.md

@@ -290,7 +290,7 @@ Details that are different:
 
 * The way the code is organized has changed: see [LoopWorkspace](loopworkspace.md){: target="_blank" }
 * The default branch name used to be `master` - but is now `main`
-* `carthage` is no longer used to determine which submodules (frameworks) are pulled in to build Loop (see [LoopWorkspace](#loopworkspace))
+* `carthage` is no longer used to determine which submodules (frameworks) are pulled in to build Loop (see [LoopWorkspace](loopworkspace.md))
 
 The information in this video is still generally useful with the last half focused on automatic-bolus - the automatic-bolus dosing strategy has now been incorporated into <span>*Loop* `main` branch</span>. *Loop* has moved on to using only one stable branch (`main`), with `dev` suggested for developers/testers.
 

docs/version/releases.md

@@ -400,7 +400,7 @@ These features are added:
 This patch release was required for those who build using the *Mac* method.
 
 * There are no changes to app functionality
-* Version 3.2.2 and earlier cannot be built using Xcode 15, see [Cycle Inside Loop](../build/build-errors.md#cycle-inside-loop)
+* Version 3.2.2 and earlier cannot be built using Xcode 15.
 
 ### Loop v3.2.2