Skip to content

Commit 2bade32

Browse files
committed
fix links
1 parent b1068d2 commit 2bade32

File tree

6 files changed

+12
-12
lines changed

6 files changed

+12
-12
lines changed

docs/build/lf-browser-build.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -194,7 +194,7 @@ Examine the table below for the bundle ID associated with your app.
194194
* If that is already taken, you can add a number, for example, "App Name ABC 123"
195195
* This name is what you see on the App Store Connect list and in the *TestFlight* app
196196
* Once installed on your phone, you will see the actual app name
197-
* You can [Change the App Store Connect Name](../browser/phone-install/#change-the-app-store-connect-name) later if you want
197+
* You can [Change the App Store Connect Name](https://loopkit.github.io/loopdocs/browser/phone-install/#change-the-app-store-connect-name) later if you want
198198
* Select your primary language.
199199
* Choose the bundle ID for your app
200200
* SKU can be anything; for example "123" but must be unique across all your apps, so try 1234 or 12345 depending on how many apps you build with this method

docs/remote/remote-control-loop.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ The bullets below take you to the indicated topics. The configuration step is li
2020

2121
## Use *LoopFollow* *Loop* Remote Control
2222

23-
Once the *LoopFollow* phone is [configured](#configure-for-remote-control), and while the *Loop* phone is handy, test sending Remote Commands. It is good to also have a browser open with the *Nightscout* URL displayed.
23+
Once the *LoopFollow* phone is [configured](#configure-loopfollow-for-remote-control), and while the *Loop* phone is handy, test sending Remote Commands. It is good to also have a browser open with the *Nightscout* URL displayed.
2424

2525
![loopfollow loop remote control choices](img/lf-lrc.png){width="300"}
2626
{align=center}

docs/remote/remote-control-nightscout.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,9 +46,9 @@ Only one override can be active at a time. If one is active, you can cancel it.
4646
## *LoopFollow* & Careportal with the *Trio* App
4747

4848
!!! warning "Important"
49-
The ability for the *Trio* app to be remotely controlled will be **disabled** when `Enable Remote Control` is turned OFF on the *Trio* phone, even if you have given *LoopFollow* your *Nightscout* URL with Careportal access. This is for the protection of the *Trio* user, so that they **always** are the primary controller of their insulin dosing app.
49+
The ability for the *Trio* app to be remotely controlled will be **disabled** when `Enable Remote Control` is turned OFF on the *Trio* phone. This is for the protection of the *Trio* user, so that they **always** are the primary controller of their insulin dosing app.
5050

51-
For more details, see [*Trio* Remote Control](remote-control-overview.md#trio-remote-control){: target="_blank" }.
51+
For more details, see [*Trio* Remote Control](https://triodocs.org/configuration/settings/features/remote-control/#trio-remote-control).
5252

5353
Trio can accept remote commands from *Nightscout* or from *LoopFollow*. There are a variety of options, but the final control of whether remote commands will be enacted rests with the Trio user. They can enable or disable remote control.
5454

docs/remote/remote-control-overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The *Loop* app and the open beta version of the *Trio* app (0.5.x or newer) supp
1515
* Trio 0.6 (or newer) requires LoopFollow 4.0 (or newer)
1616
* Trio 0.5.1.28 (or older) requires LoopFollow 3.2.11 (or older)
1717

18-
See [Trio Remote Control](trio-remote-control.md){: target="_blank" } for more information.
18+
See [Trio Remote Control](remote-control-trio.md){: target="_blank" } for more information.
1919

2020
For Browser Builders:
2121

@@ -38,7 +38,7 @@ The graphic below shows the Remote Settings screen for *LoopFollow*. You must fi
3838
* When following someone running Loop, the options are None or [Loop Remote Control](remote-control-loop.md){: target="_blank" }
3939
* When following someone running Trio, the options are None or:
4040
* Trio 0.5.x and newer: [Trio Remote Control](remote-control-trio.md){: target="_blank" }
41-
* Trio 0.2.x: [Nightscout Remote Control](remote-control-nightscout.md#loopfollow--careportal-with-the-trio-app){: target="_blank" }
41+
* Trio 0.2.x: [Nightscout Remote Control](remote-control-nightscout.md#loopfollow-careportal-with-the-trio-app){: target="_blank" }
4242

4343
![LoopFollow remote options - all types](img/lf-remote-options_3.2.svg){width="600"}
4444
{align="center"}
@@ -172,7 +172,7 @@ If you do not have APNS credentials, you need to create a key and grant it acces
172172
Highlight the filename and choose rename, then add ".txt" after ".p8". In other words, modify `AuthKey_AAAAAAAAAA.p8` to `AuthKey_AAAAAAAAAA.p8.txt` and click on `Use .txt` when questioned.
173173
> ![rename the p8 file](img/apns-rename.png){width=200}
174174
{align=center}
175-
7. Double-click to open the `AuthKey_AAAAAAAAAA.p8.txt` file. It will look similar to the screenshot below. You need to highlight **ALL OF THE CONTENTS** of that file and copy it and then paste it both into your Secrets Reference file and into the row for *LoopFollow* [APNS Key](#apns-key). Yes, *allllll* of the contents.
175+
7. Double-click to open the `AuthKey_AAAAAAAAAA.p8.txt` file. It will look similar to the screenshot below. You need to highlight **ALL OF THE CONTENTS** of that file and copy it and then paste it both into your Secrets Reference file and into the row for *LoopFollow* APNS Key. Yes, *allllll* of the contents.
176176
So, the easiest way is to:
177177
* **Click inside that file**
178178
* Highlight **all** the text, and then
@@ -182,7 +182,7 @@ If you do not have APNS credentials, you need to create a key and grant it acces
182182

183183
> ![img/apns-copy-key.png](img/apns-copy-key.png)
184184
185-
8. The APNS Key ID is the 10-character name embedded in the filename: `AuthKey_AAAAAAAAAA.p8.txt`. You can also see it if you return to Apple Developer's [`Certificates, Identifiers & Profiles`](https://developer.apple.com/account/resources/authkeys/list) as highlighted in this graphic. You copy that APNS Key ID and then paste it both into your Secrets Reference file and into the row for *LoopFollow* [APNS Key ID](#apns-key-id)
185+
8. The APNS Key ID is the 10-character name embedded in the filename: `AuthKey_AAAAAAAAAA.p8.txt`. You can also see it if you return to Apple Developer's [`Certificates, Identifiers & Profiles`](https://developer.apple.com/account/resources/authkeys/list) as highlighted in this graphic. You copy that APNS Key ID and then paste it both into your Secrets Reference file and into the row for *LoopFollow* APNS Key ID.
186186

187187
> ![APNS KEY ID is highlighted by red rectangle](img/apns-key-id.png)
188188

docs/remote/remote-control-trio.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -253,7 +253,7 @@ If you took those steps and still have missing rows, return to [Configure *LoopF
253253
This section covers known troubleshooting issues:
254254

255255
* *Nightscout* not displaying *Trio* data: [Configure for OpenAPS](#configure-for-openaps)
256-
* Was able to select *Trio* Remote Control in *LoopFollow* but it is no longer working: [Stop *Nightscout* access from the *Loop* app](#stop-nightscout-access-from-the-loop-app)
256+
* Was able to select *Trio* Remote Control in *LoopFollow* but it is no longer working: [Stop *Nightscout* access from other apps](#stop-nightscout-uploads-from-other-apps)
257257
* Cannot select *Trio* Remote Control in *LoopFollow*: [Update Profile](#update-profile)
258258

259259
### Configure for OpenAPS
@@ -285,7 +285,7 @@ In addition to this step, you may need to force the profile (from Trio) to uploa
285285
### Update Profile
286286

287287
!!! warning "Must on *Trio* 0.5.x (or newer)"
288-
If you are on *Trio* 0.2.x, you might see the option for *Trio* Remote Control in *LoopFollow* Remote Settings, but you can't use it. See [Use *LoopFollow* *Nightscout* Remote Control](#use-loopfollow-nightscout-remote-control).
288+
If you are on *Trio* 0.2.x, you might see the option for *Trio* Remote Control in *LoopFollow* Remote Settings, but you can't use it. See [Use *LoopFollow* *Nightscout* Remote Control](remote-control-nightscout.md#loopfollow-careportal-with-the-trio-app).
289289

290290
If you were previously running the *Loop* app or the *iAPS* app, [Stop *Nightscout* upload](#stop-nightscout-uploads-from-other-apps) from those apps and then force the profile to update.
291291

docs/setup/lf-setup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ The graphic below shows the display when you tap on the *Dexcom* Settings row.
100100
> The *Dexcom* Share credentials are optional, but can be useful when the *Nightscout* URL is unavailable.
101101
102102
!!! note "Setting up a second device"
103-
With version 4.3 and newer, You can set up a second device by scanning a QR code from another LoopFollow user. See this section [Import/Export Settings](#import-export-settings).
103+
With version 4.3 and newer, You can set up a second device by scanning a QR code from another LoopFollow user. See this section [Import/Export Settings](#importexport-settings).
104104

105105
- - -
106106

@@ -266,7 +266,7 @@ It is still useful for Carplay.
266266

267267
The Contact image trick added with v2.2.8 currently works to provide real-time updates on an Apple Watch.
268268

269-
For more detailed instructions, see [Real-Time Watch Updates using Contact](../)
269+
For more detailed instructions, see [Real-Time Watch Updates using Contact](lf-features.md#real-time-watch-updates-using-contact){: target="_blank" }
270270

271271
- - -
272272

0 commit comments

Comments
 (0)