diff --git a/docs/EN/SettingUpAaps/BuildingAaps.md b/docs/EN/SettingUpAaps/BuildingAaps.md
index dbd1bc16fa71..366ca86628dd 100644
--- a/docs/EN/SettingUpAaps/BuildingAaps.md
+++ b/docs/EN/SettingUpAaps/BuildingAaps.md
@@ -12,7 +12,7 @@ Three methods are available to build the AAPS app:
### Build with a browser (recommended)
-You can build the app with your smartphone using GitHub Actions. From an Android phone, the [AAPS Builder](#aaps-builder) setup page walks you through it, and you start each build yourself. From a computer or an iPhone, you can also build with a fork and save the app in your Google Drive.
+You can build the app in a web browser using GitHub Actions. From an Android phone, the [AAPS Builder](#aaps-builder) setup page walks you through it, and you start each build yourself. From a computer or an iPhone, you can also build with a fork and save the app in your Google Drive.
**[Follow these instructions.](./BrowserBuild.md)**
diff --git a/docs/EN/SettingUpAaps/ChangeAapsConfiguration.md b/docs/EN/SettingUpAaps/ChangeAapsConfiguration.md
index d37a9cc44d46..1a384762df77 100644
--- a/docs/EN/SettingUpAaps/ChangeAapsConfiguration.md
+++ b/docs/EN/SettingUpAaps/ChangeAapsConfiguration.md
@@ -1,4 +1,4 @@
-# Making changes to your AAPS' configuration
+# Making changes to your AAPS configuration
After you have completed the **[Setup Wizard](../SettingUpAaps/SetupWizard.md)**, you don't need to run the entire Wizard again if you want to only change parts of your **AAPS**' configuration.
diff --git a/docs/EN/SettingUpAaps/CompletingTheObjectives.md b/docs/EN/SettingUpAaps/CompletingTheObjectives.md
index 660ba89d76e6..83689406c818 100644
--- a/docs/EN/SettingUpAaps/CompletingTheObjectives.md
+++ b/docs/EN/SettingUpAaps/CompletingTheObjectives.md
@@ -10,7 +10,7 @@ When **AAPS** is installed for the first time, each objective must be completed
**Objectives 1 to 8** will guide you from configuring **AAPS** on your smartphone to “basic” hybrid closed looping. This will take about 6 weeks to complete. You can proceed up to **Objective 5** using a virtual pump (and using some other method of insulin delivery in the meantime). **Objectives 9 and 10** are designed to test more advanced **AAPS** features with the aim of better control of your diabetes, and will take up to 3 months to complete, possibly longer. Further details on an estimated breakdown of time can be obtained here: [How long will it take?](#preparing-how-long-will-it-take)
-As well as progressing through the **Objectives**, if required, you can also remove your progress and [go back to an earlier objective](#go-back-in-objectives).
+As well as progressing through the **Objectives**, if required, you can also remove your progress and [go back to an earlier objective](#CompletingTheObjectives-go-back-in-objectives).
## Backup your settings
@@ -39,7 +39,7 @@ The **Objectives** will need to be restarted from the beginning should you fail
- If using Tidepool:
- Follow instructions in [Tidepool](../SettingUpAaps/Tidepool.md) page to ensure **Tidepool** can receive and display **AAPS** data.
-Note - *You may need to wait for the next sensor glucose reading to arrive before **AAPS** will recognize it.*
+Note: *You may need to wait for the next sensor glucose reading to arrive before **AAPS** will recognize it.*
(objectives-objective2)=
## Objective 2: Learn how to control AAPS
@@ -52,7 +52,7 @@ Each task shows its status (**1**): the orange "**Not completed yet**" turns int
Tasks to complete **Objective 2** are:
- Set your **Profile** to 90% for a duration of 10 min.
- _Hint_: Tap your Profile name on the main screen to open the **Profile** screen, then use the **Activate** (▶) button and set percentage and duration. More information in [Profile switch & Profile Percentage](../DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md).
- - _Note_: **AAPS** does not accept basal rates below 0.05U/hr. If your **Profile** includes rates 0.06U/hr or lower you will need to create a temporary **Profile** with higher basal rates before completing this task. Switch back to your normal **Profile** after completing this task.
+ - _Note_: **AAPS** does not accept basal rates below 0.05U/hr. If your **Profile** includes rates 0.05U/hr or lower you will need to create a temporary **Profile** with higher basal rates before completing this task. Switch back to your normal **Profile** after completing this task.
- Simulate "taking a shower" by [disconnecting your pump](#AapsScreens-loop-status) in **AAPS** for a duration of 1h.
- _Hint_: press the loop icon on the main screen to open the Loop dialog, then choose a duration under **Disconnect pump**.
- End "taking a shower" by reconnecting your pump.
@@ -95,7 +95,7 @@ The minimal time to complete this objective: **7 days**. This is a mandatory wai
- Use [**Temp Targets**](../DailyLifeWithAaps/TempTargets.md) when necessary. After treating a hypo, use the predefined "hypo temp target" to prevent the system from overcorrecting upon the bounce back.
- If you are still in [Simple Mode](#preferences-simple-mode) at this point, now is probably a good time to switch it off.
-To reduce the number of proposed basal rate changes while in Open Loop, you can still use the tips described in [**Objective 3**](#objective-3-prove-your-knowledge).
+To reduce the number of proposed basal rate changes while in Open Loop, you can still use the tips described in [**Objective 3**](#objectives-objective3).
Additionally, you can change the minimum percentage for recommended basal rate changes with the "**Open mode minimum change**" setting in **Settings → Loop**. The higher the value, the fewer change notifications you will receive.
@@ -122,7 +122,7 @@ You might wish to set your [**Profile** BG target](#profile-glucose-targets) hig
```{admonition} If you have been using a virtual pump, change to a real insulin pump now!
:class: note
-If you are open looping with a virtual pump **stop here**. Only click verify at the end of this **Objective** once you have changed to using a "real" pump which delivers insulin.
+If you are open looping with a virtual pump **stop here**. Only tap **Verify** at the end of this **Objective** once you have changed to using a "real" pump which delivers insulin.
```
@@ -170,14 +170,14 @@ Minimal time to complete this objective: **1 day**. This is a mandatory wait tim
- Select **Closed Loop** by pressing the [Loop icon](#AapsScreens-loop-status) on the main screen and choosing **Closed Loop** as running mode. Stay in **Closed Loop** over a period of 1 day.
-- Slowly raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0, until you find the settings that work best for you.
+- Slowly raise your 'Max IOB for SMB' (in OpenAPS called 'max-iob') above 0, until you find the settings that work best for you.
The default recommendation for this setting is “**average meal bolus + 3x max daily basal**”, where “max daily basal” is the maximum hourly value in any time segment of the day.
This recommendation should be seen as a starting point. If you use this rule but are experiencing AAPS delivering too much insulin as glucose levels rise, you may need to :
-* lower the "Maximum total IOB OpenAPS can’t go over" value;
+* lower the "Max IOB for SMB" value;
* review your **Profile** settings, only making one adjustment at a time.
Alternatively, if you are very insulin resistant, raise the **maxIOB** value very cautiously.
@@ -206,7 +206,7 @@ Minimal time to complete this objective: **28 days**. This is a mandatory wait t
- The [SMB section in this documentation](#Open-APS-features-super-micro-bolus-smb) and [oref1 coverage in the openAPS docs](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/oref1.html) are must-reads to understand **SMB** and the concept of **zero-temping**.
- Once done, you can [raise maxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over) to get **SMBs** working more effectively. maxIOB now includes all **IOB**, not just accumulated basal. This threshold pauses **SMBs** until IOB drops below this value (_e.g._ **maxIOB** is set to 7U and a bolus of 8U is given to cover a meal: SMBs will be paused and not given unless **IOB** drops below 7U).
- A good start is setting **maxIOB** = **average meal bolus + 3x max daily basal** where "max daily basal" is the maximum hourly value in any time segment of the day. See [objective 7](#objective-7-tuning-the-closed-loop-raising-maxiob-above-0-and-gradually-lowering-bg-targets) as reference.
+ A good start is setting **maxIOB** = **average meal bolus + 3x max daily basal** where "max daily basal" is the maximum hourly value in any time segment of the day. See [objective 7](#objectives-objective7) as reference.
- Evaluate your carb absorption rate and consider changing the “min_5m_carbimpact”-parameter in [Settings → Absorption settings → min_5m_carbimpact](#Preferences-min_5m_carbimpact) if you find it too slow or too fast.
(objectives-objective10)=
diff --git a/docs/EN/SettingUpAaps/ComputerBuild.md b/docs/EN/SettingUpAaps/ComputerBuild.md
index 6019e9559601..2c380ee5ae2e 100644
--- a/docs/EN/SettingUpAaps/ComputerBuild.md
+++ b/docs/EN/SettingUpAaps/ComputerBuild.md
@@ -110,12 +110,12 @@ Git is a program that allows you to track changes in code and to collaborate wit
(BuildingAaps-steps-for-installing-git)=
#### Steps for Installing Git
-1. Check that you don’t already have **Git** installed. You can do this by typing “git” in the Windows search bar – if you see **“Git bash”** or some other form of Git, it is already installed and you can go straight to [installing Android Studio](#install-android-studio):
+1. Check that you don’t already have **Git** installed. You can do this by typing “git” in the Windows search bar – if you see **“Git bash”** or some other form of Git, it is already installed and you can go straight to [installing Android Studio](#Building-APK-install-android-studio):
-2. If you don’t have Git installed, download and install the latest version for your system from the "Download" section on [**here**](https://git-scm.com/downloads). Any recent Git version should work, select the correct version according to your system, either Mac, Windows and Linux.
+2. If you don’t have Git installed, download and install the latest version for your system from the "Download" section [**here**](https://git-scm.com/downloads). Any recent Git version should work, select the correct version according to your system, either Mac, Windows and Linux.
**Note for Mac users:** the Git webpage will also guide you to install an additional program called "homebrew" to aid the installation. If you install Git via homebrew, there is no need to change any preferences.
@@ -173,7 +173,7 @@ Once it's completed, press "Next"
-In the last step, click on "Finished" to start Android Studio for the first time.
+In the last step, click on "Finish" to start Android Studio for the first time.
@@ -306,7 +306,7 @@ This opens the following window, click to expand the dropdown called **Version C
-Check if **Android Studio** can automatically locate the correct **Path to Git executable** automatically by clicking the button "Test" (1):
+Check if **Android Studio** can automatically locate the correct **Path to Git executable** by clicking the button "Test" (1):
@@ -374,7 +374,7 @@ If you have built AAPS before, do NOT create a new keystore but select your exis
```{admonition} WARNING!
:class: warning
-Make sure to note down for yourself where your keystore is stored. You will need it when you build the next AndroidAPS update!
+Make sure to note down for yourself where your keystore is stored. You will need it when you build the next AAPS update!
```
* Now choose a simple password (and make a note of it), enter it in the password box (2), and confirm it (2).
diff --git a/docs/EN/SettingUpAaps/ConfigBuilder.md b/docs/EN/SettingUpAaps/ConfigBuilder.md
index 19826e5cf77f..2a8373904615 100644
--- a/docs/EN/SettingUpAaps/ConfigBuilder.md
+++ b/docs/EN/SettingUpAaps/ConfigBuilder.md
@@ -73,8 +73,8 @@ In **AAPS** 4 the insulin is no longer a plugin selected in **Configuration**. O
The insulin editor lets you:
-* give the profile an **Insulin nickname** so it is easy to recognise,
-* set the **Peak** (time to maximum insulin activity, in minutes) and the **DIA** (Duration of Insulin Activity, in hours), either by typing the value or using the **–** / **+** buttons,
+* give the insulin an **Insulin nickname** so it is easy to recognise,
+* set the **Peak** (time to maximum insulin activity, in minutes) and the **DIA** (Duration of Insulin Action, in hours), either by typing the value or using the **–** / **+** buttons,
* tap a **Load peak from** preset button — **Novorapid** (75 min), **Fiasp** (55 min) or **Lyumjev** (45 min) — to fill in the standard peak time for that insulin in one step.
The allowed ranges are the same whatever insulin you use:
@@ -282,7 +282,7 @@ When you select another pump, **AAPS** asks you to confirm the change:
* [Equil 5.3](../CompatiblePumps/Equil5.3.md)
* [Carelevo](../CompatiblePumps/CareLevo.md)
* Virtual pump: open loop - **AAPS** suggestions only
- * as you make you first steps with **AAPS**, during the first [objectives](../SettingUpAaps/CompletingTheObjectives.md)
+ * as you make your first steps with **AAPS**, during the first [objectives](../SettingUpAaps/CompletingTheObjectives.md)
* for pump which doesn't have any driver yet
(config-builder-wrong-pump-data)=
@@ -302,7 +302,7 @@ To use the new pump, change the pump driver: select **Virtual pump**, confirm, t
Select the type of sensitivity detection. For more details of different designs please [read on here](../DailyLifeWithAaps/SensitivityDetectionAndCob.md). This will analyze historical data on the go and make adjustments if it recognizes that you are reacting more sensitively (or conversely, more resistant) to insulin than usual. More details about how the sensitivity ratio itself is calculated can be found in [Key AAPS Features > Autosens](#Open-APS-features-autosens).
-You can view your sensitivity on the main screen in an [additional graph](#AapsScreens-section-g-additional-graphs), by selecting SEN and watching the white line. Note, you need to be in [Objective 8](#objectives-objective8) in order to let Sensitivity Detection/[Autosens](#Open-APS-features-autosens) automatically adjust the amount of insulin delivered. Before reaching that objective, the Autosens percentage / the line in your graph is displayed for information only.
+You can view your sensitivity on the main screen in an [additional graph](#AapsScreens-section-g-additional-graphs), by selecting SENS% and watching the white line. Note, you need to be in [Objective 8](#objectives-objective8) in order to let Sensitivity Detection/[Autosens](#Open-APS-features-autosens) automatically adjust the amount of insulin delivered. Before reaching that objective, the Autosens percentage / the line in your graph is displayed for information only.
### Absorption settings
If you use Oref1 with **SMB** you must change **min_5m_carbimpact** to 8. The value is only used during gaps in **CGM** readings or when physical activity "uses up" all the blood glucose rise that would otherwise cause **AAPS** to decay COB. At times when [carb absorption](../DailyLifeWithAaps/CobCalculation.md) can't be dynamically worked out based on your blood's reactions it inserts a default decay to your carbs. Basically, it is a failsafe.
diff --git a/docs/EN/SettingUpAaps/Nightscout.md b/docs/EN/SettingUpAaps/Nightscout.md
index d50e6c4f9722..c0c7b832a4a2 100644
--- a/docs/EN/SettingUpAaps/Nightscout.md
+++ b/docs/EN/SettingUpAaps/Nightscout.md
@@ -29,7 +29,7 @@ Accepting data from Nightscout (profile changes, treatments, ...) is optional an
#### Do not sync from Nightscout
-Keeping all the "Receive ... from NS" options disabled makes sure no Nightscout change will be used by AAPS:
+Keeping all the "Receive … from NS" options disabled makes sure no Nightscout change will be used by AAPS:
diff --git a/docs/EN/SettingUpAaps/Preferences.md b/docs/EN/SettingUpAaps/Preferences.md
index 60c3296c59ed..e0b746674a16 100644
--- a/docs/EN/SettingUpAaps/Preferences.md
+++ b/docs/EN/SettingUpAaps/Preferences.md
@@ -137,7 +137,7 @@ If the app is protected, you must enter the password or use the phone's biometri
- Safety limits are set based on the age you select in this setting.
- If you start hitting these hard limits (like max bolus) it's time to move one step up.
-- It's a bad idea to select higher than real age because it can lead to overdosing by entering the wrong value in the insulin dialog (by skipping the decimal dot, for example).
+- It's a bad idea to select higher than real age because it can lead to overdosing by entering the wrong value in the insulin dialog (by skipping the decimal separator, for example).
- If you want to know the actual numbers for these hard-coded safety limits, scroll to the algorithm feature you are using on [this page](../DailyLifeWithAaps/KeyAapsFeatures.md).
(Preferences-maximum-bolus)=
@@ -280,7 +280,7 @@ Depending on your settings in [Configuration > APS](../SettingUpAaps/ConfigBuild
- [Advanced meal assist (OpenAPS AMA)](#Open-APS-features-advanced-meal-assist-ama) - state of the algorithm in 2017
- [Super Micro Bolus (OpenAPS SMB)](#Open-APS-features-super-micro-bolus-smb) - most recent algorithm recommended for beginners
-As of [**AAPS** version 3.3](#version3300), [Dynamic ISF](../DailyLifeWithAaps/DynamicISF.md) feature has been moved as part of OpenAPS SMB.
+As of [**AAPS** version 3.3](#version3300), the [Dynamic ISF](../DailyLifeWithAaps/DynamicISF.md) feature has been moved into OpenAPS SMB.
### OpenAPS AMA
@@ -496,7 +496,7 @@ You can help develop **AAPS** further by sending crash reports to the developers
**Unattended Settings Export**
By enabling this feature, you allow **AAPS** to execute settings exports without user intervention. For this the master password
-is securely stored on your phone (only) at the next manually export. The stored password will be used for up to 4 weeks.
+is securely stored on your phone (only) at the next manual export. The stored password will be used for up to 4 weeks.
After 4 weeks you will be notified the password is about to expire. During a grace period of 1 week, the password can then be refreshed by
manually exporting settings from the maintenance menu.
diff --git a/docs/EN/SettingUpAaps/SettingUpTheReportingServer.md b/docs/EN/SettingUpAaps/SettingUpTheReportingServer.md
index c3948d633c64..5f60315faec4 100644
--- a/docs/EN/SettingUpAaps/SettingUpTheReportingServer.md
+++ b/docs/EN/SettingUpAaps/SettingUpTheReportingServer.md
@@ -43,7 +43,7 @@ Once you have your Nightscout instance up and running, see [Nightscout configura
Tidepool has been available in **AAPS** since version 3.2 which was released in late 2023.
```{admonition} Tidepool with **AAPS** is only for reporting
-:class: danger
+:class: danger
As there is a delay of three hours between data income and data reporting when using **AAPS**, Tidepool is not suitable for sharing real-time information with caregivers.
On the other hand, Tidepool can be a great solution for sharing reports with a patient's endocrinologist if Nightscout is not an accepted solution.
```
diff --git a/docs/EN/SettingUpAaps/SetupWizard.md b/docs/EN/SettingUpAaps/SetupWizard.md
index 417b415e9497..141782ea8e7d 100644
--- a/docs/EN/SettingUpAaps/SetupWizard.md
+++ b/docs/EN/SettingUpAaps/SetupWizard.md
@@ -122,9 +122,9 @@ Follow these steps on Android 16; other versions will vary slightly from the pro
  
- 1. On Android 12 Click on `Battery`, Android 13+ Click on `App battery usage`,
+ 1. On Android 12 click on `Battery`, on Android 13+ click on `App battery usage`.
- ) 
+  
5. On Android 12+ select the `Unrestricted` option, on Android 15+ you need to expand the `Allow background usage` setting, click on the section highlighted in red to do this then follow step 6 to complete.
@@ -454,7 +454,7 @@ When you select a real pump, **AAPS** asks for a confirmation, because it will c
-If the pump you select communicates over Bluetooth, **AAPS** asks for permission to connect to nearby devices once you finish the Wizard (see [Bluetooth permission](#bluetooth-permission)).
+If the pump you select communicates over Bluetooth, **AAPS** asks for permission to connect to nearby devices once you finish the Wizard (see [Bluetooth permission](#setup-wizard-bluetooth-permission)).
If you have already set up your profile and know how to connect your pump, feel free to connect it now. Otherwise leave it on **Virtual Pump** for the moment — you can change it anytime, or leave the Setup Wizard using the arrow in the top left corner and let **AAPS** first show you some blood glucose values.
@@ -505,7 +505,7 @@ Press "**Open Objectives**":
Here we start Objective 1, even if at the moment our setup is not completely ready to successfully complete this Objective. But this is the start.
-Press the "**Start**" button next to "**1. Objective**":
+Press the "**Start**" button of **Objective 1**:
@@ -521,6 +521,7 @@ After pressing "**FINISH**" you arrive at the main screen of **AAPS**. A "**Noti
If you accidentally leave the Setup Wizard at any point, you can either simply re-start the Wizard, or change the [configuration of the AAPS loop](../SettingUpAaps/ChangeAapsConfiguration.md) manually.
+(setup-wizard-bluetooth-permission)=
## Bluetooth permission
If you select a pump that connects over Bluetooth (for example **Omnipod Dash**), a banner reminds you that **AAPS** needs Bluetooth permission. You can press "**Dismiss**" for now — the permission is granted after you finish the Wizard:
diff --git a/docs/EN/SettingUpAaps/YourAapsProfile.md b/docs/EN/SettingUpAaps/YourAapsProfile.md
index bce711ece7a7..4222ef147043 100644
--- a/docs/EN/SettingUpAaps/YourAapsProfile.md
+++ b/docs/EN/SettingUpAaps/YourAapsProfile.md
@@ -140,9 +140,9 @@ From these examples you can see that the _smaller_ the **ISF** value, the less s
### Impact
-A **lower / stronger ISF** (i.e. 40 instead of 50) means insulin drops your **BG** less per unit. This leads to a more aggressive / stronger correction from the loop with **more insulin**. If your **ISF** is too strong (small value), this can lead to low **BG**.
+A **lower / stronger ISF** (e.g. 40 instead of 50) means insulin drops your **BG** less per unit. This leads to a more aggressive / stronger correction from the loop with **more insulin**. If your **ISF** is too strong (small value), this can lead to low **BG**.
-A **higher / weaker ISF** (i.e. 45 instead of 35) means insulin drops your **BG** more per unit. This leads to a less aggressive / weaker correction from the loop with **less insulin**. If your **ISF** is too weak (large value), this can lead to high **BG**.
+A **higher / weaker ISF** (e.g. 45 instead of 35) means insulin drops your **BG** more per unit. This leads to a less aggressive / weaker correction from the loop with **less insulin**. If your **ISF** is too weak (large value), this can lead to high **BG**.
**Example:**
* **BG** is 190 mg/dL (10.5 mmol/L) and target is 100 mg/dL (5.6 mmol/L).
@@ -207,7 +207,7 @@ It is common to have different **ICR** at different times of day due to hormone
>
> BU factor 2,4 U / 12g ===> IC = 12g / 2,4 U = 5,0 g/U
>
-> Conversion tables are available online i.e. [here](https://www.mylife-diabetescare.com/files/media/03_Documents/11_Software/FAS/SOF_FAS_App_KI-Verha%CC%88ltnis_MSTR-DE-AT-CH.pdf).
+> Conversion tables are available online, e.g. [here](https://www.mylife-diabetescare.com/files/media/03_Documents/11_Software/FAS/SOF_FAS_App_KI-Verha%CC%88ltnis_MSTR-DE-AT-CH.pdf).
### Impact
@@ -307,7 +307,7 @@ Profile helper offers data sets from two different hospitals for children to fin
4. Change to the **Profile 2** tab.
5. Press **Profile type** and select "DPV Default profile".
6. Adjust DPV Default profile (based on another hospital data set) by entering kids age, TDD Total and percentage of basal. Note that the DPV data set provides **basal rates** only, so IC and ISF are shown as zero for this profile.
-7. Open the **Comparation** tab. Comparison of the two adjusted profiles will be displayed (see screenshot below).
+7. Open the **Comparison** tab. Comparison of the two adjusted profiles will be displayed (see screenshot below).
8. If you want to start tweaking your profile based on one of these suggestions, use the **Clone** button at the bottom of the comparison.
@@ -357,6 +357,6 @@ You can also use the [Profile Helper](#aaps-screens-profile-helper) (menu ☰
4. Change to the **Profile 2** tab.
5. In **Profile type**, select "Profile switch" to choose in the history of all your **Profile Switches**.
6. Choose the **Profile Switch** you want to compare to.
-7. Open the **Comparation** tab. Comparison of the two profiles will be displayed (see screenshot below).
+7. Open the **Comparison** tab. Comparison of the two profiles will be displayed (see screenshot below).
diff --git a/docs/EN/SupportingAaps/HowCanIHelp.md b/docs/EN/SupportingAaps/HowCanIHelp.md
index f92face42417..5f535ea8d1f2 100644
--- a/docs/EN/SupportingAaps/HowCanIHelp.md
+++ b/docs/EN/SupportingAaps/HowCanIHelp.md
@@ -23,7 +23,7 @@ If you are translating something for the first time, please start with translati
You are welcome to start as a translator for the documentation in parallel or later.
-You can check the state of translations for the languages app and documentation [here](#StateOfTranslations).
+You can check the state of translations for the languages app and documentation [here](StateOfTranslations.md).
* If you want to translate **the app** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidaps).
* If you want to translate **the docs** to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs).
diff --git a/docs/EN/SupportingAaps/HowToEditTheDocs.md b/docs/EN/SupportingAaps/HowToEditTheDocs.md
index fc617b869e93..7871753aace7 100644
--- a/docs/EN/SupportingAaps/HowToEditTheDocs.md
+++ b/docs/EN/SupportingAaps/HowToEditTheDocs.md
@@ -3,7 +3,7 @@
**This description is just for editing the English documentation. All new information must be added in English first.
If you want to translate to other languages (thank you), please use [crowdin](https://crowdin.com/project/androidapsdocs).**
-For hints how to format text (headline, bold...) and set links please see the ["code syntax"](#code-syntax) section of this page.
+For hints how to format text (headline, bold...) and set links please see the ["code syntax"](#edit-the-docs-code-syntax) section of this page.
## General
@@ -35,11 +35,11 @@ For our example we are going to make an edit to AndroidAPSdocs. This can be done
3. One or the other of the options in Step 2 will create a new branch in YOUR repository where your edits will be saved. Make your edits to the file.
-We are using markdown for the docs pages. The files have the suffix ".md". The Markdown specification is not fixed and we use at the moment the myst_parser for our markdown files. Take care to use the correct syntax as [described below](#code-syntax).
+We are using markdown for the docs pages. The files have the suffix ".md". The Markdown specification is not fixed and we use at the moment the myst_parser for our markdown files. Take care to use the correct syntax as [described below](#edit-the-docs-code-syntax).
-4. You have been working in the "<>Edit file" tab. Select the "Preview changes" tab for a fresh look to make sure everything you changed looks like you meant it to (typos sic.). If you see a needed improvement, go back to the edit tab to make more improvements.
+4. You have been working in the "<>Edit file" tab. Select the "Preview changes" tab for a fresh look to make sure everything you changed looks like you meant it to (check for typos). If you see a needed improvement, go back to the edit tab to make more improvements.
@@ -55,7 +55,7 @@ We are using markdown for the docs pages. The files have the suffix ".md". The M
-PS: Your fork and branch will still be sitting on your own personal GitHub account. After you get a notification that your PR has been merged, you can delete your branch if you are done with it (Step 8's notification area will provide a link to delete the branch once it has been closed or merged). For future edits, if you follow this procedure the edits will always start with an updated version of the AndroidAPSdocs repositories. If you choose to use another method to start a PR request (e.g., editing starting from your forked repo's master branch as the starting point), you will need to ensure your repo is up-to-date by performing a "compare" first and merging in any updates that have happened since you last updated your fork. Since people tend to forget to update their repos, we recommend using the PR process outlined above until you get familiar with performing "compares".
+PS: Your fork and branch will still be sitting on your own personal GitHub account. After you get a notification that your PR has been merged, you can delete your branch if you are done with it (Step 7's notification area will provide a link to delete the branch once it has been closed or merged). For future edits, if you follow this procedure the edits will always start with an updated version of the AndroidAPSdocs repositories. If you choose to use another method to start a PR (e.g., editing starting from your forked repo's master branch as the starting point), you will need to ensure your repo is up-to-date by performing a "compare" first and merging in any updates that have happened since you last updated your fork. Since people tend to forget to update their repos, we recommend using the PR process outlined above until you get familiar with performing "compares".
(edit-the-docs-code-syntax)=
## Code syntax
@@ -68,7 +68,7 @@ The writer only e.g. marks a headline as level 1 headline and the markdown proce
The idea behind this is that
* the writer should think about the text and not the formatting first,
-* the markdown text is open for exchange between different markdown tools instead of e.g. proprietary tools like Microsoft Windows and
+* the markdown text is open for exchange between different markdown tools instead of e.g. proprietary tools like Microsoft Word and
* you can generate several output formats from one markdown file.
Markdown is not a 100% fixed standard and we try to stay as near as possible to the standard, to
@@ -225,7 +225,7 @@ This is a note.
This is a warning.
```
````
-```{admonition} Warning headline
+```{admonition} Warning headline
:class: warning
This is a warning.
```
@@ -256,7 +256,7 @@ without it taking up too much space on the page.
## Tables
-Avoid using tables with long texts as the contents is difficult to set in Markdown, they will usually not fit in a mobile phone screen width, and probably won't display the same after translation.
+Avoid using tables with long texts as the content is difficult to set in Markdown, they will usually not fit in a mobile phone screen width, and probably won't display the same after translation.
## Style Guide
@@ -274,9 +274,9 @@ Avoid using tables with long texts as the contents is difficult to set in Markdo
Use plain English wherever possible. This helps non-native readers and also aids translation of AAPS documents into other languages. Write in a conversational way with the user, imagine you are sitting across the desk from the person you are writing for. Remember - most AAPS users do not have programming backgrounds. Diabetes itself also has a lot of jargon and abbreviations. Bear in mind that some people may be recently diagnosed, may not be as experienced as you with diabetes, or may have been given different diabetes training. If you use shorthand or an abbreviation, write it out in full the first time you use it, giving the abbreviation directly after it in brackets, like “super micro bolus (SMB)”. Also, link to the glossary. Technical terms which might not be familiar to the reader can be also be added in brackets.
-Instead of: *“What causes high postprandial BG peaks in closed loop?"*
+Instead of: *“What causes high postprandial BG peaks in closed loop?”*
-Use: *“What causes a high BG peak **after lunch** (postprandial) in closed loop?"*
+Use: *“What causes a high BG peak **after lunch** (postprandial) in closed loop?”*
##### Use plain words that everyone can understand
@@ -309,7 +309,7 @@ Particularly if you record video or screenshots, make sure not to disclose your
Commands are the fastest way to give instructions, but writers sometimes fear giving commands, writing “you should do this” instead of just “do this”. Perhaps people worry that commands sound too harsh. You can often solve this by putting the word 'please' in front. However, if something must be done, it is best not to say ‘please’ as it gives the reader the option to refuse.
-Instead of: *“You should just think of it as a complete statement."*
+Instead of: *“You should just think of it as a complete statement.”*
Use: *“Think of it as a complete statement.”*
@@ -324,7 +324,7 @@ Example of an **active verb**:
Example of a **passive verb**:
-- *“The insulin (subject) is delivered (verb) by the pump (object)”*
+- *“The insulin (subject) is delivered (verb) by the pump (object).”*
*“delivered”* is a passive verb here. The subject and object are switched around, compared to the active verb sentence. We have had to make the sentence longer by introducing “is” and “by the”. Also consider starting with the active verb.
@@ -475,7 +475,7 @@ A how-to guide’s purpose is to help the already-competent user perform a parti
- HOW-to
-- narrator directly talks to the reader: In this tutorial **you** will
+- narrator directly talks to the reader: In this guide **you** will
- Future Tense -> to show the final target
diff --git a/docs/EN/SupportingAaps/OpenHumans.md b/docs/EN/SupportingAaps/OpenHumans.md
index a8e104f04a65..e46ab2d0c29b 100644
--- a/docs/EN/SupportingAaps/OpenHumans.md
+++ b/docs/EN/SupportingAaps/OpenHumans.md
@@ -2,7 +2,7 @@
## Donate your data for science
-You can help the community by donating your data to research projects! This helps scientists to pay it forward, develop new scientific ideas and broaden the open mind of open source closed loop systems.
+You can help the community by donating your data to research projects! This helps scientists to pay it forward, develop new scientific ideas and make open source closed loop systems better known.
AAPS is ready to synchronize your data with [Open Humans](https://www.openhumans.org), a platform allowing you to upload, connect, and store your personal data – such as genetics, activity and health data.
You retain full control about what happens to your data and what projects you want to support by giving them access to your data. Depending on the project you have joined, data is evaluated and used by them in different ways and extent.
@@ -77,7 +77,7 @@ The screenshot above is from an earlier **AAPS** version. In **AAPS** 4 the conf
The 'OPEN' project brings together an international and intersectoral consortium of patient innovators, clinicians, social scientists, computer scientists and patient advocacy organizations in order to investigate various aspects of Do-it-Yourself Artificial Pancreas Systems (DIY APS) that are used by an increasing number of people with diabetes. For more details see their [website](https://www.open-diabetes.eu/).
-September 2020 the 'OPEN' project launched a [survey](https://survey.open-diabetes.eu/) including the option to donate data you uploaded to Open Humans. A [tutorial](https://open-diabetes.eu/en/open-survey/survey-tutorials/) how to donate your data to the 'OPEN' project is available on their site and within the survey itself.
+In September 2020 the 'OPEN' project launched a [survey](https://survey.open-diabetes.eu/) including the option to donate data you uploaded to Open Humans. A [tutorial](https://open-diabetes.eu/en/open-survey/survey-tutorials/) how to donate your data to the 'OPEN' project is available on their site and within the survey itself.
### [OpenAPS Data Commons](https://www.openhumans.org/activity/openaps-data-commons/)
diff --git a/docs/EN/SupportingAaps/StateOfTranslations.md b/docs/EN/SupportingAaps/StateOfTranslations.md
index 3f5c1ec4fab9..293148e0053b 100644
--- a/docs/EN/SupportingAaps/StateOfTranslations.md
+++ b/docs/EN/SupportingAaps/StateOfTranslations.md
@@ -1,9 +1,9 @@
-# state of translation for app and the documentation
+# State of translation for the app and the documentation
The state is once per hour updated and reflects only the state in Crowdin.
```{tip}
-Be careful the percentage of proofreading must be lower than the percentage of translations but they decided to show it on top of the translations.
+Be careful the percentage of proofreading is always lower than or equal to the percentage of translations but Crowdin shows it on top of the translations.
It's better to look only at the percentage level of translations to see if work is to be done.
```
diff --git a/docs/EN/SupportingAaps/Translations.md b/docs/EN/SupportingAaps/Translations.md
index 6f06b3b339d4..f26e2770c000 100644
--- a/docs/EN/SupportingAaps/Translations.md
+++ b/docs/EN/SupportingAaps/Translations.md
@@ -74,7 +74,7 @@ When a proofreader approves a translation it will be added to the next version o
1. the translation is proofread
- 1. the sync run between Crowdin and Github finished (once an hour) which creates an PR for Github.
+ 1. the sync run between Crowdin and Github finished (once an hour) which creates a PR for GitHub.
1. the PR in Github was approved.
@@ -85,11 +85,11 @@ In general this needs 1 - 3 days but might during holiday take a little bit long
```{admonition} Links are not translated anymore
:class: note
-Links are not translated anymore. In the past we had a topic here but this is gone as through migraton to Markdown and the myst_parser we explicitly create labels in the english text and propagate these labels under the hood to the languages.
+Links are not translated anymore. In the past we had a topic here but this is gone as through migration to Markdown and the myst_parser we explicitly create labels in the english text and propagate these labels under the hood to the languages.
```
-You are translating the text which represents the link. Please you have to be careful **not** to remove the link which is represented by a pair of `<0>` tags or if their are more in one paragraph other numbers.
+You are translating the text which represents the link. Please be careful **not** to remove the link, which is represented by a pair of `<0>` tags (or other numbers, if there are more links in one paragraph).
It's the proofreaders job to have a special look on this!
diff --git a/docs/EN/UsefulLinks/ClinicianGuideToAaps.md b/docs/EN/UsefulLinks/ClinicianGuideToAaps.md
index 8ceb0c7a0c5f..5db2a2bcb067 100644
--- a/docs/EN/UsefulLinks/ClinicianGuideToAaps.md
+++ b/docs/EN/UsefulLinks/ClinicianGuideToAaps.md
@@ -21,7 +21,7 @@ Without a closed loop system, a person with diabetes gathers data from their pum
With automated insulin delivery, the system does the same thing: it gathers data from the pump, CGM, and anywhere else information is logged (such as Nightscout), uses this information to do the maths and decide how much more or less insulin is needed (above or below the underlying basal rate), and uses temporary basal rates to make the necessary adjustments to keep or eventually bring BGs into target range.
-If the device running AAPS breaks or goes out of range of the pump, once the latest temporary basal rate ends, the pump falls back to being a standard pump with the preprogrammed basals rates running.
+If the device running AAPS breaks or goes out of range of the pump, once the latest temporary basal rate ends, the pump falls back to being a standard pump with the preprogrammed basal rates running.
## How data is gathered:
@@ -37,7 +37,7 @@ It will also gather any information about boluses, carbohydrate consumption, and
## How does it know what to do?
-The open source software is designed to make it easy for the device to do the work people used to do (in manual mode) to calculate how insulin delivery should be adjusted. It first collects data from all the supporting devices and from the cloud, prepares the data and runs the calculations, makes predictions of expected BG-levels during the next hours will be expected to do in different scenarios, and calculates the needed adjustments to keep or bring BG back into target range. Next it sends any necessary adjustments to the pump. Then it reads the data back, and does it over and over again.
+The open source software is designed to make it easy for the device to do the work people used to do (in manual mode) to calculate how insulin delivery should be adjusted. It first collects data from all the supporting devices and from the cloud, prepares the data and runs the calculations, makes predictions of what BG levels are expected to do during the next hours in different scenarios, and calculates the needed adjustments to keep or bring BG back into target range. Next it sends any necessary adjustments to the pump. Then it reads the data back, and does it over and over again.
As the most important input parameter is the blood glucose level coming from the CGM, it is important to have high-quality CGM data.
@@ -68,7 +68,7 @@ In this example, BG is predicted to go low in the near-term, but is predicted to
### Scenario 3 - More insulin needed
-In this example, a near-term prediction shows a dip below target. However, it is not predicted to be below the safety threshold. The eventual BG is above target. Therefore, AAPS will restrain from adding any insulin that would contribute to a near-term low (by adding insulin that would make the prediction go below threshold). It will then assess adding insulin to bring the lowest level of the eventual predicted BG down to target, once it is safe to do so. *(Depending on settings and the amount and timing of insulin required, this insulin may be delivered via temp basals or SMB's (super micro boluses) ).*
+In this example, a near-term prediction shows a dip below target. However, it is not predicted to be below the safety threshold. The eventual BG is above target. Therefore, AAPS will refrain from adding any insulin that would contribute to a near-term low (by adding insulin that would make the prediction go below threshold). It will then assess adding insulin to bring the lowest level of the eventual predicted BG down to target, once it is safe to do so. *(Depending on settings and the amount and timing of insulin required, this insulin may be delivered via temp basals or SMBs (super micro boluses)).*
@@ -84,13 +84,13 @@ As a clinician who may not have experience with AAPS or DIY closed loops, you ma
The most important thing for patients to do is make one change at a time, and observe the impact for 2-3 days before choosing to change or modify another setting (unless it’s obviously a bad change that makes things worse, in which case they should revert immediately to the previous setting). The human tendency is to turn all the knobs and change everything at once; but if someone does so, then they may end up with further sub-optimal settings for the future, and find it hard to get back to a known good state.
-One of the most powerful tools for making settings changes is an automated calculation tool for basal rates, ISF, and carb ratio. This is called “[Autotune](#autotune-how-autotune-calculates-adjustments)”. It is designed to be run independently/manually, and allow the data to guide you or your patient in making incremental changes to settings. It is best practice in the community to run (or review) Autotune reports first, prior to attempting to make manual adjustments to settings. Autotune is built into AAPS as a plugin (**Configuration** → **General** → **Autotune**); see [Autotune](../AdvancedOptions/Autotune.md). It can be run on demand or automatically.
+One of the most powerful tools for making settings changes is an automated calculation tool for basal rates, ISF, and carb ratio. This is called “[Autotune](#autotune-how-autotune-calculates-adjustments)”. It is designed to allow the data to guide you or your patient in making incremental changes to settings. It is best practice in the community to run (or review) Autotune reports first, prior to attempting to make manual adjustments to settings. Autotune is built into AAPS as a plugin (**Configuration** → **General** → **Autotune**); see [Autotune](../AdvancedOptions/Autotune.md). It can be run on demand or automatically.
As these parameters are a prerequisite both for standard pump insulin delivery and for closed loop insulin delivery, discussion of the autotune results and adjustment of these parameters would be the natural link to the clinician.
Additionally, human behavior (learned from manual diabetes mode) often influences outcomes, even with a DIY closed loop. For example, if BG is predicted to go low and AAPS reduces insulin on the way down, only a small amount of carbs (e.g. 3-4g carbs) may be needed to bring BG up from 70 mg/dL (3.9 mmol/L). However, in many cases, someone may choose to treat with many more carbs (e.g. sticking to the 15 rule), which will cause a resulting faster spike both from the extra glucose and because insulin had been reduced in the timeframe leading up to the low.
## OpenAPS
-**This guide was adopted from [The clinician's guide to OpenAPS](https://openaps.readthedocs.io/en/latest/docs/Resources/clinician-guide-to-OpenAPS.html).**
+**This guide was adapted from [The clinician's guide to OpenAPS](https://openaps.readthedocs.io/en/latest/docs/Resources/clinician-guide-to-OpenAPS.html).**
OpenAPS is a system developed to be run on a small portable computer (generally referred to as the "rig").
AAPS uses many of the techniques implemented in OpenAPS, and shares much of the logic and algorithms, which is why this guide is very similar to the original guide.
Much of the information about OpenAPS can be easily adapted to AAPS, with the main difference being the hardware platform where each piece of software is run.
diff --git a/docs/EN/UsefulLinks/DedicatedGoogleAccountForAaps.md b/docs/EN/UsefulLinks/DedicatedGoogleAccountForAaps.md
index 693bb20915cd..ee477b8f2015 100644
--- a/docs/EN/UsefulLinks/DedicatedGoogleAccountForAaps.md
+++ b/docs/EN/UsefulLinks/DedicatedGoogleAccountForAaps.md
@@ -7,7 +7,7 @@ If you don't want to set up an **AAPS**-dedicated Gmail account, you can just go
```{admonition} Advantages of a dedicated Google account for AAPS
:class: dropdown
-- Dedicated Google drive space means you will not risk filling up your personal Google drive limit with **Export Preferences**.
+- Dedicated Google Drive space means you will not risk filling up your personal Google Drive limit with **Export settings**.
- Each version of **AAPS** (and supporting apps like xDrip, BYODA, etc) will be stored in one single place which is independent of your computer hardware. If your PC or phone is stolen/lost/broken you will still have access.
- By harmonizing the setup, it will make online support simpler across users with similar folder structure.
- Depending on the setup (see below), you will have a separate identity as an alias to communicate within the community which can protect your privacy.
@@ -45,14 +45,14 @@ Click [here]( ; 
+- Your existing “_Everyday_” Google account is ; 
- Your new “_AAPS_” Gmail account will be: ; 
-### Go to
+### Go to
If you are already logged into Google, this will direct you to your “Everyday” **My Account** page.
-(1) Click on the top right of the page on your profile picture (in this case, a simple 
+(1) Click on the top right of the page on your profile picture (in this case, a simple )
(2) select “_add another account_”.
@@ -89,7 +89,7 @@ Gmail will display the account name. It will ask you to accept Gmail’s terms a
### Customize the new profile display
-At this point you should be on Gmail’s MyAccount page showing your new **AAPS**-dedicated email account. The profile picture will be set by default to the first letter of your name. Change it to something unique to avoid confusion… in this example, Donald.Muck.AAPS has replaced  with 
+At this point you should be on Gmail’s MyAccount page showing your new **AAPS**-dedicated email account. The profile picture will be set by default to the first letter of your name. Change it to something unique to avoid confusion… in this example, Donald.Muck.AAPS has replaced  with .
\
@@ -103,7 +103,7 @@ This part can be a bit confusing, since you will have to switch back and forth b
2. Right click on your Browser logo in your taskbar
3. From the menu select “New Window”... and adjust it so it only takes the bottom half of the screen.
-Open in each browser window. Make sure your personal account is on top and the new dedicated **AAPS** account is on the bottom, and is easily identifiable by the profile picture in the top right corner. (if needed you can always switch accounts by clicking on the profile picture and selecting the correct one.
+Open in each browser window. Make sure your personal account is on top and the new dedicated **AAPS** account is on the bottom, and is easily identifiable by the profile picture in the top right corner. If needed, you can always switch accounts by clicking on the profile picture and selecting the correct one.
diff --git a/docs/EN/UsefulLinks/FAQ.md b/docs/EN/UsefulLinks/FAQ.md
index 0f237ec44d4c..7caf42df4a5e 100644
--- a/docs/EN/UsefulLinks/FAQ.md
+++ b/docs/EN/UsefulLinks/FAQ.md
@@ -149,7 +149,7 @@ You have to rework your old sports habits from pre-loop times. If you simply con
So, you would have more carbohydrates on board, but at the same time the loop would counteract and release insulin.
When looping you should try these steps:
-* Make a [profile switch](#ProfileSwitch-change-percentage) < 100%: tap the profile name on the main screen, tap the round **▶** button, then set **Percentage** and **Duration**.
+* Make a [profile switch](#ProfileSwitch-change-percentage) below 100%: tap the profile name on the main screen, tap the round **▶** button, then set **Percentage** and **Duration**.
* Set an [activity temp target](#TempTargets-activity-temp-target) above your standard target. With a percentage below 100 % and a duration, the same **Activate** screen offers a **Temporary target / Activity** switch that starts both at once.
* If you are using SMB make sure ["Enable SMB with high temp targets"](#Open-APS-features-enable-smb-with-high-temp-targets) and ["Enable SMB always"](#Open-APS-features-enable-smb-always) are disabled.
@@ -166,7 +166,7 @@ You can remove the pump to be 'free', but you should tell AAPS so that the IOB c
Drinking alcohol is risky in closed loop mode as the algorithm cannot predict the alcohol influenced BG correctly. You have to check out your own method for treating this using the following functions in AAPS:
* Deactivating closed loop mode and treating the diabetes manually or
-* setting high temp targets and deactivating UAM to avoid the loop increasing IOB due to an unattended meal or
+* setting high temp targets and deactivating UAM to avoid the loop increasing IOB due to an unannounced meal or
* do a [profile switch](#ProfileSwitch-change-percentage) to noticeably less than 100%
The *Alcohol* [scene](#scenes) template is a starting point you can adapt to your own method.
@@ -327,9 +327,9 @@ You can also change when the alert is raised: press the **Settings** (gear) icon
(FAQ-link-unresponsive)=
#### My link/pump/pod is unresponsive (RL/OL/EmaLink…)
-With some phones, there are Bluetooth disconnects from the Links (RL/OL/EmaL...).
+With some phones, there are Bluetooth disconnects from the Links (RL/OL/EmaLink).
-Some also have non responsive Links (AAPS says that they are connected but the Links can't reach or command the pump.)
+Some also have non responsive Links (AAPS says that they are connected but the Links can't reach or command the pump).
First try the **Reset RileyLink** button on the pump screen (see your pump's page: [Medtronic](#MedtronicPump-what-to-do-if-i-loose-connection-to-rileylink-and-or-pump), [Omnipod Eros](#OmnipodEros-reset-rileylink-config-notes)). If this does not help, the easiest way to get all these parts working together is:
@@ -379,5 +379,5 @@ The Pod state is included in the exported settings, so an active Pod can be move
Read these sections first:
-* [Export and import settings](#omnipod-dash-export-import) on the Omnipod DASH page, and [Tubeless pumps](#ExportImportSettings-tubeless-pumps): on the new phone, tick **Also replace pump settings** and use a file exported during the Pod you are wearing now,
+* [Export and import settings](#omnipod-dash-export-import) on the Omnipod DASH page, and [Tubeless pumps](#ExportImportSettings-tubeless-pumps): on the new phone, tick **Also replace pump settings** and use a file exported while wearing your current Pod,
* [Discarding a pod](#omnipod-dash-discard-pod), to remove the Pod from the old phone afterwards. Keep the old phone in airplane mode until the Pod is discarded, so that the two phones never talk to the Pod at the same time.
diff --git a/docs/EN/UsefulLinks/Glossary.md b/docs/EN/UsefulLinks/Glossary.md
index 08518975ce82..3efbab9ff6e5 100644
--- a/docs/EN/UsefulLinks/Glossary.md
+++ b/docs/EN/UsefulLinks/Glossary.md
@@ -21,7 +21,7 @@ __Android Auto__ = a system used to host certain functions of an Android smartph
__APK__ = Android application Package.
A software installation file. Further info → [Wiki - 'Building APK'](../SettingUpAaps/BuildingAaps.md).
-__Autosens__ = calculation of sensitivity to insulin between a period of a 24 and 8 hour window etc. Further info → [DIABETTECH - __Autosens__](https://www.diabettech.com/what-conclusions-can-we-draw-when-investigating-insulin-sensitivity-using-the-autosens-function-within-openaps-an-n1-study/).
+__Autosens__ = calculation of sensitivity to insulin over a 24-hour and an 8-hour window etc. Further info → [DIABETTECH - __Autosens__](https://www.diabettech.com/what-conclusions-can-we-draw-when-investigating-insulin-sensitivity-using-the-autosens-function-within-openaps-an-n1-study/).
__Azure__ = cloud computing platform to host __Nightscout__ web app → see also __Nightscout__.
@@ -49,7 +49,7 @@ __CAN__ = status light for overdue cannula change, shown in the status row of __
__CGM__ = Continuous Glucose Monitor → see also __FGM__.
-__Closed Loop__ = a closed loop system which makes automatic adjustments to the user’s basal delivery based on an __AAPS’s__ algorithm and the user’s __Profile__ settings without requiring the user’s-approval. Further info → Wiki - 'closed loop' and see also __HCL__ / __FCL__.
+__Closed Loop__ = a closed loop system which makes automatic adjustments to the user’s basal delivery based on an __AAPS’s__ algorithm and the user’s __Profile__ settings without requiring the user’s approval. Further info → [Wiki - 'closed loop'](#KeyAapsFeatures-ClosedLoop) and see also __HCL__ / __FCL__.
__COB__ = Carbs On Board.
This is the amount of carbohydrates currently available for the user's digestion → see also IOB.
@@ -59,7 +59,7 @@ i.e. how much does the user’s __BG__ increase for 1g of carbs absorbed.
__DIA__ = Duration of Insulin Action. Further info → [Wiki - 'DIA'](#Config-Builder-insulin-dia) and see also → [DIABETTECH - 'DIA'](https://www.diabettech.com/why-we-are-regularly-wrong-in-the-duration-of-insulin-action-dia-times-we-use-and-why-it-matters/).
-__DST__ = Daylight Savings Time. See [Wiki - Timezone Change and Daylight Saving](../DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md).
+__DST__ = Daylight Saving Time. See [Wiki - Timezone Change and Daylight Saving](../DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md).
__Dynamic ISF (or DynISF)__ = a feature within **AAPS** that adapts the insulin sensitivity factor (**ISF**) dynamically based on the user’s **TDD** and **BG**.
@@ -67,15 +67,15 @@ __eCarbs__ = extended Carbs.
Carbs split up over several hours (e.g. to cover fat/protein), which lets __AAPS__ spread the insulin like an extended bolus. Further info → [Wiki - 'Extended Carbs'](../DailyLifeWithAaps/ExtendedCarbs.md)
__FCL__ = Full Closed Loop.
-A loop which needs no mealtime input from the user: no carb counting and no meal bolus. Further info → Wiki - 'full closed loop' and see also __HCL__.
+A loop which needs no mealtime input from the user: no carb counting and no meal bolus. Further info → [Wiki - 'full closed loop'](../AdvancedOptions/FullClosedLoop.md) and see also __HCL__.
__FGM__ = Flash Glucose Monitor such as the Abbott Freestyle Libre.
- Further info → Wiki - 'BG source' and see also 'CGM'.
+ Further info → [Wiki - 'BG source'](#Config-Builder-bg-source) and see also 'CGM'.
-__git__ = a tool used store and download the __AAPS’__ source code.
+__git__ = a tool used to store and download the __AAPS’__ source code.
__GitHub__ = a web-based service that hosts the __AAPS__ source code and its version control (tracking changes in files and coordinating work on them, especially for teams), and can also build the app.
-It is also necessary for __APK__ updates. Further info → Wiki - 'update APK'.
+It is also necessary for __APK__ updates. Further info → [Wiki - 'update APK'](../Maintenance/UpdateToNewVersion.md).
__Glimp__ = an app to collect values from Freestyle Libre.
@@ -100,7 +100,7 @@ __Log files__ = __AAPS’__ records of the user's actions (useful for troublesho
__maxIOB__ = maximum total IOB.
This is a safety feature and prevents __AAPS__ delivering insulin over the user’s settings. Further info → [Wiki - 'Maximum total IOB OpenAPS can’t go over'](#Open-APS-features-maximum-total-iob-openaps-cant-go-over).
-__min_5m_carbimpact__ = safety feature that is a calculation of default carb decay when carb absorption cannot be determined based on the user’s blood’s reactions. Further info → [Wiki - 'Preferences'](#Preferences-min_5m_carbimpact).
+__min_5m_carbimpact__ = safety feature that is a calculation of default carb decay when carb absorption cannot be determined based on the user’s blood’s reactions. Further info → [Wiki - 'min_5m_carbimpact'](#Preferences-min_5m_carbimpact).
__Nightscout__ = open source project to access and report __CGM__ data.
The central data hub for the user’s __AAPS__ data and can generate reports to view the user’s historical __Nightscout__ data, such as expected HbA1c, time in range or search for patterns in the data via percentile chart etc.
@@ -115,7 +115,7 @@ __OpenAPS__ = Open Artificial Pancreas System, the predecessor project and basis
__Open Loop system__ = an __AAPS__ feature that will recommend adjustments and which must be performed manually by the user on __AAPS__. Further info → [Wiki - 'Open Loop'](#KeyAapsFeatures-OpenLoop).
-__Oref0 / Oref1__ = sensitivity detection and "reference design implementation version 0/1". It is the key algorithm behind OpenAPS Wiki - sensitivity detection.
+__Oref0 / Oref1__ = sensitivity detection and "reference design implementation version 0/1". It is the key algorithm behind OpenAPS. Further info → [Wiki - 'sensitivity detection'](../DailyLifeWithAaps/SensitivityDetectionAndCob.md).
__OS-AID__ = Open-Source Automated Insulin Delivery.
An __AID__ system built from open-source software, such as __AAPS__, __OpenAPS__, Loop or Trio. These systems are not formally approved by health bodies (FDA, NHS etc.) → see also __AID__.
@@ -154,16 +154,16 @@ __Super bolus__ = shift of basal to bolus insulin for faster __BG__ adjustment.
__TBB__ = total base basal (sum of basal rate within 24 hours) → see also __TBR__ / __TDD__.
-__TBR__ = temporary basal rate→ see also __TBB__ / __TDD__.
+__TBR__ = temporary basal rate → see also __TBB__ / __TDD__.
__TDD__ = total daily dose (bolus + basal per day) → see also __TBB__ / __TBR__.
-__TT__ = temporary target temporary increase/decrease of the user’s __BG__ target (range) e.g. for eating or sport activities. Further info → [Wiki - 'temp targets'](../DailyLifeWithAaps/TempTargets.md).
+__TT__ = temporary target: temporary increase/decrease of the user’s __BG__ target (range) e.g. for eating or sport activities. Further info → [Wiki - 'temp targets'](../DailyLifeWithAaps/TempTargets.md).
__UAM__ = unannounced meals.
Detection of significant increase in __BG__ levels due to meals, adrenaline or other influences and attempt to adjust this. Further info → [Wiki - 'UAM'](#enable-uam) and see also __SMB__.
-__Virtual pump__ = an __AAPS__ feature which allows the user to try __AAPS’__ functions or for PWD using a pump model with no __AAPS__ driver for looping → see also __Open Loop__.
+__Virtual pump__ = an __AAPS__ feature which allows the user to try __AAPS’__ functions, or lets PWD whose pump model has no __AAPS__ driver use __AAPS__ as an open loop → see also __Open Loop__.
__Wallpaper__ = __AAPS__ background image see phones page.
diff --git a/docs/EN/WearOS/BuildingAapsWearOS.md b/docs/EN/WearOS/BuildingAapsWearOS.md
index 0227ef2f0e84..dbdbe416bbb9 100644
--- a/docs/EN/WearOS/BuildingAapsWearOS.md
+++ b/docs/EN/WearOS/BuildingAapsWearOS.md
@@ -78,7 +78,7 @@ Next: install the Wear apk on the watch, see [Set up AAPS on your Wear OS watch]
In the process of building the full **AAPS** app (and in fact any signed app), Android Studio generates a .json file in the same folder. This then causes errors with [uncommitted changes](#troubleshooting_androidstudio-uncommitted-changes) when you try to build the next signed app, like the **AAPS** wear app. The quickest way to resolve this is to navigate to the folder where the full AAPS app has been built, your folder is probably something like:
-`C:\Users\Your Name\AndroidStudioProjects\AndroidAPS\app\aapsclient\release. `
+`C:\Users\Your Name\AndroidStudioProjects\AndroidAPS\app\full\release. `
Either delete, or move the unneeded .json file out of the folder. Then try to build the **AAPS** wear app again. If that doesn't work, the more detailed [troubleshooting guide](../GettingHelp/TroubleshootingAndroidStudio.md) will help you to identify the specific file causing the issue, which could also be your keystore file.
diff --git a/docs/EN/WearOS/WearOsSmartwatch.md b/docs/EN/WearOS/WearOsSmartwatch.md
index 2bb285412031..cee645546d3f 100644
--- a/docs/EN/WearOS/WearOsSmartwatch.md
+++ b/docs/EN/WearOS/WearOsSmartwatch.md
@@ -91,7 +91,7 @@ Install the **AAPS Wear** apk using [Wear Installer 2](https://youtu.be/abgN4jQq
```{admonition} Wear OS 5
:class: warning
-On Wear OS 5 the AAPS watchface has to be selected with Wear Installer 2 right after installing the Wear app: the installer offers the **AAPS (Custom)** watchface at the end of the installation. If you accidentally switch to another watchface, repeat the installation. Changing the watchface settings (Dark, Watchdivider, etc.) may not be possible.
+On Wear OS 5 the AAPS watchface has to be selected with Wear Installer 2 right after installing the Wear app: the installer offers the **AAPS (Custom)** watchface at the end of the installation. If you accidentally switch to another watchface, repeat the installation. Changing the watchface settings (Dark, Matching divider, etc.) may not be possible.
If the classic watchface currently works for you, **disable automatic watch updates**: the next firmware update is likely to break it. If you update to Wear OS 6 anyway, read the section above: **AAPS** then installs its own watchface in the new format.
```
@@ -115,13 +115,13 @@ Here are basic setup guides for the [Galaxy Watch 5](https://www.youtube.com/wat
## Basic smartwatch familiarity
After basic setup of your watch according to the video above, go to the playstore on the phone and download the following apps:
-"Galaxy Wearable" “Samsung” and either “Easy Fire tools” or "Wear Installer 2".
+"Galaxy Wearable", “Samsung” and either “Easy Fire tools” or "Wear Installer 2".
There are plenty of 3rd party YouTube videos which will help you with getting familiar with your new smartwatch, for example:
[https://www.youtube.com/watch?v=tSVkqWNmO2c](https://www.youtube.com/watch?v=tSVkqWNmO2c)
-The app “Galaxy Wearable” also has an instruction manual section in it. Open galaxy wearable on the phone, search for the watch, attempt to pair the watch with the phone. Depending on your version, this may prompt you to install a further 3rd app “galaxy watch 4 plugin” from the playstore (takes a while to download). Install this on the phone, and then attempt to pair the watch and phone again in the wearable app. Go through a series of menus and tick various preferences.
+The app “Galaxy Wearable” also has an instruction manual section in it. Open galaxy wearable on the phone, search for the watch, attempt to pair the watch with the phone. Depending on your version, this may prompt you to install one more app, “galaxy watch 4 plugin”, from the playstore (takes a while to download). Install this on the phone, and then attempt to pair the watch and phone again in the wearable app. Go through a series of menus and tick various preferences.
## Setting up a Samsung account
@@ -280,8 +280,8 @@ The final step is to configure **AAPS** on the phone to interact with **Wear.apk
To bolus or take other actions from the watch, also turn on **Wear control** in [Settings > Wear](#preferences-wear).
-To change to a different **AAPS** watchface, press on the home screen of the
-watch and it will come to “customise”. Then swipe right until you get to all the **AAPS** faces.
+To change to a different **AAPS** watchface, long-press the watchface on the home screen of the
+watch and tap **Customize**. Then swipe right until you get to all the **AAPS** faces.
If the **AAPS** Wear.apk has been successfully side-loaded onto the smartwatch, it will look like this:
@@ -359,7 +359,7 @@ F - phone battery
G - basal rate (shown in U/h during standard rate and in % during TBR)
-H - BGI (blood glucose interaction)
+H - BGI (blood glucose impact)
-> the degree to which BG “should” be rising or falling based on insulin activity alone.
I - carbs (carbs on board | e-carbs in the future)
diff --git a/docs/EN/index.md b/docs/EN/index.md
index fb5ed06158b3..9785ae79d298 100644
--- a/docs/EN/index.md
+++ b/docs/EN/index.md
@@ -5,7 +5,7 @@
```{admonition} Latest Release
:class: note
- 31 October 2026 : Version 4.0.0 is out. Check the [Release Notes](#latestrelease) to see what's new and follow the instructions in the [update manual](./Maintenance/UpdateToNewVersion.md) to update.
+31 October 2026: Version 4.0.0 is out. Check the [Release Notes](#latestrelease) to see what's new and follow the instructions in the [update manual](./Maintenance/UpdateToNewVersion.md) to update.
```
@@ -17,7 +17,7 @@ This documentation explains how to set up and use **AAPS**. You can navigate thr
Section **1) Getting Started**, the [Introduction](Getting-Started/Introduction.md) explains the general concept of what an artificial pancreas system (APS) is designed to do. It outlines the background of looping in general, why **AAPS** was developed, compares **AAPS** to other systems, and addresses safety. It gives suggestions about how to talk to your clinical team about **AAPS**, explains why you need to build the **AAPS** app yourself rather than just downloading it, and gives an overview of the typical connectivity of an **AAPS** system. It also addresses accessibility, and who is likely to benefit from **AAPS**.
-[Preparing for AAPS](./Getting-Started/PreparingForAaps.md) gives more detail about safety considerations, and the phones, CGMs (Continuous Glucose Monitors) and insulin pumps which are compatible with **AAPS**. It gives an overview of the process you will go through, and provides an approximate timeline for gaining full functionality of **AAPS**. This section gets you technically prepared to assemble your **AAPS** setup as quickly and efficiently as possible. The subsection [CGM Configuration](./Getting-Started/CompatiblesCgms.md) explains how to optimize your CGM setup and which smoothing options are best.
+[Preparing for AAPS](./Getting-Started/PreparingForAaps.md) gives more detail about safety considerations, and the phones, CGMs (Continuous Glucose Monitors) and insulin pumps which are compatible with **AAPS**. It gives an overview of the process you will go through, and provides an approximate timeline for gaining full functionality of **AAPS**. This section gets you technically prepared to assemble your **AAPS** setup as quickly and efficiently as possible. The subsection [Compatible CGMs](./Getting-Started/CompatiblesCgms.md) explains how to optimize your CGM setup and which smoothing options are best.
Now that you have a solid understanding of the process, you can start assembling your **AAPS** loop.
@@ -42,7 +42,7 @@ Section **9) [Help & Troubleshooting](GettingHelp/WhereCanIGetHelp.md)** should
Section **10)** covers **[Advanced AAPS options](./AdvancedOptions/FullClosedLoop.md)** such as how to progress from using **AAPS** for hybrid-closed looping (bolusing for meals _etc._) to full closed looping (no bolusing), how to [tune your profile](./GettingHelp/ProfileTuning.md) and use Autotune, and details development and engineering modes. Most users get on just fine with the main or "Master" **AAPS** version without looking into these options, this section is for users who already have good control and are looking to further improve their setup.
-In section **11) [How to support AAPS](SupportingAaps/HowToEditTheDocs.md)** we provide information so that you can support this project. You can donate money, equipment or expertise. You can suggest/make changes to the documentation yourself, help with [translation of the documentation](SupportingAaps/Translations) and provide your data through the Open Humans project.
+In section **11) [How to support AAPS](SupportingAaps/HowCanIHelp.md)** we provide information so that you can support this project. You can donate money, equipment or expertise. You can suggest/make changes to the documentation yourself, help with [translation of the documentation](SupportingAaps/Translations.md) and provide your data through the Open Humans project.
Section **12) Resources**, contains archived or additional documentation, including a subsection for [clinicians](UsefulLinks/ClinicianGuideToAaps.md) who have expressed interest in open source artificial pancreas technology such as **AAPS**, or for patients who want to share such information with their clinicians, this topic is also addressed in the introduction. More diabetes and looping references and resources are also contained in this section. It includes the [Glossary](./UsefulLinks/Glossary.md), a list of the acronyms (or short-term names) used throughout **AAPS**. This is where to go to find out what the terms ISF or TT, stand for, for example.