Tabbed options in Browser Build

And some broken links

Author: psonnera

docs/EN/AdvancedOptions/Autotune.md

@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
 
 - The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
 
-  - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+  - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
 
   ![Autotune Compare profiles](../images/Autotune/Autotune_5.png)
 
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
 
 ![Autotune default screen](../images/Autotune/Autotune_11.png)
 
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated.
+- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#autotune-run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated.
   - **Be Careful, you must trust and verify during several following days, that after an update and activation of Tuned profile without modification, it improves your loop**
 
 - Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal.
   - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off)
 - Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below. 
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below. 
 
 ### Other settings
 

docs/EN/AdvancedOptions/DevBranch.md

@@ -61,6 +61,6 @@ Available from 3.3.2.1.dev
 
     - Select the variant you need:
       - fullRelease: For regular pump usage with full functionality.
-      - [aapsclient、aapsclient2](../RemoteFeatures/RemoteControl.md#aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
+      - [aapsclient, aapsclient2](#RemoteControl_aapsclient) For caregivers (requires [Nightscout](../SettingUpAaps/Nightscout.md))。
       - pumpcontrol
       - Text ending with “Debug” indicates that the APK will be built in debug mode, which is useful for troubleshooting.

docs/EN/AdvancedOptions/FullClosedLoop.md

@@ -7,7 +7,7 @@ Whilst **hybrid closed loop** ('HCL') is algorithm based, it still requires the
 
 In **FCL** mealsize-related bolus are no longer required: leave it to the algorithm!  **AAPS** may allow without the user giving any bolus, and without making carb inputs, in a mode called ‘un-announced meals’ **(‘UAM’)**. **UAM** allows **AAPS** to better tolerate incorrect carb inputs by being more aggressive.
 
-### What to expect?
+## What to expect?
 
 There are many published studies on the favourable results **FCL** can achieve. For further reading refer to the following: 
 
@@ -22,7 +22,7 @@ Success for **FCL** requires the user to:
 - fine tune and adjust the **AAPS** settings (notably **Automations**). 
 
 
-### General considerations why (not to) move from HCL to FCL
+## General considerations why (not to) move from HCL to FCL
 
 **FCL** is not for everyone:
 
@@ -32,15 +32,15 @@ Success for **FCL** requires the user to:
 - Difficulties still remain to establish a **FCL** for kids (discussed below).
 
 
-### Well-tuned hybrid closed loop
+## Well-tuned hybrid closed loop
 
 It is advisable to first establish a well-tuned **HC**L before considering the transition to **FCL**.  Success with **FCL** requires a highly personalised individualised tuning of the user’s setting so that **AAPS** can give insulin to closely mimic YOUR successful hybrid closed loop mode. 
 
 **FCL** requires the user to set up and tune their **Automations**. However the user must have a confident understanding of their insulin management needs before embarking on **FCL**. Errors can be masked with counter-errors. This can create an unstable **FCL** system, and make it hard to later correct. You should expect to reach a comparable %TIR with your FCL as you see today in your **HCL**. 
 
 **FCL is a DIY set up of Automations determined by the user by analysing their data from both their successful HCL and  initial FCL experience when tuning your settings.** 
 
-### Fast insulin (Lyumjev, Fiasp)
+## Fast insulin (Lyumjev, Fiasp)
 
 **FCL** requires fast insulin.  This is so that at the start of meal-related **BG** rise, **FCL** is able to keep **BG** in range (by common definition, under 180 mg/dl (10 mmol/l)).
 
@@ -62,7 +62,7 @@ IEEE Control Systems Magazine, ResearchGate [The Artificial Pancreas and Meal Co
 
 However, Fiasp or Lyumjev can result in frequent pump occlusions, even after optimising things like needle length. It is important to have an eye on the cannula or pod time. Many users find 48 hours to be the efficacy insulin limit before resulting in cannula/pod failure.
 
-### Prerequisites
+## Prerequisites
 
 **BG** values and stable bluetooth connectivity are required to ensure **AAPS** can optimally perform without losing valuable time. **FCL** requires a 24/7 technically stable system:
 
@@ -76,13 +76,13 @@ However, Fiasp or Lyumjev can result in frequent pump occlusions, even after opt
 
 The above will vary depending on your **AAPS** component system and your lifestyle.
 
-### Meal-related limitations
+## Meal-related limitations
 
 - Setting up a **FCL** may be easier for people whose diets do not consist of food components with a rapid high effect on **BG**, and meal patterns that do not wildly vary day-to-day. This does not necessarily mean low carb.                                            
-               
+  
 - Fat or protein rich diets, or slow digestion/gastroparesis, make things easier rather than harder for **FCL**  because late carbs nicely cover for inevitable “tails” of late action from bolus needed around peak time.
 
-#### Glycemic index and effect on blood glucose
+### Glycemic index and effect on blood glucose
 
 The challenge for the **UAM** mode rises with rising 'Effect on Blood Glucose ('EBG')
 
@@ -102,15 +102,15 @@ The most difficult meals for **FCL** are those foods exclusively very high and h
 Erratic consumption of snacks and sweet drinks that are loaded with fast absorbing carbs is problematic for **FCL**.
 
 
-#### Preparing for activity/sports
+## Preparing for activity/sports
 
 When exercising or being active, with a pump or hybrid closed loop it is recommended that the user reduces **IOB** prior to exercise.
 
 With **FCL**, the algorithm is tuned to detect **UAM** and automatically deliver insulin to counter **BG** rises.  A high **Temp Target** and lower **Profile Percentage** (effective already around meal start) should be set well in advance of any activity.
 
 Unusual or erratic exercise activity levels present difficulties for **FCL**. Planning ahead is required for exercise (especially if you want to reduce the need for rescue carbs/snacks during sports low). After an active day it is recommended that a lower  **Percentage Profile** is set for overnight after the evening meal is fully digested: set in **Automations** an elevated (>100 mg/dl) **BG**  target, with “no **SMBs** at elevated target” selected in **AAPS*** preferences.
 
-#### Hurdles for kids
+## Hurdles for kids
 
 **FCL** can present extra challenges for children and these include:
 
@@ -261,7 +261,7 @@ Automation #4, “post-meal High”, is also suitable in hybrid closed loop.
 
 In addition, a termination-Automation #5, “Stop pmH”, is needed, so that the aggressiveness of the insulin administration is reduced, as soon as the glucose value is falling. (However, often the loop will limit more insulin anyways for hypo prevention because predicted glucose runs low already).
 
-### Hypo prevention
+## Hypo prevention
 
 The core problem is that the **UAM** **FCL** (without carb inputs) can have **no idea how many g of carbs are still available** for absorption, and might use up that “tail” insulin, without you going into a hypo from it. 
 

docs/EN/CompatibleCgms/Juggluco.md

@@ -19,6 +19,8 @@ Disable any active uploader to Nightscout in Juggluco.
 
 ![Disable Nightscout Upload](../images/juggluco/DisableNightscoutUpload.png)
 
+(juggluco-to-aaps)=
+
 ## Juggluco to AAPS
 
 Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
@@ -31,6 +33,8 @@ Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
 
 ![Juggluco to AAPS](../images/juggluco/Juggluco-AAPS.png)
 
+(juggluco-to-xdrip)=
+
 ## Juggluco to xDrip+
 
 Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.

docs/EN/CompatibleCgms/Libre3.md

@@ -18,7 +18,7 @@ Within xDrip+ the sensor can be calibrated in the range of -40 mg/dl to +20 mg/d
 ## Method 1: use 1-minute readings directly
 AndroidAPS is taylored for 5-minute readings. Therefore processing 1-minute values has occasional limitations. 
 
-![Juggluco broadcast to AAPS](../images/Juggluco_AAPS.png)
+See [here](#juggluco-to-aaps).
 
 
 ## Method 2: convert 1-minute readings into 5-minute values via xDrip 
@@ -30,8 +30,6 @@ Follow the instructions [here]( https://www.juggluco.nl/Juggluco/libre3/)
 
 Make sure you send the glucose values to xDrip+: In Juggluco's settings you can configure Juggluco to send its glucose value to other apps. Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+
 
-![Juggluco broadcast to xDrip+](../images/Juggluco_xDrip.png)
-
 ### Step 2: Setup xDrip
 
 The blood glucose values are received by the xDrip+ app on the smartphone.
@@ -60,10 +58,10 @@ After a sensor change xDrip+ will automatically detect the new sensor and will d
 
 ### Step 4: Configure AndroidAPS
 
-- Select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+- See [here](#juggluco-to-xdrip) and come back.
 
 - If AndroidAPS does not receive BG values when phone is in airplane mode, use "Identify receiver"
-- Turn of Smoothing (done in xDrip+ already)
+- Turn off Smoothing (done in xDrip+ already)
 
 ## Subsequent sensor changes