fix broken links

Author: marionbarker

docs/browser/other-apps.md

@@ -314,7 +314,7 @@ You need to configure a *TestFlight* Internal Testing Group for each app you bui
 * Then after each successful build of the app, group members will get a notification when the new build is transferred to *TestFlight* and is available for use
 * They open the *TestFlight* app on their phone to install the new build
 
-If you need detailed instruction, visit [Configure to Use Browser: *TestFlight* Users Overview](tf-users.md#testflight-users-overview){: target="_blank" }.
+If you need detailed instruction, visit [Configure to Use Browser: *TestFlight* Users Overview](tf-users.md#testflight-overview){: target="_blank" }.
 
 ## Create Certificates
 

docs/operation/algorithm/prediction.md

@@ -6,7 +6,7 @@ $$ BG[t] = Insulin[t] + Carb[t] + RetrospectiveCorrection[t] + Momentum[t] $$
 
 Note that the [Momemtum](#glucose-momentum-effect) term does not just add to the other effects as implied in the simple formula above; it is blended with the other terms as described in more detail in the [Momemtum](#glucose-momentum-effect) section below).
 
-You can see the individual contributions of these effects by tapping on the glucose chart on Loop's main screen to view the  [Predicted Glucose Chart](loop-3/displays-v3.md#predicted-glucose-chart){: target="_blank" }. *Loop* updates this glucose prediction every five minutes when a new CGM value has been received and the pump's status has been updated.
+You can see the individual contributions of these effects by tapping on the glucose chart on Loop's main screen to view the  [Predicted Glucose Chart](../../loop-3/displays-v3.md#predicted-glucose-chart){: target="_blank" }. *Loop* updates this glucose prediction every five minutes when a new CGM value has been received and the pump's status has been updated.
 
 Just a note, this whole page is fairly technical. While perhaps not the most interesting topic for many readers, if you are seeking the detailed view of the *Loop* algorithm this discussion is quite useful. If you want a more surface understanding, the overview, bolus and temporary basal recommendations pages alone are probably sufficient.
 

docs/version/development.md

@@ -18,7 +18,7 @@ This section is provides an overview of changes to dev compared to `Loop 3.4.4`.
 
 These changes in the build process only work when `dev` is your default branch. Once `Loop 3.6.0` is released, these changes will work with the `main` branch.
 
-Automatic certificate generation and renewal requires a `Variable` be added to your organization or your repository. Please see these instructions: [Add Variable](prepare-fork.md#add-variable){: target="_blank" }
+Automatic certificate generation and renewal requires a `Variable` be added to your organization or your repository. Please see these instructions: [Add Variable](../browser/prepare-fork.md#add-variable){: target="_blank" }
 
 ### Loop Updates
 
@@ -101,7 +101,7 @@ To really understand what branches are, we should probably explain a little more
 
 Details that are different:
 
-* The way the code is organized has changed: see [LoopWorkspace](#loopworkspace)
+* 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))