From 2a8592e270951763e02b421f18475bb765524e90 Mon Sep 17 00:00:00 2001 From: marionbarker Date: Thu, 25 Apr 2024 16:40:24 -0700 Subject: [PATCH] fix typos --- docs/build/pump.md | 6 +++--- docs/gh-actions/build-dev-browser.md | 2 +- docs/loop-3/omnipod.md | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/build/pump.md b/docs/build/pump.md index 800639ff583..0c93c36552b 100644 --- a/docs/build/pump.md +++ b/docs/build/pump.md @@ -57,7 +57,7 @@ Some pumps may have an “L” or “S” or "R" before the pump region, e.g. a ### Medtronic Pump Firmware -A pump’s firmware is the internal software that runs your pump. Older Medtronic firmware allows the *Loop* app to act as a “remote control” to set temporary basals and report back pump data. Newer firmware disabled that “remote control” access and therefore cannot be used with these DIY closed-loop systems. There is currently no ability to downgrade a pump’s firmware or replace it with older firmware. Before you buy a used pump, make sure the pump firmware is compabible. +A pump’s firmware is the internal software that runs your pump. Older Medtronic firmware allows the *Loop* app to act as a “remote control” to set temporary basal rates and report back pump data. Newer firmware disabled that “remote control” access and therefore cannot be used with these DIY closed-loop systems. There is currently no ability to downgrade a pump’s firmware or replace it with older firmware. Before you buy a used pump, make sure the pump firmware is compabible. !!! note "" @@ -69,7 +69,7 @@ A pump’s firmware is the internal software that runs your pump. Older Medtron + Medtronic Worldwide Veo 554 or 754 --> firmware 2.6A or lower + Medtronic Canadian/Australian Veo 554 or 754 --> firmware 2.7A or lower -To find your pump’s firmware you will need to power it on. If the pump has not been powered on for some time (i.e., has been in storage without a battery for a while), it will run through a start-up count and the firmware version will appear on the bottom right of the pump’s screen. Don’t turn away, as the version number will only be displayed for a little while before the screen moves to other information displays. +To find your pump’s firmware you will need to power it on. If the pump has not been powered on for some time (i.e., has been in storage without a battery for a while), it will run through a start-up count and the firmware version will appear on the bottom right of the pump’s screen. Don’t turn away, as the version number will only be displayed for a little while before the pump moves to other information displays. If the pump has been active recently or has a reservoir installed, follow these steps: @@ -118,7 +118,7 @@ Finding a compatible Medtronic pump is probably the most difficult part for most * [Looping in a time of covid](https://www.facebook.com/groups/1087611668259945/){: target="_blank" } -The most success appears to come from either one-on-one discussions with fellow people with diabetes, your doctors or using apps (Craigslist, NextDoor, LetGo, HelpAround). If you are using Craigslist, you may wish to use an app on your iPhone to make the searching easier. There are apps to search multiple cities at once for your keywords and set up alerts. +The most success appears to come from either one-on-one discussions with people with diabetes, your doctors or using apps (Craigslist, NextDoor, LetGo, HelpAround). If you are using Craigslist, you may wish to use an app on your iPhone to make the searching easier. There are apps to search multiple cities at once for your keywords and set up alerts. ![Craigslist](img/craigslist.png) diff --git a/docs/gh-actions/build-dev-browser.md b/docs/gh-actions/build-dev-browser.md index e36c0a9f65f..a777dc0dd50 100644 --- a/docs/gh-actions/build-dev-browser.md +++ b/docs/gh-actions/build-dev-browser.md @@ -95,7 +95,7 @@ Here is a summary of the extra steps; each step has an associated link. This ass !!! warning "What about the `alive branch`" * Sometimes you get an error about the `alive branch` * It should be created for you automatically if you are building with the `dev branch` **and** you have `workflow` permission added to the `scope` for your *GitHub* `Personal Access Token` - * If necessary, delete the `alive branch` and run the `Build Loop` again + * If necessary, delete the `alive branch` and run the `Build Loop` action again #### Add and Update New `Identifier` diff --git a/docs/loop-3/omnipod.md b/docs/loop-3/omnipod.md index 387768e7b2f..f6ca5b09447 100644 --- a/docs/loop-3/omnipod.md +++ b/docs/loop-3/omnipod.md @@ -26,7 +26,7 @@ You'll see this screen every time you ask Loop to `Pair New Pod`. The Omnipod Common pairing protocol is the same for all pods. The difference is that Omnipod requires a RileyLink compatible device and Omnipod DASH does not. There are also slight differences in some of the text and graphics, e.g., Omnipod DASH uses a blue needle cap and Omnipod has a clear needle cap. -Graphic below shows the Pair Pod screen for Omnipod (first) and Omnipod DASH (right). +Graphic below shows the Pair Pod screen for Omnipod (left) and Omnipod DASH (right). ![pair pod screens for Omnipod and Omnipod DASH](img/loop-3-pair-pod-duo.svg){width="500"} {align="center"}