Merge pull request #2513 from openaps/l10n_master

New Crowdin updates

Author: psonnera

docs/CROWDIN/cs/CompatiblePumps/OmnipodDASH.md

@@ -51,29 +51,29 @@ The instructions below explain how to activate a new pod session using **AAPS**.
 
 Ensure you have read and understand this whole guide, have read and understand the **Before You Begin** section, as well as  **[Omnipod and AAPS Constraints and Issues](#omnipod-dash-constraints)** to avoid running into a known problem.
 
-#### **SAFETY FIRST** - You **SHOULD NOT** try to connect **AAPS** to a pod for the first time without having access to all of the following:
+### **SAFETY FIRST** - You **SHOULD NOT** try to connect **AAPS** to a pod for the first time without having access to all of the following:
 1. Extra pods (3 or more spare)
 2. Spare Insulin and MDI equipment
 3. A working Omnipod PDM (In case **AAPS** fails)
 4. Supported Phones are a must! (See [Hardware/Software Requirements](#hardware-software-requirements))
 5. Correct version of AAPS built and installed
 
-#### **Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.**
+### **Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.**
 - Before using **AAPS** you or your care giver would have had to manage the Pod using the Omnipod PDM (or in some regions a Phone app) to send commands to your DASH (e.g a Bolus).
 - The DASH can only facilitate a single Bluetooth device (e.g PDM or Phone) connection to manage and send commands.
 - The device that successfully activates the pod is the only device allowed to communicate with that Pod from that point forward. This means that once you activate a DASH with your Android phone using **AAPS**, **you will no longer be able to use your PDM with that pod!** For the time that Pod is active the **AAPS** Dash driver running on your Android phone is now the new PDM for your pod.
 - **DO NOT Throw away your PDM!** It is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or **AAPS** is not working correctly.
 
-#### Your pod **WILL NOT** stop delivering insulin when it is not connected to AAPS.
+### Your pod **WILL NOT** stop delivering insulin when it is not connected to AAPS.
 Default basal rates are programmed on the pod on activation as defined in the current active [**Profile**](../SettingUpAaps/YourAapsProfile.md).  
 As long as **AAPS** is operational it will send basal rate adjustment commands that run for a maximum of 120 minutes.  
 When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md).
 
-#### **AAPS Profile(s) do not support 30 minute basal rate time frames**
+### **AAPS Profile(s) do not support 30 minute basal rate time frames**
 If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**.  
 You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature.
 
-#### **0U/h Profile basal rates are NOT supported in AAPS**
+### **0U/h Profile basal rates are NOT supported in AAPS**
 While the DASH does support a zero basal rate, **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate.  
 Instead a temporary zero basal rate can be achieved through the "Disconnect pump" function, or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate.  
 **NOTE:** The lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h.
@@ -120,7 +120,7 @@ To verify that you have selected the DASH in **AAPS**, if you have **checked the
 
 (omnipod-dash-activate-pod)=
 
-### Aktivovat Pod
+### Activate Pod
 
 1. Navigate to the **DASH** tab and click on the **POD MGMT (1)** button, and then click on **Activate Pod (2)**.
 
@@ -194,7 +194,7 @@ To verify that you have selected the DASH in **AAPS**, if you have **checked the
 
 (omnipod-dash-deactivate-pod)=
 
-### Deaktivovat Pod
+### Deactivate Pod
 
 Under normal circumstances, the expected lifetime of a pod is three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of total pod usage.
 
@@ -351,7 +351,7 @@ Below is an explanation of the layout and meaning of the icons and status fields
 
 
 
-### Tlačítka
+### Buttons
 
 ![Refresh_Icon](../images/DASH_images/Refresh_LOGO.png) Sends a refresh command to the active pod to update communication.
 
@@ -405,7 +405,7 @@ The settings groups are listed below; you can enable or disable via a toggle swi
 
 ***NOTE:** An asterisk (\*) denotes the default setting is enabled.*
 
-### Potvrzovací pípnutí
+### Confirmation beeps
 
 ![Dash_settings_4](../images/DASH_images/Dash_settings/Dash_settings_4.jpg)
 
@@ -421,7 +421,7 @@ Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery
 
 
 
-### Výstrahy
+### Alerts
 
 ![Dash_settings_5](../images/DASH_images/Dash_settings/Dash_settings_5.jpg)
 
@@ -439,7 +439,7 @@ Provides **AAPS** alerts for pod expiration, shutdown, low reservoir based on th
 
 
 
-### Oznámení
+### Notifications
 
 ![Dash_settings_6](../images/DASH_images/Dash_settings/Dash_settings_6.jpg)
 
@@ -465,7 +465,7 @@ This tab is well documented in the main **AAPS** documentation but there are a f
 
    ![ACT_1](../images/DASH_images/Actions_Tab/ACT_1.png)
 
-### Úroveň
+### Level
 
 **Insulin Level**
 

docs/CROWDIN/cs/CompatiblePumps/OmnipodEros.md

@@ -483,13 +483,13 @@ Below is an explanation of the layout and meaning of the icons on the **Pod Mana
 
 > ![Omnipod_Tab_Pod_Management](../images/omnipod/Omnipod_Tab_Pod_Management.png)
 
-- **Aktivovat Pod**
+- **Activate Pod**
 
   > ![activate_pod](../images/omnipod/ICONS/omnipod_overview_pod_management_activate_pod.png)
   > 
   > Primes and activates a new pod
 
-- **Deaktivovat Pod**
+- **Deactivate Pod**
 
   > ![deactivate_pod](../images/omnipod/ICONS/omnipod_overview_pod_management_deactivate_pod.png)
   > 
@@ -589,7 +589,7 @@ Allows for scanning of a pod communication device. The Omnipod driver cannot sel
 
 - **Enable battery change logging in Actions:** In the Actions menu, the battery change button is enabled IF you have enabled this setting AND the battery reporting setting above.  Some pod communication devices now have the ability to use regular batteries which can be changed.  This option allows you to note that and reset battery age timers.
 
-### Potvrzovací pípnutí
+### Confirmation beeps
 
 Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes.
 
@@ -598,7 +598,7 @@ Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery
 - **\*SMB beeps enabled:** Enable or disable confirmation beeps when a SMB is delivered.
 - **TBR beeps enabled:** Enable or disable confirmation beeps when a TBR is set or canceled.
 
-### Výstrahy
+### Alerts
 
 Provides AAPS alerts and Nightscout announcements for pod expiration, shutdown, low reservoir based on the defined threshold units.
 
@@ -610,7 +610,7 @@ Provides AAPS alerts and Nightscout announcements for pod expiration, shutdown,
 - **Number of units:** The number of units at which to trigger the pod low reservoir alert.
 - **Automatically acknowledge Pod alerts:** When enabled a notification will still be issued however immediately after the first pod communication contact since the alert was issued it will now be automatically acknowledged and the alert will be dismissed.
 
-### Oznámení
+### Notifications
 
 Provides AAPS notifications and audible phone alerts when it is uncertain if TBR, SMB, or bolus events were successful.
 

docs/CROWDIN/cs/DailyLifeWithAaps/AapsScreens.md

@@ -95,13 +95,13 @@ The blocks in the middle shows:
 
 On the right side, an icon shows the loop status:
 
-1. Green circle = loop running
-2. Purple circle with dotted line = [low glucose suspend (LGS)](#objectives-objective6)
+1. Green circle = [closed loop](#KeyAapsFeatures-ClosedLoop), loop running
+2. Purple circle with dotted line = [low glucose suspend (LGS)](#KeyAapsFeatures-LGS)
 3. Red circle = loop disabled (not working permanently)
 4. Red circle = loop suspended (temporarily paused but basal insulin will be given) - remaining time is shown below icon
 5. Grey circle = pump disconnected (temporarily no insulin dosage at all) - remaining time is shown below icon
 6. Orange circle = super bolus running - remaining time is shown below icon
-7. Blue circle with dotted line = open loop
+7. Blue circle with dotted line = [open loop](#KeyAapsFeatures-OpenLoop)
 
 Short press or Long press the icon to open the Loop dialog to switch loop mode (Close, Low Glucose Suspend, Open or Disable), suspend / re-enable loop or disconnect / reconnect pump.
 
@@ -771,12 +771,6 @@ This tab shows all notes and alerts recorded in Nightscout.
 
 (aaps-screens-running-mode)=
 
-### Running mode
-
-![Running mode](../images/Screens/RunningMode.png)
-
-Running mode shows current and past AAPS running mode, it is also visible on the main graph as an upper colored bar.
-
 ## History Browser
 
 This view can be accessed by pressing the 3 dots on the right of the menu, then History. It is not possible to put in the main menu through the Config Builder. It can also be accessed through a button at the bottom of the [Action tab](#screens-action-tab).