diff --git a/docs/CROWDIN/cs/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/cs/Maintenance/UpdateToNewVersion.md
index 17cbeaebb640..2647e7e07cf9 100644
--- a/docs/CROWDIN/cs/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/cs/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Důležité poznámky
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Zkontrolujte verzi AAPS na telefonu
 
-After you installed the new apk, you can check the AAPS version on your phone by clicking the three dots menu on the top right and then About. You should see the current version.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![Nainstalovaná verze AAPS](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![Nainstalovaná verze AAPS](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/cs/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/cs/RemoteFeatures/RemoteControl.md
index 9e00f2fe3b4c..8e41dad699c2 100644
--- a/docs/CROWDIN/cs/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/cs/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ Pokud zvolíte Websockety (což je volitelné), ujistěte se, že jsou aktivová
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Uživatelé by měli zajistit, že jak __AAPSClient__, tak __AAPS__ zobrazují „připojeno“ na záložce „NSClient" a že lze přepnout 'Profil' nebo 'Dočasný cíl' správně aktivovat v __AAPS__ po jejich výběru v __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Uživatelé by měli také zajistit, že jsou sacharidy jsou zaznamenány v obou aplikacích na kartě „Ošetření“, jinak by to mohlo naznačovat chybu v uživatelském nastavení.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient a možnosti chytrých hodinek
 
-Chytré hodinky mohou být velmi užitečným nástrojem pro správu **AAPS** vašeho dítěte. K dispozici je několik možností. Je-li na telefonu rodičů nainstalován **AAPSClient**, lze na kompatibilní chytré hodinky připojené k rodičovskému telefonu nainstalovat [**AAPSClient WearOS aplikaci**](https://github.com/nightscout/AndroidAPS/releases/). Na hodinkách pak bude zoubrazována aktuální glykémiie, stav smyčky, a bude možné zadávat sacharidy, dočasné cíle a změny profilu. Z aplikace WearOS ale nebude možné posílat bolusy. You can read more about Smartwatches [here](#4-smartwatches).
+Chytré hodinky mohou být velmi užitečným nástrojem pro správu **AAPS** vašeho dítěte. K dispozici je několik možností. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. Na hodinkách pak bude zoubrazována aktuální glykémiie, stav smyčky, a bude možné zadávat sacharidy, dočasné cíle a změny profilu. Z aplikace WearOS ale nebude možné posílat bolusy. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/cs/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/cs/RemoteFeatures/RemoteMonitoring.md
index e4eea3dc842f..8f7a92883b71 100644
--- a/docs/CROWDIN/cs/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/cs/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitorování dětí](../images/KidsMonitoring.png)
 
-AAPS nabízí několik možností pro vzdálené monitorování dětí a také umožňuje odesílání vzdálených příkazů. Samozřejmě můžete také použít vzdálené monitorování, abyste sledovali svého partnera nebo přítele.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Funkce
 
-- Pumpa dítěte je řízena z telefonu dítěte používajícího AAPS.
-- Rodiče mohou vzdáleně sledovat všechny relevantní údaje jako např. hladiny glukózy, aktivní sacharidy aktivní inzulín atd. pomocí **aplikace AAPSClient** na svém telefonu. Nastavení v AAPS i AAPSClientu musí být stejné.
-- Rodiče mohou být na svém mobilu varováni alarmy v aplikaci **xDrip v režimu follower**.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Nástroje a aplikace pro vzdálené monitorování
 
 - [Nightscout](https://nightscout.github.io/) v prohlížeči (hlavně zobrazení dat)
-- Aplikace AAPSClient je zjednodušená verze AAPS, která umožňuje někoho sledovat, přepínat profily, nastavovat dočas. cíle a zadávat sacharidy. K dispozici ke stažení jsou 2 tyto aplikace:  [AAPSClient & AAPSClient2](https://github.com/nightscout/AndroidAPS/releases/). Jediný rozdíl mezi nimi spočívá v jiném názvu. Slouží k tomu, abyste mohli mít v telefonu dvě různé instance téže aplikace, pokud potřebujete sledovat 2 různé osoby/nightscouty.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. K dispozici ke stažení jsou 2 tyto aplikace:  [AAPSClient & AAPSClient2](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Dexcom follow, pokud používáte originální aplikaci Dexcom (pouze hodnoty glykémie)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) nebo [Spike](https://spike-app.com/) na iOS (hlavně hodnoty glykémií a **alarmy**)
@@ -23,13 +23,12 @@ AAPS nabízí několik možností pro vzdálené monitorování dětí a také u
 
 ## Možnosti chytrých hodinek
 
-Když máte děti, mohou být chytré hodinky velmi užitečným nástrojem pro ovládání AAPS. K dispozici je několik možností:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- Je-li na telefonu rodičů nainstalován AAPSClient, lze na kompatibilní chytré hodinky připojené k rodičovskému telefonu nainstalovat [aplikaci AAPSClient pro WearOS](https://github.com/nightscout/AndroidAPS/releases/). Na hodinkách pak bude zoubrazována aktuální glykémiie, stav smyčky, a bude možné zadávat sacharidy, dočasné cíle a změny profilu. Z aplikace WearOS ale nebude možné posílat bolusy.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. Takto lze využít všechny funkce popsané v předchozím případě, ale navíc lze posílat i bolusy. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. Z aplikace WearOS ale nebude možné posílat bolusy.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. Takto lze využít všechny funkce popsané v předchozím případě, ale navíc lze posílat i bolusy. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Co je třeba zvážit
 
-- Nastavení v AAPS i AAPSClientu musí být stejné.
-- Vezměte v úvahu časový rozdíl mezi hlavním a sledujícím zařízením způsobený časem potřebným k nahrávání a stahování, a také skutečnost, že hlavní AAPS telefon bude nahrávat pouze po spuštění smyčky.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/de/CompatibleCgms/Juggluco.md b/docs/CROWDIN/de/CompatibleCgms/Juggluco.md
index 4741e7884684..c38ee0c955b2 100644
--- a/docs/CROWDIN/de/CompatibleCgms/Juggluco.md
+++ b/docs/CROWDIN/de/CompatibleCgms/Juggluco.md
@@ -1,41 +1,41 @@
-# Juggluco settings
+# Juggluco Einstellungen
 
-If not already set up, then download [Juggluco](https://www.juggluco.nl/Juggluco/download.html).
+Sofern noch nicht eingerichtet, lade als erstes [Juggluco](https://www.juggluco.nl/Juggluco/download.html) herunter.
 
-Follow the [instructions](https://www.juggluco.nl/Jugglucohelp/introhelp.html) to connect your sensor.
+Um Deinen Sensor zu verbinden, führe diese [Einzelschritte](https://www.juggluco.nl/Jugglucohelp/introhelp.html) durch.
 
-## Basic settings for all CGM systems
+## Grundlegende Einstellungen für alle CGM-Systeme
 
-### Disable Nightscout uploader
+### Nightscout Upload ausschalten
 
 Ab der AAPS-Version 3.2, sollte neben AAPS keine andere App Daten (Glukosewerte und Behandlungsdaten) zu Nightscout hochladen.
 
-Disable any active uploader to Nightscout in Juggluco.
+Deaktiviere in Juggluco jeden aktiven Nightscout-Uploader.
 
 ![Disable Nightscout Upload](../images/juggluco/DisableNightscoutUpload.png)
 
 (juggluco-to-aaps)=
 
-## Juggluco to AAPS
+## Juggluco zu AAPS
 
-Juggluco can send blood glucose directly to AAPS, enabling SMBs always if you are using a [trusted sensor](#GettingStarted-TrustedBGSource).
+Juggluco kann Glukosewerte direkt an AAPS senden. Nutzt Du einen [vertrauenswürdigen Sensor](#GettingStarted-TrustedBGSource), kann die Option „SMB immer aktivieren“ eingeschaltet werden.
 
-When using a Libre 2/2+/3/3+ sensor, minute-by-minute readings will be sent to AAPS but will not trigger minute-by-minute calculations in AAPS.
+Die Sensoren Libre 2/2+/3/3+ senden jede Minute Messwerte an AAPS. Die Neuberechnungen in AAPS erfolgen dennoch nicht minütlich.
 
-Enable xDrip broadcast in Juggluco (do not enable Patched Libre), confirm and save the AAPS package information. Select the xDrip+ BG data source in AAPS.
+Aktiviere in Juggluco den xDrip+-Broadcast (nicht „Patched Libre“ aktivieren), bestätige und speicher die AAPS-Paketinformationen. Wähle xDrip+ in AAPS als BZ-Quelle aus.
 
-Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS.
+Stelle sicher, dass eine ausreichende [Glättung](./SmoothingBloodGlucoseData.md) der Werte in AAPS erfolgt.
 
-![Juggluco to AAPS](../images/juggluco/Juggluco-AAPS.png)
+![Juggluco zu AAPS](../images/juggluco/Juggluco-AAPS.png)
 
 (juggluco-to-xdrip)=
 
-## Juggluco to xDrip+
+## Juggluco zu xDrip+
 
-Juggluco can send blood glucose to xDrip+ which will then send them to AAPS.
+Juggluco kann Glukosewerte an xDrip+ schicken, die von da aus dann an AAPS gesendet werden.
 
-Enable Patched Libre in Juggluco (do not enable xDrip broadcast), confirm and save the dexdrip package information. Select the xDrip+ BG data source in AAPS.
+Aktiviere in Juggluco „Patched Libre“ (xDrip+-Broadcast nicht aktivieren), bestätige und speicher die Dexdrip-Paketinformationen. Wähle xDrip+ in AAPS als BZ-Quelle aus.
 
-Apply sufficient [smoothing](./SmoothingBloodGlucoseData.md) in AAPS if necessary, when using a Libre 2/2+/3/3+ sensor, xDrip+ will average the minute-by-minute to 5 minutes readings and [also smoothen](#libre2-value-smoothing-raw-values) them.
+Wenn nötig, sorge in AAPS für eine ausreichende [Glättung](./SmoothingBloodGlucoseData.md). Nutzt Du die Sensoren Libre 2/2+/3/3+, wird xDrip+ die minütlichen Glukosewerte auf 5 Minuten mitteln und auch [glätten](#libre2-value-smoothing-raw-values).
 
-![Juggluco to xDrip+](../images/juggluco/Juggluco-xDrip+.png)
+![Juggluco zu xDrip+](../images/juggluco/Juggluco-xDrip+.png)
diff --git a/docs/CROWDIN/de/CompatibleCgms/Libre3.md b/docs/CROWDIN/de/CompatibleCgms/Libre3.md
index 66d42c534f49..c7409405c43e 100644
--- a/docs/CROWDIN/de/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/de/CompatibleCgms/Libre3.md
@@ -13,7 +13,7 @@ Der Sensor kann in xDrip+ im Bereich von -40 mg/dl bis +20 mg/dl (-2.2 mmol/l bi
 ## Methode 1: Direkte Nutzung der minütlich übertragenen Sensorwerte
 AAPS ist auf „Sensorwerte alle 5 Minuten“ ausgelegt. Die Verarbeitung von minütlichen Werten bringt in einzelnen Situationen daher Einschränkungen mit sich.
 
-See [here](#juggluco-to-aaps).
+Schaue [hier](#juggluco-to-aaps) nach.
 
 
 ## Methode 2: Umwandlung in xDrip+ der minütlichen Messwerte in 5-Minuten-Werte
@@ -52,10 +52,10 @@ Nach einem Sensorwechsel erkennt xDrip+ den neuen Sensor automatisch und löscht
 
 ### Schritt 4: AndroidAPS konfigurieren
 
-- See [here](#juggluco-to-xdrip) and come back.
+- Lies [diesen Abschnitt](#juggluco-to-xdrip) und komme dann hierhin zurück.
 
 - Wenn sich das Smartphone im Flugmodus befindet und AAPS keine Glukosewerte erhält, verwende "Empfänger identifizieren"
-- Turn off Smoothing (done in xDrip+ already)
+- Glättung deaktivieren (in xDrip+ bereits erfolgt)
 
 ## Sensorwechsel
 
diff --git a/docs/CROWDIN/de/DailyLifeWithAaps/AapsScreens.md b/docs/CROWDIN/de/DailyLifeWithAaps/AapsScreens.md
index ea0692ab77cb..09d59a91bbae 100644
--- a/docs/CROWDIN/de/DailyLifeWithAaps/AapsScreens.md
+++ b/docs/CROWDIN/de/DailyLifeWithAaps/AapsScreens.md
@@ -58,8 +58,8 @@ Wenn Du den [SMB-Algorithmus](#Config-Builder-aps) und [Autosens](#Open-APS-feat
 
 Aktiviere eine oder beide der folgenden Optionen in [Einstellungen > OpenAPS SMB Einstellungen](#Preferences-openaps-smb-settings):
 
-     * "sensitivity raises target" and/or 
-     * "resistance lowers target" 
+     * „Empfindlichkeit erhöht den Zielwert“ und/oder 
+     * „Resistenz senkt den Zielwert" 
     
 
 Falls **AAPS** Resistenz oder Sensibilität erkennt, wird das aus dem Profil vorgegebene Ziel angepasst. Falls das Ziel geändert wird, wechselt der Hintergrund der Zielschaltfläche auf grün.
@@ -100,7 +100,7 @@ Auf der rechten Seite zeigt ein Symbol den Loop-Status an:
 3. Roter Kreis = Loop deaktiviert (dauerhaft)
 4. Roter Kreis = Loop ausgesetzt (vorübergehend pausiert, aber Basalinsulin wird weiter abgegeben) - verbleibende Zeit wird unter dem Symbol angezeigt
 5. Grauer Kreis = Pumpe getrennt (vorübergehend gar keine Insulinabgabe) - verbleibende Zeit wird unter dem Symbol angezeigt
-6. orangener Kreis = Superbolus läuft - verbleibende Zeit wird unterhalb des Symbols angezeigt
+6. Orangener Kreis = Superbolus läuft - verbleibende Zeit wird unterhalb des Symbols angezeigt
 7. Blue circle with dotted line = [open loop](#KeyAapsFeatures-OpenLoop)
 
 Drücke kurz oder lang auf das Icon um den Dialog zum Wechsel des Loop-Modus (Close loop, Low Glucose Suspend [Reduzierung der Basalrate bei niedrigen Glukosewerten], Open Loop, Abschalten), zum Pausieren / wieder Einschalten des Loop oder zum Trennen / erneuten Verbinden der Pumpe.
@@ -179,7 +179,7 @@ Ein Symbol mit einem Kindergesicht oben rechts in diesem Abschnitt zeigt, dass D
 
 2. **Grain**: [carbs on board (COB)](../DailyLifeWithAaps/CobCalculation.md) - yet unabsorbed carbs you have eaten before The icon pulses red if carbs are required (see [below](#aaps-screens-carbs-required))
 
-3. **Lila Linie**: current basal rate. Das Symbol verändert sich, um eine temporäre Basalrate zu zeigen (Standard ist 100%) 
+3. **Lila Linie**: aktuelle Basalrate. Das Symbol verändert sich, um eine temporäre Basalrate zu zeigen (Standard ist 100%) 
   * Klicke auf das Icon um Details zur Basalrate und einer eventuellen temporären Basalrate (inkl. verbleibende Dauer) angezeigt zu bekommen.
 4. **Pfeile nach oben & unten**: zeigen den aktuellen [Autosens](#Open-APS-features-autosens)-Status bzw. den Status des [dynamischen ISF](#Open-APS-features-DynamicISF) (aktiviert oder deaktiviert) an. In diesem Abschnitt können mehrere Werte angezeigt werden: 
   * AS: Autosens-Wert. Wird auch dann angezeigt, wenn Autosens deaktiviert ist (rein informatorisch). Wird auch angezeigt, wenn DynISF aktiviert ist und ohne Wirkung ist.
diff --git a/docs/CROWDIN/de/DailyLifeWithAaps/Automations.md b/docs/CROWDIN/de/DailyLifeWithAaps/Automations.md
index 8ce31e40198b..dde5f6a10753 100644
--- a/docs/CROWDIN/de/DailyLifeWithAaps/Automations.md
+++ b/docs/CROWDIN/de/DailyLifeWithAaps/Automations.md
@@ -179,7 +179,7 @@ Beachte, dass für alle altersbezogenen Bedingungen der Vergleich auf Gleichheit
 * Pumpenbatterie-Stand: Für alle unterstützen Pumpen verfügbar, der Vergleich „NOT\_AVAILABLE“ funktioniert für diesen Auslöser nicht, da der Wert in **AAPS** immer gefüllt ist
 
 (automations-automation-action)=
-## Aktion
+## Action
 
 ![Automation Actions](../images/automation_actions.png)
 
diff --git a/docs/CROWDIN/de/DailyLifeWithAaps/KeyAapsFeatures.md b/docs/CROWDIN/de/DailyLifeWithAaps/KeyAapsFeatures.md
index 95287cc7f6dd..5321d1982f7f 100644
--- a/docs/CROWDIN/de/DailyLifeWithAaps/KeyAapsFeatures.md
+++ b/docs/CROWDIN/de/DailyLifeWithAaps/KeyAapsFeatures.md
@@ -1,6 +1,6 @@
 # Wichtigste AAPS-Funktionalitäten
 
-## Loop mode
+## Loop-Modus
 
 The loop status is shown on the main screen with one of the icons below.
 
diff --git a/docs/CROWDIN/de/Getting-Started/Introduction.md b/docs/CROWDIN/de/Getting-Started/Introduction.md
index b122e27d66d6..0d96d5f14d42 100644
--- a/docs/CROWDIN/de/Getting-Started/Introduction.md
+++ b/docs/CROWDIN/de/Getting-Started/Introduction.md
@@ -39,7 +39,7 @@ Diverse kommerzielle Hybrid-Closed-Loop-Systeme wurden auf den Markt gebracht, z
 
 Android APS (**AAPS**) ist ein Hybrid-Closed-Loop-System oder eine "künstliche Bauchspeicheldrüse" (Artificial Pancreas System = APS). Es berechnet benötigte Insulinmengen, indem es bewährte [OpenAPS](https://openaps.org/)-Algorithmen (Berechnungsvorschriften) verwendet, die von der #WeAreNotWaiting Typ 1 Diabetes Community entwickelt wurden.
 
-Da OpenAPS nur mit bestimmten älteren Insulinpumpen kompatibel ist, wurde **AAPS** (das mit einer breiteren Palette von Insulinpumpen verwendet werden kann) 2016 von Milos Kozak für ein Familienmitglied mit Typ-1-Diabetes entwickelt. Seit diesen frühen Tagen wurde **AAPS** durch ein Team von freiwilligen Computerentwicklern und anderen Enthusiasten kontinuierlich weiterentwickelt und verfeinert. Viele dieser Personen haben einen Bezug zur Welt des Typ-1-Diabetes. Today, **AAPS** is used by approximately 20,000 people. Das System ist sehr flexibel und anpassbar. Dadurch, dass es System Open-Source ist, ist es auch problemlos mit viel anderer Open-Source-Diabetes Software und vielen Plattformen kompatibel. Die grundlegenden Komponenten des gegenwärtigen **AAPS**-Systems werden oben in **Bild 1** dargestellt.
+Da OpenAPS nur mit bestimmten älteren Insulinpumpen kompatibel ist, wurde **AAPS** (das mit einer breiteren Palette von Insulinpumpen verwendet werden kann) 2016 von Milos Kozak für ein Familienmitglied mit Typ-1-Diabetes entwickelt. Seit diesen frühen Tagen wurde **AAPS** durch ein Team von freiwilligen Computerentwicklern und anderen Enthusiasten kontinuierlich weiterentwickelt und verfeinert. Viele dieser Personen haben einen Bezug zur Welt des Typ-1-Diabetes. Heute wird **AAPS** von rund 20.000 Personen genutzt. Das System ist sehr flexibel und anpassbar. Dadurch, dass es System Open-Source ist, ist es auch problemlos mit viel anderer Open-Source-Diabetes Software und vielen Plattformen kompatibel. Die grundlegenden Komponenten des gegenwärtigen **AAPS**-Systems werden oben in **Bild 1** dargestellt.
 
 
 
@@ -87,7 +87,7 @@ Es gibt mehrere mögliche Überwachungskanäle (Sugarmate, Dexcom Follow, xDrip+
 Ein bedeutender Vorteil von **AAPS** gegenüber kommerziellen Systemen ist, dass es für Follower möglich ist, über authentifizierte Texte (SMS) Befehle oder über eine App ([Nachtscout](https://nightscout.github.io/) oder AAPSClient), um eine große Anzahl von Befehlen an das **AAPS** System zurückzuschicken. Das ist eine der durch Eltern von Typ-1 Kindern am häufigsten genutzte Funktionalität in AAPS. Es ist sehr nützlich: zum Beispiel auf dem Spielplatz. Wenn Du einen Snack von Deinem eigenen Telefon aus für einen Vorab-Bolus machen willst, und Dein Kind ins Spielen vertieft ist. Das System kann überwacht werden (_z. B._ Fitbit), grundlegende Befehle senden (_z. B._ Samsung Galaxy Watch 4), oder das gesamte AAPS System kann über eine leistungsstarke Smartwatch (**5**) (_z. B._ LEMFO) vollständig gesteuert werden. In diesem letzten Szenario ersetzt die Full-Android-Smartwatch das Smartphone. Mit zunehmender Batteriekapazität und zuverlässigerer Technik der Smartwatches wird diese Option auch immer attraktiver.
 
 #### 6) **Keine kommerziellen Einschränkungen aufgrund der offenen Anwendungsschnittstellen**
-Über die Verwendung eines Open-Source-Ansatzes hinaus kann der Quellcode von **AAPS** jederzeit eingesehen werden, was das allgemeine Prinzip der Bereitstellung offener Programmierschnittstellen ist. Dies gibt anderen Entwicklern die Möglichkeit, ebenfalls neue Ideen einzubringen. **AAPS** ist eng in Nightscout integriert. Dies beschleunigt die Entwicklung und ermöglicht es den Anwendern, Funktionen hinzuzufügen, um das Leben mit Diabetes noch einfacher zu machen. Good examples for such integrations are [Nightscout](https://nightscout.github.io/), [Nightscout Reporter](https://nightscout-reporter.zreptil.de/), xDrip+, [M5 stack](https://github.com/mlukasek/M5_NightscoutMon/wiki) etc. Es besteht ein ständiger Dialog zwischen Open-Source-Entwicklern und den Entwicklern kommerzieller Systeme. Viele der DIY-Innovationen werden schrittweise von kommerziellen Systemen übernommen, wo die Entwicklungen verständlicherweise langsamer sind. Auch weil Schnittstellen zwischen Systemen verschiedener Unternehmen (Pumpen, Apps, Sensoren _usw._) sorgfältig ausgehandelt und lizenziert werden müssen. Dies kann auch Innovationen verlangsamen die für den einzelnen Patienten bequem sind (oder für eine kleine Untergruppe von Patienten mit sehr spezifischen Anforderungen), die aber keinen großen finanziellen Gewinn bringen.
+Über die Verwendung eines Open-Source-Ansatzes hinaus kann der Quellcode von **AAPS** jederzeit eingesehen werden, was das allgemeine Prinzip der Bereitstellung offener Programmierschnittstellen ist. Dies gibt anderen Entwicklern die Möglichkeit, ebenfalls neue Ideen einzubringen. **AAPS** ist eng in Nightscout integriert. Dies beschleunigt die Entwicklung und ermöglicht es den Anwendern, Funktionen hinzuzufügen, um das Leben mit Diabetes noch einfacher zu machen. Gute Beispiele für solche Integrationen sind [Nightscout](https://nightscout.github.io/), [Nightscout Reporter](https://nightscout-reporter.zreptil.de/), xDrip+, [M5 Stack](https://github.com/mlukasek/M5_NightscoutMon/wiki) usw. Es besteht ein ständiger Dialog zwischen Open-Source-Entwicklern und den Entwicklern kommerzieller Systeme. Viele der DIY-Innovationen werden schrittweise von kommerziellen Systemen übernommen, wo die Entwicklungen verständlicherweise langsamer sind. Auch weil Schnittstellen zwischen Systemen verschiedener Unternehmen (Pumpen, Apps, Sensoren _usw._) sorgfältig ausgehandelt und lizenziert werden müssen. Dies kann auch Innovationen verlangsamen die für den einzelnen Patienten bequem sind (oder für eine kleine Untergruppe von Patienten mit sehr spezifischen Anforderungen), die aber keinen großen finanziellen Gewinn bringen.
 
 #### 7) **Detaillierte App-Oberfläche**
 Mit **AAPS** ist es einfach Dinge wie Insulinstände in der Pumpe, Alter des Katheters, Sensoralter, Pumpenbatterie, Insulin-On-Bord _usw._. Viele Aktionen können durch die **AAPS** App durchgeführt werden (Füllen der Pumpe, Abschalten der Pumpe _etc._), anstatt an der Pumpe selbst, was bedeutet, dass die Pumpe in der Tasche oder am Gürtel bleiben kann.
@@ -218,7 +218,7 @@ Frage Dein Team, ob es bereits Patienten in Behandlung hat, die DIY-Looping verw
 
 Wenn Du das Gefühl hast, dass Du von Deinem Team beim Loopen mit **AAPS** nicht genügend unterstützt wirst, können folgende Diskussionspunkte hilfreich sein:
 
-a) Das **AAPS** System wurde von Patienten und deren Betreuern entworfen. Es wurde letztendlich für die Sicherheit konzipiert, aber auch auf Grundlage einer fundierten Patientenerfahrung. There are currently around **20,000** AAPS users worldwide. Es ist daher wahrscheinlich, dass es in Deiner Klinik weitere Patienten gibt, die DIY-Looping verwenden (ob sie gegenseitig davon wissen oder nicht).
+a) Das **AAPS** System wurde von Patienten und deren Betreuern entworfen. Es wurde letztendlich für die Sicherheit konzipiert, aber auch auf Grundlage einer fundierten Patientenerfahrung. Derzeit gibt es weltweit rund **20.000** AAPS-Nutzende. Es ist daher wahrscheinlich, dass es in Deiner Klinik weitere Patienten gibt, die DIY-Looping verwenden (ob sie gegenseitig davon wissen oder nicht).
 
 b) Eine kürzlich in der international führenden medizinischen Fachzeitschrift [The Lancet](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/pdf/nihms-1765784.pdf)_(1)_ veröffentlichte und von Experten begutachtete Anleitung hat bestätigt, dass DIY-Loops **sicher** und **wirksam bei der Verbesserung der Diabeteskontrolle** sind, einschließlich der Zeit im Zielbereich (engl. time in range = TIR). Es gibt regelmäßige Artikel in führenden Zeitschriften wie [Nature](https://doi.org/10.1038/d41586-023-02648-9)_(3)_ die den Fortschritt in der DIY-Looping-Commmunity hervorheben.
 
@@ -321,7 +321,7 @@ David Burren [https://bionicwookie.com/](https://bionicwookie.com/)
 
 Die obige Tabelle setzt voraus, dass die Nutzenden sowohl Zugang zu einem CGM-System und auch zu einer Insulinpumpe haben.
 
-*Alle Daten von **AAPS** können medizinischen Fachkräften über Datenaustauschplattformen zur Verfügung gestellt werden, einschließlich Nightscout, das die Aufzeichnung und Echtzeitüberwachung von CGM-Daten, Insulinabgabe, Kohlenhydratangaben, Prognosen und Einstellungen ermöglicht. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioral considerations.
+*Alle Daten von **AAPS** können medizinischen Fachkräften über Datenaustauschplattformen zur Verfügung gestellt werden, einschließlich Nightscout, das die Aufzeichnung und Echtzeitüberwachung von CGM-Daten, Insulinabgabe, Kohlenhydratangaben, Prognosen und Einstellungen ermöglicht. Aus Nightscout können Tages- und Wochenberichte erzeugt werden, die in Diskussionen eines Diabetes-Teams mit einem Typ 1-Patienten hilfreich sein können, da sie genauere Daten zur glykämischen Kontrolle und Verhaltensüberlegungen beisteuern.
 
 (accessibility-for-users-aaps-who-are-partially-or-completely-blind)=
 
@@ -331,7 +331,7 @@ Die obige Tabelle setzt voraus, dass die Nutzenden sowohl Zugang zu einem CGM-Sy
 AAPS kann von Blinden verwendet werden. Auf Android-Geräten stellt das Betriebssystem ein Programm namens TalkBack zur Verfügung. Dies ermöglicht die Bildschirmorientierung über die Sprachausgabe als Teil des Betriebssystems. Mit TalkBack kannst Du sowohl Dein Smartphone als auch AAPS bedienen, ohne dass Du es sehen musst.
 
 #### Das Erstellen der AAPS-App:
-Als Benutzer wirst Du die AAPS-App in Android Studio erstellen. Many people use Microsoft Windows for this purpose, where there is the screen reader analogous to TalkBack. Da Android Studio eine Java-Anwendung ist, muss die Komponente "Java Access Bridge" in der Systemsteuerung aktiviert werden. Andernfalls wird der Screenreader des PCs nicht in Android Studio sprechen.
+Als Benutzer wirst Du die AAPS-App in Android Studio erstellen. Zu diesem Zweck verwenden viele Microsoft Windows, wo es den Screenreader analog zu TalkBack gibt. Da Android Studio eine Java-Anwendung ist, muss die Komponente "Java Access Bridge" in der Systemsteuerung aktiviert werden. Andernfalls wird der Screenreader des PCs nicht in Android Studio sprechen.
 
 Wie Du das machst, hängt von Deinem Betriebssystem ab. Zwei Methoden sind nachfolgend aufgeführt:
 
diff --git a/docs/CROWDIN/de/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/de/Maintenance/UpdateToNewVersion.md
index d201947fa6ed..5945999238db 100644
--- a/docs/CROWDIN/de/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/de/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@ Aufgrund der gesetzlichen Regelungen für Medizinprodukte ist **AAPS** nicht als
 
 ## Wichtige Hinweise
 
-* Aktualisiere so bald wie möglich auf die neueste **AAPS**-Version, nachdem sie verfügbar ist.
-* Sobald eine neue Version verfügbar ist, wird Dir in der **AAPS**-App ein Hinweis darüber angezeigt.
-* Wenn eine neue Version verfügbar ist, wird darüber auch auf Facebook informiert.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Aktualisiere so bald wie möglich auf die neueste **AAPS**-Version, nachdem sie verfügbar ist.
+- Sobald eine neue Version verfügbar ist, wird Dir in der **AAPS**-App ein Hinweis darüber angezeigt.
+- Wenn eine neue Version verfügbar ist, wird darüber auch auf Facebook informiert.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### AAPS-Version auf dem Smartphone überprüfen
 
-Nachdem Du die neue APK-Datei installiert hast, kannst Du auf dem Smartphone die Version prüfen. Gehe dazu oben rechts auf die drei Punkte und wähle dann "Über". Du solltest die aktuelle Version angezeigt bekommen.
+Schaue in den [Release Notes](../Maintenance/ReleaseNotes.md) nach, ob es nach dem Update besondere Dinge zu beachten gibt.
 
-![Installierte AAPS Version](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Schaue in den [Release Notes](../Maintenance/ReleaseNotes.md) nach, ob es nach dem Update besondere Dinge zu beachten gibt.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![Installierte AAPS Version](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/de/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/de/RemoteFeatures/RemoteControl.md
index 1dbed76075aa..2851b8f85116 100644
--- a/docs/CROWDIN/de/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/de/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ Wenn Du die optionale Funktion 'Mit Websockets verbinden' auswählst, achte dara
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Achte darauf, dass sowohl der __AAPSClient__ als auch __AAPS__ auf dem Reiter „NSClient“ für jedes der Smartphones „verbunden“ anzeigt und dass bei Auswahl eines „Profilwechsel“ oder „Temporäres Ziel“ im  __AAPSClient__ dieses auch in __AAPS__ korrekt aktiviert wird.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Achte auch darauf, dass Kohlenhydrat-Eingaben, sowohl im __AAPSClient__ als auch in __AAPS__ unter 'Behandlungen" erscheinen. Passiert das nicht, ist das ein Hinweis darauf, dass die Einstellungen nicht richtig sind.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Das 'NS access token'-Konfigurationsproblem beheben
 
@@ -110,7 +110,7 @@ Eine Remote-Steuerung über die **AAPSClient**-App wird nur dann empfohlen, wenn
 
 ### AAPSClient mit Smartwatch-Optionen
 
-Eine Smartwatch kann sehr nützlich sein, um bei Kindern **AAPS** zu managen. Es sind einige verschiedene Konfigurationen möglich. Auf einer kompatiblen Smartwatch kann die [AAPSClient WearOS App](https://github.com/nightscout/AndroidAPS/releases/) installiert werden, die mit der AAPSClient-App auf dem Eltern-Smartphone verbunden wird. Damit können der aktuelle Glukosewert und der Loop-Status angezeigt werden. Zusätzlich können dann KH-Einträge vorgenommen werden und auch temporäre Ziele und Profiländerungen aktiviert werden. Die Abgabe eines Bolus ist NICHT über die WearOS App möglich. [Hier](#4-smartwatches) kannst Du mehr über Smartwatches erfahren.
+Eine Smartwatch kann sehr nützlich sein, um bei Kindern **AAPS** zu managen. Es sind einige verschiedene Konfigurationen möglich. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. Damit können der aktuelle Glukosewert und der Loop-Status angezeigt werden. Zusätzlich können dann KH-Einträge vorgenommen werden und auch temporäre Ziele und Profiländerungen aktiviert werden. Die Abgabe eines Bolus ist NICHT über die WearOS App möglich. [Hier](#4-smartwatches) kannst Du mehr über Smartwatches erfahren.
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/de/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/de/RemoteFeatures/RemoteMonitoring.md
index 6e90b49c8628..08c7589a1abf 100644
--- a/docs/CROWDIN/de/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/de/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Überwachung von Kindern](../images/KidsMonitoring.png)
 
-Es gibt einige Möglichkeiten (z. B. mit SMS-Befehlen), AAPS fernsteuern zu können. Natürlich kann mittels Remote Monitoring auch der Partner oder Freund unterstützt werden.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Funktionen
 
-- Die Pumpe des Kindes wird vom Smartphone des Kindes durch AAPS gesteuert.
-- Die Eltern können remote alle relevanten Daten wie Glukosewerte, aktive Kohlenhydrate, aktives Insulin usw. sehen. Dazu können sie die **AAPSClient App** auf ihrem Smartphone verwenden. Verwende in AAPS und der AAPSClient App die gleichen Einstellungen.
-- Alarme auf den Smartphones der Eltern sind durch Einsatz **xDrip+ im Follower Modus** möglich.
-- Die Fernsteuerung von AAPS mit [SMS-Befehlen](../RemoteFeatures/SMSCommands.md) ist durch eine Zwei-Faktor-Authentifizierung abgesichert.
-- Remote-Steuerung über die AAPSClient-App wird nur empfohlen, wenn Deine Synchronisation gut funktioniert (d.h. Du siehst keine unerwünschten Datenänderungen wie z.B. Selbstmodifikation von TT, TBR usw.) siehe [Versionshinweise für Version 2.8.1.1](#important-hints-2-8-1-1) für weitere Details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Tools und Apps für die Fernüberwachung
 
 - [Nightscout](https://nightscout.github.io/) im Webbrowser (vor allem Datenanzeige)
-- Die AAPSClient-App ist eine reduzierte AAPS-Version mit der Du jemandem folgen, Profilwechsel vornehmen, TT setzen und Kohlenhydrate eingeben kannst. Die beiden Apps AAPSClient & AAPSClient2 können [direkt heruntergeladen](https://github.com/nightscout/AndroidAPS/releases/) werden. Einziger Unterschied ist der App-Name. Dadurch kannst du die App zwei Mal auf dem gleichen Smartphone installieren, wenn du zwei verschiedenen Personen bzw. Nightscout-Instanzen folgen willst.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. Die beiden Apps AAPSClient & AAPSClient2 können [direkt heruntergeladen](https://github.com/nightscout/AndroidAPS/releases/) werden. AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Dexcom Follow App zusammen mit der originalen Dexcom App (nur BZ-Werte)
 - [xDrip+](../CompatibleCgms/xDrip.md) im Follower-Modus (hauptsächlich Glukosewerte und **Alarme**)
 - [Sugarmate](https://sugarmate.io/) oder [Spike](https://spike-app.com/) für iOS (vor allem BZ-Werte und **Alarme**)
@@ -23,13 +23,12 @@ Es gibt einige Möglichkeiten (z. B. mit SMS-Befehlen), AAPS fernsteuern zu kön
 
 ## Smartwatch-Optionen
 
-Eine Smartwatch kann die AAPS-Steuerung speziell mit Kindern vereinfachen. Es sind einige verschiedene Konfigurationen möglich:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- Auf einer kompatiblen Smartwatch kann die [AAPSClient WearOS App](https://github.com/nightscout/AndroidAPS/releases/) installiert werden, die mit der AAPSClient App auf dem Eltern-Smartphone verbunden wird. Damit können der aktuelle Glukosewert und der Loop-Status angezeigt werden. Zusätzlich können dann KH-Einträge vorgenommen werden und auch temporäre Ziele und Profiländerungen aktiviert werden. Die Abgabe eines Bolus ist NICHT über die WearOS App möglich.
-- Alternativ kann die [AAPS WearOS-App](../WearOS/WearOsSmartwatch.md) erstellt und auf einer kompatiblen Smartwatch installiert werden. Die App ist zwar mit der Smartwatch des Kindes verbunden, aber die Smartwatch selbst wird nicht durch ein Elternteil getragen. Damit sind dann alle Funktionen der oben beschriebenen NSClient-Version (Smatwatch) verfügbar und zusätzlich die Abgabe eines Bolus möglich. Damit kann ein Elternteil einen Bolus abgeben, ohne an das in Reichweite befindliche Smartphone des Kindes zu müssen.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. Die Abgabe eines Bolus ist NICHT über die WearOS App möglich.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. Damit sind dann alle Funktionen der oben beschriebenen NSClient-Version (Smatwatch) verfügbar und zusätzlich die Abgabe eines Bolus möglich. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Dinge, die zu beachten sind
 
-- Verwende in AAPS und der AAPSClient App die gleichen Einstellungen.
-- Diese entsteht zum einen durch die Zeit, die für Up- und Download benötigt wird, zum anderen lädt das AAPS-Haupttelefon nur Daten hoch, wenn es eine Aktivität des Closed Loop auf dem Smartphone gab.
-- Wie sieht der Notfallplan aus, wenn die Fernsteuerung nicht funktionieren sollte (_d.h._ Netzwerkprobleme auftreten oder die Bluetooth-Verbindung verloren geht)?  Denke immer daran, was mit **AAPS** passieren wird, wenn Du plötzlich keine neuen Befehle senden kannst. **AAPS** überschreibt die Basalrate, den ISF und das ICR mit den aktuellen Profilwerten. Falls Deine Remote-Verbindung unterbrochen wird, ist es ist besser temporäre Profilwechsel (_d.h._ mit einer beschränkten Dauer) genutzt zu haben, als auf ein dauerhaftes stärkeres Insulinprofil geschwechselt zu sein. Wenn Die eingegebene Zeitspanne abgelaufen ist, wird die Pumpe auf das Original-Profil zurückfallen.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- Wie sieht der Notfallplan aus, wenn die Fernsteuerung nicht funktionieren sollte (_d.h._ Netzwerkprobleme auftreten oder die Bluetooth-Verbindung verloren geht)?  Denke immer daran, was mit **AAPS** passieren wird, wenn Du plötzlich keine neuen Befehle senden kannst. **AAPS** überschreibt die Basalrate, den ISF und das ICR mit den aktuellen Profilwerten. Falls Deine Remote-Verbindung unterbrochen wird, ist es ist besser temporäre Profilwechsel (_d.h._ mit einer beschränkten Dauer) genutzt zu haben, als auf ein dauerhaftes stärkeres Insulinprofil geschwechselt zu sein. Wenn Die eingegebene Zeitspanne abgelaufen ist, wird die Pumpe auf das Original-Profil zurückfallen.
diff --git a/docs/CROWDIN/de/SettingUpAaps/CompletingTheObjectives.md b/docs/CROWDIN/de/SettingUpAaps/CompletingTheObjectives.md
index 7928f9755edb..576d8fbb89cb 100644
--- a/docs/CROWDIN/de/SettingUpAaps/CompletingTheObjectives.md
+++ b/docs/CROWDIN/de/SettingUpAaps/CompletingTheObjectives.md
@@ -114,7 +114,7 @@ Im **Ziel 5**, wirst Du kennen- und verstehen lernen, wie sich die temporären B
 
 Um das Ziel abzuschließen, werden ungefähr **7 Tage ** benötigt.
 
-In diesem **Ziel** musst Du Deinen Wert für „Maximales Basal-IOB, das OpenAPS abgeben darf \[IE\] (OpenAPS “max-iob”)“, wie es im Abschnitt [OpenAPS Funktionen](#Open-APS-features-max-u-h-a-temp-basal-can-be-set-to) beschrieben ist, ermitteln. This value can be set in [Preferences > OpenAPS SMB](#Preferences-openaps-smb-settings). Wenn Du an dieser stelle noch eine virtuelle Pumpe nutzt, stelle sicher, dass diese Sicherheitseinstellung sowohl in **AAPS**, als auch in Deiner Insulinpumpe eingestellt ist.
+In diesem **Ziel** musst Du Deinen Wert für „Maximales Basal-IOB, das OpenAPS abgeben darf \[IE\] (OpenAPS “max-iob”)“, wie es im Abschnitt [OpenAPS Funktionen](#Open-APS-features-max-u-h-a-temp-basal-can-be-set-to) beschrieben ist, ermitteln. Diesen Wert kannst Du in den [Einstellungen > OpenAPS SMB](#Preferences-openaps-smb-settings) festlegen. Wenn Du an dieser stelle noch eine virtuelle Pumpe nutzt, stelle sicher, dass diese Sicherheitseinstellung sowohl in **AAPS**, als auch in Deiner Insulinpumpe eingestellt ist.
 
 Eventuell setzt Du, bis Du mit den **AAPS**-Berechnungen und Einstellungen zufrieden bist, in Deinem [**Profil** ein Glukosewert-Ziel](#profile-glucose-targets), das über Deinem üblichen Ziel liegt. Möglicherweise möchtest Du mit der Anpassung Deines **Glukosewert-Ziels** experimientieren und in Deinem **Profil** einen engeren Bereich (z.B. 1 oder weniger mmol/l [20 mg/dl oder weniger]) hinterlegen und beobachten, wie sich das auswirkt.
 
@@ -165,11 +165,11 @@ Das heißt, während Du Dich im **Ziel 6** befindest, wird **AAPS** bei fallende
 (objectives-objective7)=
 ## Ziel 7: Justiere den Closed Loop, erhöhe maxIOB über 0 und setze den Zielbereich langsam herunter
 
-Um **Ziel 7** abzuschließen, musst Du den Loop schließen (Closed Loop) und Deinen [maxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)-Wert erhöhen. **maxIOB** was zeroed out automatically in **Objective 6**, due to the Low Glucose Suspend mode. This is no longer the case. **AAPS** wird ab jetzt Deinen hinterlegten maxIOB-Wert nutzen, um hohe Glukosewerte zu korrigieren.
+Um **Ziel 7** abzuschließen, musst Du den Loop schließen (Closed Loop) und Deinen [maxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)-Wert erhöhen. **maxIOB** was zeroed out automatically in **Objective 6**, due to the Low Glucose Suspend mode. Das ist jetzt nicht mehr nötig. **AAPS** wird ab jetzt Deinen hinterlegten maxIOB-Wert nutzen, um hohe Glukosewerte zu korrigieren.
 
 Das Ziel kann frühestens nach **einem Tag** abgeschlossen werden. Das ist eine Pflichtwartezeit. Das nächste **Ziel** kann erst dann gestartet werden, wenn die Wartezeit abgelaufen ist.
 
-- Select **Closed Loop** by pressing and holding the [Loop icon](#AapsScreens-loop-status) in the top right corner of the **Overview** screen. Bleibe einen Tag im **Closed Loop**-Modus.
+- Aktiviere den **Closed Loop** dadurch, dass Du länger auf das [Loop-Symbol](#AapsScreens-loop-status) in der oberen rechten Ecke der **ÜBERSICHT** drückst. Bleibe einen Tag im **Closed Loop**-Modus.
 
 - 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.
 
diff --git a/docs/CROWDIN/de/SupportingAaps/HowCanIHelp.md b/docs/CROWDIN/de/SupportingAaps/HowCanIHelp.md
index 6b6380f67bb4..5780708c0fa5 100644
--- a/docs/CROWDIN/de/SupportingAaps/HowCanIHelp.md
+++ b/docs/CROWDIN/de/SupportingAaps/HowCanIHelp.md
@@ -15,7 +15,7 @@ Juhuu! Schau dir die Issues an, frag im discord Channel. Es gibt immer viel zu t
 Großartig, das ist sehr willkommen und eine gute Möglichkeit, etwas beizutragen!
 
 * Den discord Channel über das Wiki findest du hier: [AndroidAPSwiki/Lobby](https://discord.gg/4fQUWHZ4Mw). 
-* Eine Anleitung, wie man Beiträge auf Englisch hinzufügt und bearbeitet, ist hier zu finden: [Wie man die Dokumentation bearbeitet](../SupportingAaps/HowToEditTheDocs.md). Other languages are only translated from English and can't be edited for consistency reasons.
+* Eine Anleitung, wie man Beiträge auf Englisch hinzufügt und bearbeitet, ist hier zu finden: [Wie man die Dokumentation bearbeitet](../SupportingAaps/HowToEditTheDocs.md). Andere Sprachen können nur übersetzt, aber nicht bearbeitet werden. Dadurch wird die Einheitlichkeit des Wikis in allen Sprachen gewährleistet.
 
 ## Ich spreche mehrere Sprachen und würde gerne bei der Übersetzung der App bzw. des Wikis helfen
 
diff --git a/docs/CROWDIN/de/index.md b/docs/CROWDIN/de/index.md
index eb3fbd701b92..147651f5533d 100644
--- a/docs/CROWDIN/de/index.md
+++ b/docs/CROWDIN/de/index.md
@@ -5,7 +5,7 @@
 ```{admonition} Latest Release
 :class: note
 
-31/12/2025: Version 3.4 ist nun verfügbar. Check the [Release Notes](#latestrelease) to see what's new and get update instructions.
+31/12/2025: Version 3.4 ist nun verfügbar. Schau Dir die [Release Notes](#latestrelease) an, in denen Du erfährst welche Neuerungen es gibt und was es bei einem Update zu beachten gibt.
 
 ```
 
@@ -21,7 +21,7 @@ Abschnitt **2) „Erste Schritte“** - Die [Einführung](Getting-Started/Introd
 
 Jetzt, da Du ein solides Grundverständnis des Prozesses hast, kannst Du damit beginnen, Deinen **AAPS**-Loop zu erstellen.
 
-Abschnitt **3) AAPS einrichten** enthält Schritt-für-Schritt Anleitungen, um dies zu tun. It covers choosing and [setting up your reporting server](./SettingUpAaps/SettingUpTheReportingServer.md) (Nightscout or Tidepool) so you can review and share your data, getting ready for building the AAPS app, building the AAPS app and transferring the AAPS app to your phone. Es umfasst auch das Einrichten der **AAPS**-App mithilfe des Einrichtungsassistenten, das Verknüpfen mit Deiner CGM-App und entweder einer echten oder einer virtuellen Insulinpumpe sowie das Verknüpfen von **AAPS** mit Deinem Berichtsserver. Du wirst danach durch einen kleinschrittigen und sehr fein justierten Prozess sehr behutsam an die vollständige **AAPS**-Nutzung herangeführt. Damit soll sichergestellt werden, dass Du oder Dein Kind, sicher durch die verschiedenen Funktionen und Menü-Konfigurationen navigieren lernst, bevor Du zur folgenden Phase (auch "nächstes Ziel" bzw. "Objective" genannt) übergehst und schließlich genug Erfahrung gesammelt hast, um die weitreichensten Funktionalitäten der App nutzen zu können. Diese Objectives (Ziele) sind so aufgebaut, dass nach und nach weitere **AAPS**-Funktionen freigeschaltet werden und so am Ende vom 'Open Loop' auf 'Closed Loop' umgestellt werden kann.
+Abschnitt **3) AAPS einrichten** enthält Schritt-für-Schritt Anleitungen, um dies zu tun. Er beschreibt die Auswahl und [Einrichtung Deines Servers für Berichte](./SettingUpAaps/SettingUpTheReportingServer.md) (Nightscout oder Tidepool), damit Du Deine relevanten Daten auswerten und teilen kannst, die Vorbereitung für die Erstellung, das eigentliche Erstellen (sog. Build) der AAPS-App und die Übertragung der AAPS-App auf Dein Smartphone. Es umfasst auch das Einrichten der **AAPS**-App mithilfe des Einrichtungsassistenten, das Verknüpfen mit Deiner CGM-App und entweder einer echten oder einer virtuellen Insulinpumpe sowie das Verknüpfen von **AAPS** mit Deinem Berichtsserver. Du wirst danach durch einen kleinschrittigen und sehr fein justierten Prozess sehr behutsam an die vollständige **AAPS**-Nutzung herangeführt. Damit soll sichergestellt werden, dass Du oder Dein Kind, sicher durch die verschiedenen Funktionen und Menü-Konfigurationen navigieren lernst, bevor Du zur folgenden Phase (auch "nächstes Ziel" bzw. "Objective" genannt) übergehst und schließlich genug Erfahrung gesammelt hast, um die weitreichensten Funktionalitäten der App nutzen zu können. Diese Objectives (Ziele) sind so aufgebaut, dass nach und nach weitere **AAPS**-Funktionen freigeschaltet werden und so am Ende vom 'Open Loop' auf 'Closed Loop' umgestellt werden kann.
 
 Abschnitt **4) AAPS im Alltag** behandelt wichtige **AAPS**-Funktionen, um Dir beim Umgang (und der Anpassung) von **AAPS** zu helfen. Dies beinhaltet insbesondere das Verständnis der Bildschirme, Kohlenhydrate an Bord (CoB), Sensitivität, Profilwechsel, temporäre Ziele, verzögerte Kohlenhydrate (oder eCarbs), Automatisierungen und dynamischer ISF (DynamicISF). Es behandelt auch häufige Themen wie den Umgang mit verschiedenen Mahlzeitenarten den Umgang mit Kanülen- und Sensorwechseln, Smartphone-Updates, Zeitumstellungen, [Reisen mit AAPS](DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md) und Sport. Häufig gestellte Fragen und Antworten dazu findest Du im Abschnitt zur Fehlerbehebung.
 
@@ -84,21 +84,21 @@ Komponentenübersicht <./Getting-Started/ComponentOverview.md>
 ```
 
 ```{toctree}
-:caption: 3) Setting up AAPS
+:caption: 3) AAPS
 
-Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
+Einrichten des Berichtsservers <./SettingUpAaps/SettingUpTheReportingServer.md>
 - Nightscout <./SettingUpAaps/Nightscout.md>
 - Tidepool <./SettingUpAaps/Tidepool.md>
-Building AAPS <./SettingUpAaps/BuildingAaps.md>
-- Browser Build <./SettingUpAaps/BrowserBuild.md>
-- Computer Build <./SettingUpAaps/ComputerBuild.md>
-Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
-Setup Wizard <./SettingUpAaps/SetupWizard.md>
-Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
-Change AAPS configuration <./SettingUpAaps/ChangeAapsConfiguration.md>
-- Config Builder <./SettingUpAaps/ConfigBuilder.md>
-- Preferences <./SettingUpAaps/Preferences.md>
-Completing the objectives <./SettingUpAaps/CompletingTheObjectives.md>
+AAPS erstellen <./SettingUpAaps/BuildingAaps.md>
+- Im Browser (Browser Build) <./SettingUpAaps/BrowserBuild.md>
+- Mit dem Computer (Computer Build) <./SettingUpAaps/ComputerBuild.md>
+AAPS übertragen und installieren <./SettingUpAaps/TransferringAndInstallingAaps.md>
+Einrichtungsassistent <./SettingUpAaps/SetupWizard.md>
+Dein AAPS-Profil <. SettingUpAaps/YourAapsProfile.md>
+Ändern der AAPS-Konfiguration <./SettingUpAaps/ChangeAapsConfiguration.md>
+- Konfiguation <./SettingUpAaps/ConfigBuilder.md>
+- Einstellungen <./SettingUpAaps/Preferences.md>
+Abschluss der Ziele <./SettingUpAaps/CompletingTheObjectives.md>
 ```
 
 ```{toctree}
@@ -141,27 +141,27 @@ Austausch-Plattform für eigene Zifferblätter <./ExchangeSiteCustomWatchfaces/i
 ```
 
 ```{toctree}
-:caption: 7) Maintenance of AAPS
+:caption: 7) AAPS pflegen
 
-Export/Import Settings <./Maintenance/ExportImportSettings.md>
-Reviewing your data <./Maintenance/Reviewing.md>
+Export/Import der Einstellungen <./Maintenance/ExportImporteinstellungen. d>
+Deine Daten prüfen <./Maintenance/Reviewing.md>
 AAPS Release Notes <./Maintenance/ReleaseNotes.md>
-Documentation updates <./Maintenance/DocumentationUpdate.md>
-Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
-- Browser Update <./Maintenance/UpdateBrowserBuild.md>
-- Computer Update <./Maintenance/UpdateComputerBuild.md>
+Dokumentation aktualisieren <. Maintenance/DocumentationUpdate.md>
+Update auf eine neue AAPS-Version <./Maintenance/UpdateToNewVersion. d>
+- Browser-Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer-Update <./Maintenance/UpdateComputerBuild.md>
 
 ```
 
 ```{toctree}
-:caption: 8) Getting Help
-
-Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md>
-General troubleshooting <./GettingHelp/GeneralTroubleshooting.md>
-- Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md>
-Profile Tuning Guide <./GettingHelp/ProfileTuning.md>
-Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md>
-Accessing logfiles <./GettingHelp/AccessingLogFiles.md>
+:caption: 8) Hilfe
+
+Wo kann ich Hilfe mit AAPS <./GettingHelp/WhereCanIGetHelp bekommen. d>
+Allgemeine Fehlerbehebung <./GettingHelp/GeneralTroubleshooting.md>
+- Bluetooth Fehlerbehebung <. GettingHelp/BluetoothTroubleshooting.md>
+Anleitung zum Profil-Tuning <./GettingHelp/ProfileTuning.md>
+Fehlersuche Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md>
+Zugriff auf Logdateien <./GettingHelp/AccessingLogFiles.md>
 ```
 
 ```{toctree}
diff --git a/docs/CROWDIN/el/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/el/Maintenance/UpdateToNewVersion.md
index 0e1a294def73..2c0aec79a676 100644
--- a/docs/CROWDIN/el/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/el/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Σημαντικές σημειώσεις
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Ελέγξτε την έκδοση AAPS στο τηλέφωνό σας
 
-After you installed the new apk, you can check the AAPS version on your phone by clicking the three dots menu on the top right and then About. You should see the current version.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![Η έκδοση AAPS έχει εγκατασταθεί](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![Η έκδοση AAPS έχει εγκατασταθεί](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/el/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/el/RemoteFeatures/RemoteControl.md
index ec56e609989a..fb40dd39e083 100644
--- a/docs/CROWDIN/el/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/el/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. Αυτό θα εμφανίσει την τρέχουσα γλυκόζη αίματος, την κατάσταση του συστήματος και θα επιτρέψει την καταχώρηση υδατανθράκων, προσωρινών στόχων και τις αλλαγές προφίλ. ΔΕΝ θα επιτρέψει γευματική δόση ινσουλίνης από την εφαρμογή WearOS. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. Αυτό θα εμφανίσει την τρέχουσα γλυκόζη αίματος, την κατάσταση του συστήματος και θα επιτρέψει την καταχώρηση υδατανθράκων, προσωρινών στόχων και τις αλλαγές προφίλ. ΔΕΝ θα επιτρέψει γευματική δόση ινσουλίνης από την εφαρμογή WearOS. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/el/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/el/RemoteFeatures/RemoteMonitoring.md
index 559e01f58caa..5e59e447eb51 100644
--- a/docs/CROWDIN/el/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/el/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-Το AndroidAPS προσφέρει αρκετές επιλογές για την απομακρυσμένη παρακολούθηση των παιδιών και επίσης επιτρέπει την αποστολή εντολών από απόσταση. Φυσικά, μπορείτε να χρησιμοποιήσετε το σύστημα απομακρυσμένης παρακολούθησης για να ακολουθήσετε τον σύντροφο ή τον φίλο σας.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Λειτουργίες
 
-- Η αντλία του παιδιού ελέγχεται από το τηλέφωνο του παιδιού χρησιμοποιώντας το AndroidAPS.
-- Parents can remotely follow seeing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient app** on their phone. Settings must be the same in AAPS and AAPSClient app.
-- Οι γονείς μπορούν να έχουν συναγερμούς χρησιμοποιώντας την εφαρμογή **xDrip+ με λειτουργία ακόλουθου ** στο τηλέφωνο τους.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Εργαλεία και εφαρμογές για την εξ αποστάσεως παρακολούθηση
 
 - [Nightscout ](https://nightscout.github.io/)στο πρόγραμμα περιήγησης στο web (κυρίως εμφάνιση δεδομένων)
-- AAPSClient app is a stripped down version of AAPS capable of following somebody, making profile switches, setting TTs and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). Η μόνη διαφορά μεταξύ τους είναι το όνομα της εφαρμογής. Με αυτόν τον τρόπο μπορείτε να εγκαταστήσετε την εφαρμογή δύο φορές στο ίδιο τηλέφωνο ώστε να μπορείτε να ακολουθήσετε δύο διαφορετικά άτομα/nightscouts με την εφαρμογή.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Παρακολούθηση Dexcom αν χρησιμοποιείτε την αυθεντική εφαρμογή του Dexcom (μόνο τιμές γλυκόζης)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) ή [Spike](https://spike-app.com/) σε iOS (κυρίως τιμές γλυκόζης και συναγερμοί ****)
@@ -23,13 +23,12 @@
 
 ## Επιλογές Smartwatch
 
-Ένα smartwatch μπορεί να είναι ένα πολύ χρήσιμο εργαλείο για τη διαχείριση του AAPS με παιδιά. Μερικές διαφορετικές ρυθμίσεις είναι δυνατές:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- If AAPSClient is installed on the parents phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the parent's phone. Αυτό θα εμφανίσει την τρέχουσα γλυκόζη αίματος, την κατάσταση του συστήματος και θα επιτρέψει την καταχώρηση υδατανθράκων, προσωρινών στόχων και τις αλλαγές προφίλ. ΔΕΝ θα επιτρέψει γευματική δόση ινσουλίνης από την εφαρμογή WearOS.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. Σε αυτό περιλαμβάνονται όλες οι λειτουργίες που αναφέρονται παραπάνω, καθώς και η ικανότητα για γευματική δόση ινσουλίνης. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. ΔΕΝ θα επιτρέψει γευματική δόση ινσουλίνης από την εφαρμογή WearOS.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. Σε αυτό περιλαμβάνονται όλες οι λειτουργίες που αναφέρονται παραπάνω, καθώς και η ικανότητα για γευματική δόση ινσουλίνης. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Πράγματα που πρέπει να σκεφτείτε
 
-- Settings must be the same in AAPS and AAPSClient app.
-- Λάβετε υπόψη το χρονικό κενό ανάμεσα στο βασικό χρήστη και τον ακόλουθο που δημιουργείται λόγω του χρόνου που χρειάζεται για να ανέβουν και να κατέβουν τα δεδομένα, όπως επίσης και το γεγονός ότι το βασικό τηλέφωνο με AAPS θα ανεβάσει τα δεδομένα μόνο αφού ξεκινήσει το κύκλωμα.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/es/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/es/Maintenance/UpdateToNewVersion.md
index dc7606872dbf..915c5254614f 100644
--- a/docs/CROWDIN/es/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/es/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Notas importantes
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Check AAPS version on phone
 
-After you installed the new apk, you can check the AAPS version on your phone by clicking the three dots menu on the top right and then About. You should see the current version.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![AAPS version installed](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![AAPS version installed](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/es/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/es/RemoteFeatures/RemoteControl.md
index db777b3fa799..1ce37dfd56ed 100644
--- a/docs/CROWDIN/es/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/es/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/es/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/es/RemoteFeatures/RemoteMonitoring.md
index 77ee549e461b..acb408a92d80 100644
--- a/docs/CROWDIN/es/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/es/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-AAPS ofrece varias opciones para la supervisión remota de los niños y también permite enviar comandos remotos. Por supuesto, también puede usar la supervisión remota para seguir los datos de su pareja o amigo.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Funciones
 
-- La bomba de insulina del niño/a es controloda desde el teléfono del niño/a usando AAPS.
-- Parents can remotely follow seeing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient app** on their phone. Settings must be the same in AAPS and AAPSClient app.
-- Parents can be alarmed by using **xDrip+ app in follower mode** on their phone.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Tools and apps for remote monitoring
 
 - [Nightscout](https://nightscout.github.io/) in web browser (mainly data display)
-- AAPSClient app is a stripped down version of AAPS capable of following somebody, making profile switches, setting TTs and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). The only difference is the app name. This way you can install the app twice on the same phone, to be able to follow 2 different persons/nightscouts with it.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Dexcom follow if you are using original Dexcom app (BG values only)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) or [Spike](https://spike-app.com/) on iOS (mainly BG values and **alarms**)
@@ -23,13 +23,12 @@ AAPS ofrece varias opciones para la supervisión remota de los niños y también
 
 ## Smartwatch options
 
-A smartwatch can be a very useful tool in helping manage AAPS with kids. A couple of different configurations are possible:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- If AAPSClient is installed on the parents phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. It will NOT allow bolusing from the WearOS app.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Things to consider
 
-- Settings must be the same in AAPS and AAPSClient app.
-- Consider time gap between master and follower due to time for up- and download as well as the fact that AAPS master phone will only upload after loop run.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/fr/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/fr/Maintenance/UpdateToNewVersion.md
index b63241b1f90a..48c963b02bac 100644
--- a/docs/CROWDIN/fr/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/fr/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Remarques importantes
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Vérifier la version d'AAPS sur le téléphone
 
-Après avoir installer le nouvel apk, vous pouvez vérifier la version AAPS sur votre téléphone en cliquant sur le menu 3 points en haut à droite puis sur "à propos". Vous devriez voir la version actuelle en résultat.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![Version installée d'AAPS](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![Version installée d'AAPS](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/fr/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/fr/RemoteFeatures/RemoteControl.md
index 5e6dbf56421f..e92a740c7845 100644
--- a/docs/CROWDIN/fr/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/fr/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. Ceci affichera l'état actuel de la glycémie, le statut de la boucle et autorisera l'entrée des glucides, des cibles temporaires et des changements de profil. Cela n'autorisera pas les bolus depuis l'application WearOS. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. Ceci affichera l'état actuel de la glycémie, le statut de la boucle et autorisera l'entrée des glucides, des cibles temporaires et des changements de profil. Cela n'autorisera pas les bolus depuis l'application WearOS. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/fr/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/fr/RemoteFeatures/RemoteMonitoring.md
index 668ef4731063..ef27ed103be6 100644
--- a/docs/CROWDIN/fr/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/fr/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Le suivi des enfants](../images/KidsMonitoring.png)
 
-AndroidAPS offre plusieurs options pour la surveillance à distance des enfants et permet également d'envoyer des commandes à distance. Bien sûr, vous pouvez également utiliser la surveillance à distance pour suivre votre partenaire ou votre ami.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Fonctions
 
-- La pompe de l'enfant est contrôlée par le téléphone de l'enfant grâce à AAPS.
-- Les parents peuvent suivre à distance toutes les données pertinentes telles que les glycémies, les glucides actifs, l'insuline active, etc. en utilisant l'application **AAPSClient** sur leur téléphone. Les paramètres doivent être les mêmes dans AAPS et AAPSClient.
-- Les parents peuvent recevoir des alarmes en utilisant l'application **xDrip+ en mode suiveur** sur leur téléphone.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Outils et applications pour la surveillance à distance
 
 - [Nightscout](https://nightscout.github.io/) dans le navigateur web (principalement affichage des données)
-- L'application AAPSClient est une version réduite d'AAPS capable de suivre quelqu'un, de faire des changements de profil, de régler des CTs et d'entrer des glucides. Il y a 2 applications: [AAPSClient & AAPSClient2 que vous pouvez télécharger](https://github.com/nightscout/AndroidAPS/releases/). La seule différence est le nom de l'application. De cette façon, vous pouvez installer l'application deux fois sur le même téléphone, pour pouvoir suivre 2 personnes/nightscout différentes.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. Il y a 2 applications: [AAPSClient & AAPSClient2 que vous pouvez télécharger](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Dexcom Follow si vous utilisez l'application officielle Dexcom (glycémies uniquement)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) ou [Spike](https://spike-app.com/) sur iOS (principalement les valeur de glycémies et les **alarmes**)
@@ -23,13 +23,12 @@ AndroidAPS offre plusieurs options pour la surveillance à distance des enfants
 
 ## Utiliser une montre
 
-Une montre peut être un outil très utile pour aider à gérer AAPS avec les enfants. Plusieurs configurations différentes sont possibles:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- Si AAPSClient est installé sur le téléphone des parents, l'application [AAPSClient WearOS](https://github.com/nightscout/AndroidAPS/releases/) peut être installée sur une montre compatible connectée au téléphone des parents. Ceci affichera l'état actuel de la glycémie, le statut de la boucle et autorisera l'entrée des glucides, des cibles temporaires et des changements de profil. Cela n'autorisera pas les bolus depuis l'application WearOS.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. Cela inclut toutes les fonctions listées ci-dessus, ainsi que la capacité d'injecter un bolus. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. Cela n'autorisera pas les bolus depuis l'application WearOS.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. Cela inclut toutes les fonctions listées ci-dessus, ainsi que la capacité d'injecter un bolus. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Points à considérer
 
-- Les paramètres doivent être les mêmes dans AAPS et AAPSClient.
-- Considérez un décalage de temps entre le maître et le suiveur dû au temps de téléchargement, et parce que le téléphone principal AAPS ne remontera les données qu'après l'exécution de la boucle.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/he/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/he/Maintenance/UpdateToNewVersion.md
index 5f87b88aca1a..ce7a47824295 100644
--- a/docs/CROWDIN/he/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/he/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Important notes
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Check AAPS version on phone
 
-After you installed the new apk, you can check the AAPS version on your phone by clicking the three dots menu on the top right and then About. You should see the current version.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![AAPS version installed](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![AAPS version installed](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/he/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/he/RemoteFeatures/RemoteControl.md
index bfb60ba010d6..53bdf894afd6 100644
--- a/docs/CROWDIN/he/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/he/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. האפליקציה תראה רמת סוכר נוכחית, מצב לולאה, ותאפשר הזנת פחמימות, יעדי מטרה זמניים, ושינויי פרופיל. אין אפשרות לבולוסים מרחוק באמצעות אפליקציית WearOS. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. האפליקציה תראה רמת סוכר נוכחית, מצב לולאה, ותאפשר הזנת פחמימות, יעדי מטרה זמניים, ושינויי פרופיל. אין אפשרות לבולוסים מרחוק באמצעות אפליקציית WearOS. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/he/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/he/RemoteFeatures/RemoteMonitoring.md
index d097e4cf45a2..73fa4681177e 100644
--- a/docs/CROWDIN/he/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/he/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-מערכת AndroidAPS מציעה מספר אפשרויות לניטור מרחוק ושליחת פקודות מרחוק לטיפול בילדים. באותה מידה ניתן לנטר מרחוק גם את בן\\בת הזוג או חבר.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## פונקציות
 
-- משאבת הילד נשלטת באמצעות מכשיר הטלפון של הילד, דרך AAPS.
-- ההורים יכולים לעקוב מרחוק ולראות את כל המידע הרלוונטי, כגון רמת סוכר, פחמימות פעילות, אינסולין פעיל, וכו', באמצעות ** אפליקציית AAPSClient** במכשיר הטלפון הפרטי שלהם. על ההגדרות ב-AAPS ובאפליקציית AAPSClient להיות זהות.
-- הורים יכולים לקבל התרעות באמצעות שימוש **באפליקציית xDrip בתור עוקבים (follower mode)** במכשירים החכמים.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## כלים ואפליקציות לניטור מרחוק
 
 - [נייטסקאוט](https://nightscout.github.io/) בדפדפן אינטרנט (בעיקר הצגת נתונים)
-- אפליקציית AAPSClient היא גרסה חלקית של AAPS, המסוגלת לעקוב אחר מטופל\ת, מאפשרת החלפת פרופילים, הגדרת ערכי מטרה זמניים ורישום פחמימות. קיימות שתי אפליקציות: [AAPSClient ו-AAPSClient2 להורדה](https://github.com/nightscout/AndroidAPS/releases/). ההבדל היחידי ביניהן הוא שמן. כך ניתן להתקין שני עותקים של האפליקציה על אותו המכשיר ולעקוב אחר שני מטופלים או חשבונות נייטסקאוט במקביל.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. קיימות שתי אפליקציות: [AAPSClient ו-AAPSClient2 להורדה](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - דקסקום Follow אם אתם משתמשים באפליקציית דקסקום (רק ערכי הסוכר מוצגים)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - אפליקציית [Sugarmate](https://sugarmate.io/) או [Spike](https://spike-app.com/) על מכשירי iOS (בעיקר ערכי סוכר **והתראות**)
@@ -23,13 +23,12 @@
 
 ## אפשרויות שעון חכם
 
-שעון חכם יכול להיות כלי עזר משמעותי בניהול AAPS אצל ילדים. ישנן מספר תצורות אפשריות:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- במידה ו-AAPSClient מותקן במכשיר הטלפון של ההורים, ניתן להתקין אפליקציית [AAPSClient WearOS ](https://github.com/nightscout/AndroidAPS/releases/)על שעון חכם תואם המחובר למכשיר הטלפון של ההורים. האפליקציה תראה רמת סוכר נוכחית, מצב לולאה, ותאפשר הזנת פחמימות, יעדי מטרה זמניים, ושינויי פרופיל. אין אפשרות לבולוסים מרחוק באמצעות אפליקציית WearOS.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. אפשרות זו כוללת את כל הפונקציות הרשומות לעיל, וכן את האפשרות למתן בולוסים. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. אין אפשרות לבולוסים מרחוק באמצעות אפליקציית WearOS.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. אפשרות זו כוללת את כל הפונקציות הרשומות לעיל, וכן את האפשרות למתן בולוסים. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## דברים שיש לקחת בחשבון
 
-- על ההגדרות ב-AAPS ובאפליקציית AAPSClient להיות זהות.
-- שימו לב שיש הפרש זמנים מסויים בין הטלפון הראשי של המטופל לבין הטלפון העוקב בגלל שליחה והורדה של נתונים ובגלל ש-AAPS של המכשיר הראשי יעלה עדכון רק אחרי שיסיים לבצע את פעולתו.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/ko/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/ko/Maintenance/UpdateToNewVersion.md
index 39652f06ceeb..44291479fd40 100644
--- a/docs/CROWDIN/ko/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/ko/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## 중요사항
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Check AAPS version on phone
 
-After you installed the new apk, you can check the AAPS version on your phone by clicking the three dots menu on the top right and then About. You should see the current version.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![AAPS version installed](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![AAPS version installed](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/ko/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/ko/RemoteFeatures/RemoteControl.md
index 4ba0c6926d55..842f9a77c919 100644
--- a/docs/CROWDIN/ko/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/ko/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/ko/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/ko/RemoteFeatures/RemoteMonitoring.md
index 79b47eb139b6..f94dcff88657 100644
--- a/docs/CROWDIN/ko/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/ko/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-AAPS offer several options for remote monitoring of children and also allows to send remote commands. Of course you can also use remote monitoring to follow your partner or friend.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Functions
 
-- Kid's pump is controlled by kid's phone using AAPS.
-- Parents can remotely follow seeing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient app** on their phone. Settings must be the same in AAPS and AAPSClient app.
-- Parents can be alarmed by using **xDrip+ app in follower mode** on their phone.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Tools and apps for remote monitoring
 
 - [Nightscout](https://nightscout.github.io/) in web browser (mainly data display)
-- AAPSClient app is a stripped down version of AAPS capable of following somebody, making profile switches, setting TTs and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). The only difference is the app name. This way you can install the app twice on the same phone, to be able to follow 2 different persons/nightscouts with it.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Dexcom follow if you are using original Dexcom app (BG values only)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) or [Spike](https://spike-app.com/) on iOS (mainly BG values and **alarms**)
@@ -23,13 +23,12 @@ AAPS offer several options for remote monitoring of children and also allows to
 
 ## Smartwatch options
 
-A smartwatch can be a very useful tool in helping manage AAPS with kids. A couple of different configurations are possible:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- If AAPSClient is installed on the parents phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. It will NOT allow bolusing from the WearOS app.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Things to consider
 
-- Settings must be the same in AAPS and AAPSClient app.
-- Consider time gap between master and follower due to time for up- and download as well as the fact that AAPS master phone will only upload after loop run.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/lt/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/lt/Maintenance/UpdateToNewVersion.md
index d1a5bd0946ef..a3035061e3fe 100644
--- a/docs/CROWDIN/lt/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/lt/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Svarbios pastabos
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Check AAPS version on phone
 
-After you installed the new apk, you can check the AAPS version on your phone by clicking the three dots menu on the top right and then About. You should see the current version.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![AAPS version installed](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![AAPS version installed](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/lt/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/lt/RemoteFeatures/RemoteControl.md
index 153c24590465..8b7308910dea 100644
--- a/docs/CROWDIN/lt/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/lt/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/lt/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/lt/RemoteFeatures/RemoteMonitoring.md
index 00c16d0555f3..7d2ef089ed8b 100644
--- a/docs/CROWDIN/lt/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/lt/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-AAPS offer several options for remote monitoring of children and also allows to send remote commands. Of course you can also use remote monitoring to follow your partner or friend.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Functions
 
-- Kid's pump is controlled by kid's phone using AAPS.
-- Parents can remotely follow seeing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient app** on their phone. Settings must be the same in AAPS and AAPSClient app.
-- Parents can be alarmed by using **xDrip+ app in follower mode** on their phone.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Tools and apps for remote monitoring
 
 - [Nightscout](https://nightscout.github.io/) in web browser (mainly data display)
-- AAPSClient app is a stripped down version of AAPS capable of following somebody, making profile switches, setting TTs and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). The only difference is the app name. This way you can install the app twice on the same phone, to be able to follow 2 different persons/nightscouts with it.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Dexcom follow if you are using original Dexcom app (BG values only)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) or [Spike](https://spike-app.com/) on iOS (mainly BG values and **alarms**)
@@ -23,13 +23,12 @@ AAPS offer several options for remote monitoring of children and also allows to
 
 ## Smartwatch options
 
-A smartwatch can be a very useful tool in helping manage AAPS with kids. A couple of different configurations are possible:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- If AAPSClient is installed on the parents phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. It will NOT allow bolusing from the WearOS app.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Things to consider
 
-- Settings must be the same in AAPS and AAPSClient app.
-- Consider time gap between master and follower due to time for up- and download as well as the fact that AAPS master phone will only upload after loop run.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/nl/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/nl/Maintenance/UpdateToNewVersion.md
index f24dd26d837c..f5016ee083f4 100644
--- a/docs/CROWDIN/nl/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/nl/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Belangrijk:
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Check AAPS version on phone
 
-After you installed the new apk, you can check the AAPS version on your phone by clicking the three dots menu on the top right and then About. You should see the current version.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![AAPS version installed](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![AAPS version installed](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/nl/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/nl/RemoteFeatures/RemoteControl.md
index c867243d4b9c..742442ca6fe9 100644
--- a/docs/CROWDIN/nl/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/nl/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/nl/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/nl/RemoteFeatures/RemoteMonitoring.md
index 84e847963d60..1e12370c6e8e 100644
--- a/docs/CROWDIN/nl/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/nl/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-AAPS offer several options for remote monitoring of children and also allows to send remote commands. Of course you can also use remote monitoring to follow your partner or friend.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Functions
 
-- Kid's pump is controlled by kid's phone using AAPS.
-- Parents can remotely follow seeing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient app** on their phone. Settings must be the same in AAPS and AAPSClient app.
-- Parents can be alarmed by using **xDrip+ app in follower mode** on their phone.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Tools and apps for remote monitoring
 
 - [Nightscout](https://nightscout.github.io/) in web browser (mainly data display)
-- AAPSClient app is a stripped down version of AAPS capable of following somebody, making profile switches, setting TTs and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). The only difference is the app name. This way you can install the app twice on the same phone, to be able to follow 2 different persons/nightscouts with it.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Dexcom follow if you are using original Dexcom app (BG values only)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) or [Spike](https://spike-app.com/) on iOS (mainly BG values and **alarms**)
@@ -23,13 +23,12 @@ AAPS offer several options for remote monitoring of children and also allows to
 
 ## Smartwatch options
 
-A smartwatch can be a very useful tool in helping manage AAPS with kids. A couple of different configurations are possible:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- If AAPSClient is installed on the parents phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. It will NOT allow bolusing from the WearOS app.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Things to consider
 
-- Settings must be the same in AAPS and AAPSClient app.
-- Consider time gap between master and follower due to time for up- and download as well as the fact that AAPS master phone will only upload after loop run.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/pb/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/pb/Maintenance/UpdateToNewVersion.md
index e31ab758029f..4a290089964a 100644
--- a/docs/CROWDIN/pb/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/pb/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Important notes
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Check AAPS version on phone
 
-After you installed the new apk, you can check the AAPS version on your phone by clicking the three dots menu on the top right and then About. You should see the current version.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![AAPS version installed](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![AAPS version installed](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/pb/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/pb/RemoteFeatures/RemoteControl.md
index 7bbb08512d33..9c4a4a78ca2b 100644
--- a/docs/CROWDIN/pb/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/pb/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/pb/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/pb/RemoteFeatures/RemoteMonitoring.md
index fb4a84fd2650..a4d8acbf22a0 100644
--- a/docs/CROWDIN/pb/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/pb/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-AAPS offer several options for remote monitoring of children and also allows to send remote commands. Of course you can also use remote monitoring to follow your partner or friend.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Functions
 
-- Kid's pump is controlled by kid's phone using AAPS.
-- Parents can remotely follow seeing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient app** on their phone. Settings must be the same in AAPS and AAPSClient app.
-- Parents can be alarmed by using **xDrip+ app in follower mode** on their phone.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Tools and apps for remote monitoring
 
 - [Nightscout](https://nightscout.github.io/) in web browser (mainly data display)
-- AAPSClient app is a stripped down version of AAPS capable of following somebody, making profile switches, setting TTs and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). The only difference is the app name. This way you can install the app twice on the same phone, to be able to follow 2 different persons/nightscouts with it.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Dexcom follow if you are using original Dexcom app (BG values only)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) or [Spike](https://spike-app.com/) on iOS (mainly BG values and **alarms**)
@@ -23,13 +23,12 @@ AAPS offer several options for remote monitoring of children and also allows to
 
 ## Smartwatch options
 
-A smartwatch can be a very useful tool in helping manage AAPS with kids. A couple of different configurations are possible:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- If AAPSClient is installed on the parents phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. It will NOT allow bolusing from the WearOS app.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Things to consider
 
-- Settings must be the same in AAPS and AAPSClient app.
-- Consider time gap between master and follower due to time for up- and download as well as the fact that AAPS master phone will only upload after loop run.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/pl/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/pl/Maintenance/UpdateToNewVersion.md
index f35cc58bef0f..17f5f95a3922 100644
--- a/docs/CROWDIN/pl/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/pl/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Important notes
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Check AAPS version on phone
 
-After you installed the new apk, you can check the AAPS version on your phone by clicking the three dots menu on the top right and then About. You should see the current version.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![AAPS version installed](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![AAPS version installed](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/pl/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/pl/RemoteFeatures/RemoteControl.md
index 8e24b04fdad3..1e02b367e839 100644
--- a/docs/CROWDIN/pl/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/pl/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/pl/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/pl/RemoteFeatures/RemoteMonitoring.md
index cdd5c9c3a971..3f09d4afd84d 100644
--- a/docs/CROWDIN/pl/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/pl/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-AAPS offer several options for remote monitoring of children and also allows to send remote commands. Of course you can also use remote monitoring to follow your partner or friend.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Functions
 
-- Kid's pump is controlled by kid's phone using AAPS.
-- Parents can remotely follow seeing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient app** on their phone. Settings must be the same in AAPS and AAPSClient app.
-- Parents can be alarmed by using **xDrip+ app in follower mode** on their phone.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Tools and apps for remote monitoring
 
 - [Nightscout](https://nightscout.github.io/) in web browser (mainly data display)
-- AAPSClient app is a stripped down version of AAPS capable of following somebody, making profile switches, setting TTs and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). The only difference is the app name. This way you can install the app twice on the same phone, to be able to follow 2 different persons/nightscouts with it.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Dexcom follow if you are using original Dexcom app (BG values only)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) or [Spike](https://spike-app.com/) on iOS (mainly BG values and **alarms**)
@@ -23,13 +23,12 @@ AAPS offer several options for remote monitoring of children and also allows to
 
 ## Smartwatch options
 
-A smartwatch can be a very useful tool in helping manage AAPS with kids. A couple of different configurations are possible:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- If AAPSClient is installed on the parents phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. It will NOT allow bolusing from the WearOS app.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Things to consider
 
-- Settings must be the same in AAPS and AAPSClient app.
-- Consider time gap between master and follower due to time for up- and download as well as the fact that AAPS master phone will only upload after loop run.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/pt/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/pt/Maintenance/UpdateToNewVersion.md
index ba44f9973d28..a3c3e878e440 100644
--- a/docs/CROWDIN/pt/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/pt/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Notas importantes
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Check AAPS version on phone
 
-After you installed the new apk, you can check the AAPS version on your phone by clicking the three dots menu on the top right and then About. You should see the current version.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![AAPS version installed](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![AAPS version installed](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/pt/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/pt/RemoteFeatures/RemoteControl.md
index b648b3b27f4e..ffbc397b7a24 100644
--- a/docs/CROWDIN/pt/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/pt/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/pt/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/pt/RemoteFeatures/RemoteMonitoring.md
index 795d018f0041..1598e7c64d21 100644
--- a/docs/CROWDIN/pt/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/pt/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-AAPS offer several options for remote monitoring of children and also allows to send remote commands. Of course you can also use remote monitoring to follow your partner or friend.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Functions
 
-- Kid's pump is controlled by kid's phone using AAPS.
-- Parents can remotely follow seeing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient app** on their phone. Settings must be the same in AAPS and AAPSClient app.
-- Parents can be alarmed by using **xDrip+ app in follower mode** on their phone.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Tools and apps for remote monitoring
 
 - [Nightscout](https://nightscout.github.io/) in web browser (mainly data display)
-- AAPSClient app is a stripped down version of AAPS capable of following somebody, making profile switches, setting TTs and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). The only difference is the app name. This way you can install the app twice on the same phone, to be able to follow 2 different persons/nightscouts with it.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Dexcom follow if you are using original Dexcom app (BG values only)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) or [Spike](https://spike-app.com/) on iOS (mainly BG values and **alarms**)
@@ -23,13 +23,12 @@ AAPS offer several options for remote monitoring of children and also allows to
 
 ## Smartwatch options
 
-A smartwatch can be a very useful tool in helping manage AAPS with kids. A couple of different configurations are possible:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- If AAPSClient is installed on the parents phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. It will NOT allow bolusing from the WearOS app.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Things to consider
 
-- Settings must be the same in AAPS and AAPSClient app.
-- Consider time gap between master and follower due to time for up- and download as well as the fact that AAPS master phone will only upload after loop run.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/ro/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/ro/Maintenance/UpdateToNewVersion.md
index e31ab758029f..4a290089964a 100644
--- a/docs/CROWDIN/ro/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/ro/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Important notes
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Check AAPS version on phone
 
-After you installed the new apk, you can check the AAPS version on your phone by clicking the three dots menu on the top right and then About. You should see the current version.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![AAPS version installed](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![AAPS version installed](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/ro/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/ro/RemoteFeatures/RemoteControl.md
index a6ccc0db7d45..4d39520f8e86 100644
--- a/docs/CROWDIN/ro/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/ro/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/ro/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/ro/RemoteFeatures/RemoteMonitoring.md
index cd7f43829f9b..e30f5eef4217 100644
--- a/docs/CROWDIN/ro/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/ro/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-AAPS offer several options for remote monitoring of children and also allows to send remote commands. Of course you can also use remote monitoring to follow your partner or friend.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Functions
 
-- Kid's pump is controlled by kid's phone using AAPS.
-- Parents can remotely follow seeing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient app** on their phone. Settings must be the same in AAPS and AAPSClient app.
-- Parents can be alarmed by using **xDrip+ app in follower mode** on their phone.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Tools and apps for remote monitoring
 
 - [Nightscout](https://nightscout.github.io/) in web browser (mainly data display)
-- AAPSClient app is a stripped down version of AAPS capable of following somebody, making profile switches, setting TTs and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). The only difference is the app name. This way you can install the app twice on the same phone, to be able to follow 2 different persons/nightscouts with it.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Dexcom follow if you are using original Dexcom app (BG values only)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) or [Spike](https://spike-app.com/) on iOS (mainly BG values and **alarms**)
@@ -23,13 +23,12 @@ AAPS offer several options for remote monitoring of children and also allows to
 
 ## Smartwatch options
 
-A smartwatch can be a very useful tool in helping manage AAPS with kids. A couple of different configurations are possible:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- If AAPSClient is installed on the parents phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. It will NOT allow bolusing from the WearOS app.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Things to consider
 
-- Settings must be the same in AAPS and AAPSClient app.
-- Consider time gap between master and follower due to time for up- and download as well as the fact that AAPS master phone will only upload after loop run.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/ru/AdvancedOptions/FullClosedLoop.md b/docs/CROWDIN/ru/AdvancedOptions/FullClosedLoop.md
index 4c861bc3ac2b..a21488183f5b 100644
--- a/docs/CROWDIN/ru/AdvancedOptions/FullClosedLoop.md
+++ b/docs/CROWDIN/ru/AdvancedOptions/FullClosedLoop.md
@@ -27,14 +27,14 @@
 Автономный замкнутый цикл (**FCL**) не для всех:
 
 - Многие пользователи автономного цикла добиваются 90% времени в целевом диапазоне (4--! 0), а HbA1c - менее 6%, однако некоторые предпочитают более жесткий контроль. Следует отметить, что снижение показателей выше 140 мг/дл (7,7 ммоль/л) при приёме быстрых углеводов, вероятно, требует предварительного введения болюса.
-- **AAPS** tuning can be challenging. It is not for those users who feel overwhelmed AAPS.  You will need to dedicate a few weeks in order to adjust and fine tune your **FCL**. Investing such time can yield better results and **BG** control.
-- Meal management may become easier, however exercise can still be challenging in **FCL**. Most of us like to limit sports snacks in an attempt to control body weight.
-- Difficulties still remain to establish a **FCL** for kids (discussed below).
+- Тонкая настройка **AAPS** может быть сложной. Особенно для тех, кто не чуствует себя уверенным пользователем AAPS.  Для полноценной настройки **Автономного ЗЦ** понадобится несколько недель. Потраченное время не пропадет зря - вы получите полноценную компенсацию и контоль **ГК**.
+- Как правило, при работе с **АЗЦ**. люди легче справляются с компенсацией питания, чем физической нагрузки. Многие любят ограничивать себя в количестве спортивных перекусов чтобы контролировать массу тела.
+- Организация **АЗЦ** для детей по-прежнему представляет сложности (обсуждаются ниже).
 
 
-## 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.
+Прежде чем переходить на **АЗЦ** рекомендуется хорошо отладить гибридный **ЗЦ**.  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**.
 
diff --git a/docs/CROWDIN/ru/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/ru/Maintenance/UpdateToNewVersion.md
index f038df9f4a7a..3eb358d27cff 100644
--- a/docs/CROWDIN/ru/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/ru/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Важные Примечания
 
-* Обновите **AAPS** как можно быстрее после выхода новой версии.
-* Когда доступна новая версия, в самом приложении **AAPS** появляется информационный баннер об этом.
-* О новой версии также выходит объявление на Facebook во время релиза.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Обновите **AAPS** как можно быстрее после выхода новой версии.
+- Когда доступна новая версия, в самом приложении **AAPS** появляется информационный баннер об этом.
+- О новой версии также выходит объявление на Facebook во время релиза.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Проверьте версию AAPS на телефоне
 
-После установки нового приложения, проверьте версию AAPS, нажав на выпадающее меню вверху справа "о приложении". Вы увидете текущую версию.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![Установленная версия AAPS](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![Установленная версия AAPS](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/ru/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/ru/RemoteFeatures/RemoteControl.md
index 9c69a85e7e99..68cac4185324 100644
--- a/docs/CROWDIN/ru/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/ru/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-Смарт-часы - полезный инструмент в управлении **AAPS** у детей. Возможны несколько различных конфигураций. Если AAPSClient установлен на родительский телефон,, приложение [AAPSClient WearOS](https://github.com/nightscout/AndroidAPS/releases/) может быть установлено на смарт-часах, сопряженных с родительским телефоном. На них будет отображаться текущая ГК, статус замкнутого цикла, возможность вписать углеводы, временные цели и изменения профиля. Возможности ввести болюс с приложения на WearOS не будет. You can read more about Smartwatches [here](#4-smartwatches).
+Смарт-часы - полезный инструмент в управлении **AAPS** у детей. Возможны несколько различных конфигураций. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. На них будет отображаться текущая ГК, статус замкнутого цикла, возможность вписать углеводы, временные цели и изменения профиля. Возможности ввести болюс с приложения на WearOS не будет. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/ru/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/ru/RemoteFeatures/RemoteMonitoring.md
index ae9ce5bc39b2..8478d2bcaf0b 100644
--- a/docs/CROWDIN/ru/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/ru/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-AAPS предлагает несколько опций для удаленного мониторинга детей, а также позволяет отправлять удаленные команды. Конечно, его можно использовать для мониторинга партнера или друга.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Функции
 
-- Помпа ребенка управляется телефоном ребенка с помощью AAPS.
-- Родители могут дистанционно следить за всеми данными, такими как уровень глюкозы, активные углеводы, активный инсулин и т. д. с помощью приложения **AAPSClient** на своем телефоне. Настройки должны быть одинаковыми в AAPS и AAPSClient.
-- Родители могут слышать оповещения с помощью приложения **xDrip в режиме слежения (follower)** на своем телефоне.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Инструменты и приложения для удаленного мониторинга
 
 - [Nightscout](https://nightscout.github.io/) в интернет-браузере (в основном отображение данных)
-- * Приложение AAPSClient-это урезанная версии AAPS для слежения, переключения профилей, постановки временных целей TT и ввода углеводов. Существует два приложения для загрузки:  [AAPSClient & AAPSClient2](https://github.com/nightscout/AndroidAPS/releases/). Единственное отличие-это название приложения. Таким образом имеется возможность установить приложение дважды на одном телефоне, чтобы следить за 2 разными лицами/nightscout.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. Существует два приложения для загрузки:  [AAPSClient & AAPSClient2](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Приложение Dexcom Follow, если вы используете оригинальное приложение Dexcom (только ГК)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) или [Spike](https://spike-app.com/) на iOS (в основном значения ГК и <1>оповещения</1>)
@@ -23,13 +23,12 @@ AAPS предлагает несколько опций для удаленно
 
 ## Опции для смарт-часов
 
-Смарт-часы бывают очень полезным инструментом для управления AAPS у детей. Возможны несколько различных конфигураций:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- Если AAPSClient установлен на родительский телефон,, приложение [AAPSClient WearOS](https://github.com/nightscout/AndroidAPS/releases/) может быть установлено на смарт-часах, сопряженных с родительским телефоном. На них будет отображаться текущая ГК, статус замкнутого цикла, возможность вписать углеводы, временные цели и изменения профиля. Возможности ввести болюс с приложения на WearOS не будет.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. В него войдут все перечисленные выше функции, а также возможность подать болюс. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. Возможности ввести болюс с приложения на WearOS не будет.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. В него войдут все перечисленные выше функции, а также возможность подать болюс. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Важные факторы
 
-- Настройки должны быть одинаковыми в AAPS и AAPSClient.
-- Учитывайте временной разрыв между ведущим телефоном и ведомым из-за времени на загрузку и выгрузку, а также из-за того, что ведущий телефон AAPS начнет выгрузку только после выполнения цикла.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/sk/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/sk/Maintenance/UpdateToNewVersion.md
index e31ab758029f..4a290089964a 100644
--- a/docs/CROWDIN/sk/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/sk/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Important notes
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Check AAPS version on phone
 
-After you installed the new apk, you can check the AAPS version on your phone by clicking the three dots menu on the top right and then About. You should see the current version.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![AAPS version installed](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![AAPS version installed](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/sk/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/sk/RemoteFeatures/RemoteControl.md
index 249e61f5d784..847f96ce1f8d 100644
--- a/docs/CROWDIN/sk/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/sk/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/sk/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/sk/RemoteFeatures/RemoteMonitoring.md
index 3c9c9ff6e680..b4b74984b9fc 100644
--- a/docs/CROWDIN/sk/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/sk/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-AAPS offer several options for remote monitoring of children and also allows to send remote commands. Of course you can also use remote monitoring to follow your partner or friend.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Functions
 
-- Kid's pump is controlled by kid's phone using AAPS.
-- Parents can remotely follow seeing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient app** on their phone. Settings must be the same in AAPS and AAPSClient app.
-- Parents can be alarmed by using **xDrip+ app in follower mode** on their phone.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Tools and apps for remote monitoring
 
 - [Nightscout](https://nightscout.github.io/) in web browser (mainly data display)
-- AAPSClient app is a stripped down version of AAPS capable of following somebody, making profile switches, setting TTs and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). The only difference is the app name. This way you can install the app twice on the same phone, to be able to follow 2 different persons/nightscouts with it.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Dexcom follow if you are using original Dexcom app (BG values only)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - [Sugarmate](https://sugarmate.io/) or [Spike](https://spike-app.com/) on iOS (mainly BG values and **alarms**)
@@ -23,13 +23,12 @@ AAPS offer several options for remote monitoring of children and also allows to
 
 ## Smartwatch options
 
-A smartwatch can be a very useful tool in helping manage AAPS with kids. A couple of different configurations are possible:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- If AAPSClient is installed on the parents phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the parent's phone. This will show current BG, loop status and allow carb entry, temp targets and profile changes. It will NOT allow bolusing from the WearOS app.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. It will NOT allow bolusing from the WearOS app.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Things to consider
 
-- Settings must be the same in AAPS and AAPSClient app.
-- Consider time gap between master and follower due to time for up- and download as well as the fact that AAPS master phone will only upload after loop run.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/tr/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/tr/Maintenance/UpdateToNewVersion.md
index 853026cb7c51..07fe35c4207f 100644
--- a/docs/CROWDIN/tr/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/tr/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## Önemli notlar
 
-* Please update to the new version of **AAPS** as soon as possible after a new release is available.
-* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
-* The new version will also be announced on Facebook at the time of release.
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Please update to the new version of **AAPS** as soon as possible after a new release is available.
+- When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+- The new version will also be announced on Facebook at the time of release.
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### Telefondaki AAPS sürümünü kontrol edin
 
-Yeni apk'yı yükledikten sonra, sağ üstteki üç nokta menüsüne ve ardından Hakkında'ya tıklayarak telefonunuzdaki AAPS sürümünü kontrol edebilirsiniz. Mevcut sürümü görmelisiniz.
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
 
-![Yüklü AAPS sürümü](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![Yüklü AAPS sürümü](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/tr/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/tr/RemoteFeatures/RemoteControl.md
index 2f78e8e67a2d..ffcd54c841f9 100644
--- a/docs/CROWDIN/tr/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/tr/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@ If selecting Websockets (which is optional) ensure this is activated or deactiva
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### Troubleshooting 'NS access token' configuration issues
 
@@ -110,7 +110,7 @@ Remote control through **AAPSClient** is only recommended if your synchronizatio
 
 ### AAPSClient with smartwatch options
 
-A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the parents phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. Bu, mevcut KŞ'yi, döngü durumunu gösterecek ve karbonhidrat girişi, geçici hedefler ve profil değişikliklerine izin verecektir. WearOS uygulamasından bolus kullanımına izin VERİLMEZ. You can read more about Smartwatches [here](#4-smartwatches).
+A smartwatch can be a very useful tool for helping to manage **AAPS** with kids. A couple of different configurations are possible. If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. Bu, mevcut KŞ'yi, döngü durumunu gösterecek ve karbonhidrat girişi, geçici hedefler ve profil değişikliklerine izin verecektir. WearOS uygulamasından bolus kullanımına izin VERİLMEZ. You can read more about Smartwatches [here](#4-smartwatches).
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/tr/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/tr/RemoteFeatures/RemoteMonitoring.md
index b63cd918d9b0..0f22a0a75b86 100644
--- a/docs/CROWDIN/tr/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/tr/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![Monitoring children](../images/KidsMonitoring.png)
 
-AAPS, çocukların uzaktan izlenmesi için çeşitli seçenekler sunar ve ayrıca uzaktan sms komutları göndermeye izin verir. Elbette, partnerinizi veya arkadaşınızı takip etmek için de uzaktan izlemeyi kullanabilirsiniz.
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## Fonksiyonlar
 
-- Çocuğun pompası, AAPS kullanılarak çocuğun telefonu tarafından kontrol edilir.
-- Parents can remotely follow seeing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient app** on their phone. Settings must be the same in AAPS and AAPSClient app.
-- Ebeveynler, telefonlarında **xDrip+ uygulamasını takipçi modunda** kullanarak KŞ uyarılarını alabilirler.
-- Remote control of AAPS using [SMS Commands](../RemoteFeatures/SMSCommands.md) secured by two-factor authentication.
-- Remote control through AAPSClient app is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## Uzaktan izleme için araçlar ve uygulamalar
 
 - Web tarayıcısında [Nightscout](https://nightscout.github.io/) (Ana veri ekranı)
-- AAPSClient app is a stripped down version of AAPS capable of following somebody, making profile switches, setting TTs and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). Tek fark uygulama adıdır. Bu şekilde aynı telefona iki kez uygulamayı yükleyebilir, 2 farklı kişiyi/nightscout'u takip edebilirsiniz.
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - Orijinal Dexcom uygulamasını kullanıyorsanız, Dexcom follow uygulaması (yalnızca KŞ değerleri)
 - [xDrip+](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
 - iOS'ta [Sugarmate](https://sugarmate.io/) veya [Spike](https://spike-app.com/) (esas olarak KŞ değerleri ve **alarmlar**)
@@ -23,13 +23,12 @@ AAPS, çocukların uzaktan izlenmesi için çeşitli seçenekler sunar ve ayrıc
 
 ## Akıllı saat seçenekleri
 
-Akıllı saat, çocuklarla AAPS'nin yönetilmesine yardımcı olmak için çok yararlı bir araç olabilir. Birkaç farklı konfigürasyon mümkündür:
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- If AAPSClient is installed on the parents phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the parent's phone. Bu, mevcut KŞ'yi, döngü durumunu gösterecek ve karbonhidrat girişi, geçici hedefler ve profil değişikliklerine izin verecektir. WearOS uygulamasından bolus kullanımına izin VERİLMEZ.
-- Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. Bu uygulama yukarıda listelenen tüm fonksiyonların yanı sıra bolus insülin yeteneğini de içerir. This allows the parent to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. WearOS uygulamasından bolus kullanımına izin VERİLMEZ.
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. Bu uygulama yukarıda listelenen tüm fonksiyonların yanı sıra bolus insülin yeteneğini de içerir. This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## Dikkat edilmesi gereken önemli noktalar
 
-- Settings must be the same in AAPS and AAPSClient app.
-- AAPS ana telefonunun yalnızca döngü çalıştırıldıktan sonra karşıya bilgi yükleyeceğini, bunun yanı sıra yükleme ve indirme süresi nedeniyle ana ve takipçi arasında bilgide zaman farkının oluşacağını da göz önünde bulundurun.
-- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- What is your emergency plan for when remote control does not work (_i.e._ network problems or lost bluetooth connection)?  Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.
diff --git a/docs/CROWDIN/zh_CN/CompatibleCgms/OttaiM8.md b/docs/CROWDIN/zh_CN/CompatibleCgms/OttaiM8.md
index dc1680306ba6..00df28b01c47 100644
--- a/docs/CROWDIN/zh_CN/CompatibleCgms/OttaiM8.md
+++ b/docs/CROWDIN/zh_CN/CompatibleCgms/OttaiM8.md
@@ -16,4 +16,4 @@
 3. 点击"与AAPS共享"，同意第三方数据传输协议
 4. 启用"与AAPS共享血糖数据"功能
 
-![Ottai](../images/Ottai.png)
+![欧泰 (Ottai)](../images/Ottai.png)
diff --git a/docs/CROWDIN/zh_CN/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/zh_CN/Maintenance/UpdateToNewVersion.md
index 7e8ff174fb02..50841d3f818d 100644
--- a/docs/CROWDIN/zh_CN/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/zh_CN/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## 重要说明
 
-* 当有新版本发布时，请尽快更新至最新版本的 **AAPS**。
-* 当有新版本可用时，**AAPS** 应用内会显示新版本的信息横幅。
-* 新版本发布时也会在 Facebook 上同步公告。
-* Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- 当有新版本发布时，请尽快更新至最新版本的 **AAPS**。
+- 当有新版本可用时，**AAPS** 应用内会显示新版本的信息横幅。
+- 新版本发布时也会在 Facebook 上同步公告。
+- Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+- Do not forget to export your **AAPS'** settings.
 
 ## Update AAPS with browser build
 
@@ -23,8 +24,13 @@ Follow [these instructions.](./UpdateComputerBuild.md).
 
 ### 检查手机上的 AAPS 版本
 
-安装新的APK后，您可以通过点击右上角的三个点菜单，然后点击“关于”来检查手机上的AAPS版本。 您应该看到当前版本。
+请查阅 [版本说明](../Maintenance/ReleaseNotes.md) 确认是否有更新后的特别注意事项。
 
-![已安装的 AAPS 版本](../images/Update_VersionCheck.png)
+After you installed the new apk:
 
-请查阅 [版本说明](../Maintenance/ReleaseNotes.md) 确认是否有更新后的特别注意事项。
\ No newline at end of file
+- you can check the **AAPS'** version on your phone by clicking the three dots menu on the top right and then 'About' (as per the screenshot below). The **AAPS'** current version can be viewed; 
+- ensure import settings have been actioned;
+- action a 'full synchroniation' under **NSClient** to ensure **AAPS** is working off accurate & complete data; and
+- please check your **AAPS'** settings under **Preferences** and ensure these remain accurate.
+
+![已安装的 AAPS 版本](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_CN/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/zh_CN/RemoteFeatures/RemoteControl.md
index 191f8677f554..7ad0fe1fb5e8 100644
--- a/docs/CROWDIN/zh_CN/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/zh_CN/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-用户应确保__AAPSClient__和__AAPS__在各自手机的“NSClient”标签下均显示“已连接”，并且一旦在__AAPSClient__中选择，就可以在__AAPS__中正确激活“Profile Switches”或“Temp Target”。
+The user should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
 
-用户还应确保在__AAPSClient__和__AAPS__的“Treatments”中都记录了碳水化合物，否则可能表明用户设置出现故障。
+The user should also ensure that when carbs are entered in either __AAPS__ or __AAPSClient__ that the data is automatically logged in both ‘Treatments’ for both __AAPSClient__ and __AAPS__. Otherwise, this could indicate a malfunction within either the user’s __AAPS__ or __AAPSClient__ set up.
 
 ### 故障排除“NS访问令牌”配置问题
 
@@ -110,7 +110,7 @@
 
 ### AAPSClient与智能手表选项
 
-智能手表是帮助管理孩子**AAPS**的非常有用的工具。 有几种不同的配置可选。 如果在父母的手机上安装了**AAPSClient**，则可以在与父母的手机连接的兼容智能手表上安装[**AAPSClient WearOS**应用程序](https://github.com/nightscout/AndroidAPS/releases/)。 这将显示当前的血糖值、Loop（闭环系统）状态和允许碳水化合物输入、临时目标设定以及配置更改。 但它不允许通过WearOS应用进行大剂量胰岛素注射。 您可以阅读有关智能手表的更多信息[此处](#4-smartwatches)。
+智能手表是帮助管理孩子**AAPS**的非常有用的工具。 有几种不同的配置可选。 If **AAPSClient** is installed on the caregiver's phone, the [**AAPSClient WearOS** app](https://github.com/nightscout/AndroidAPS/releases/) can be downloaded and installed on a compatible smartwatch which is connected to the parent's phone. 这将显示当前的血糖值、Loop（闭环系统）状态和允许碳水化合物输入、临时目标设定以及配置更改。 但它不允许通过WearOS应用进行大剂量胰岛素注射。 您可以阅读有关智能手表的更多信息[此处](#4-smartwatches)。
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/zh_CN/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/zh_CN/RemoteFeatures/RemoteMonitoring.md
index 18afd12f07d8..cbc5977c3bcd 100644
--- a/docs/CROWDIN/zh_CN/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/zh_CN/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![监控儿童](../images/KidsMonitoring.png)
 
-AAPS为儿童提供多种远程监控选项，并且还可以发送远程指令。 当然，您也可以使用远程监控来跟踪您的伴侣或朋友。
+__AAPS__ offers several features for remote monitoring of type 1 diabetic children and also faciltates remote commands which sends instructions to the __AAPS__ remotely. Similarly, __AAPSClient__ can also be used for remote monitoring to follow your partner's or friend's __AAPS__.
 
 ## 功能
 
-- 孩子的泵可通过孩子的手机使用AAPS进行控制。
-- 父母可以使用手机上的**AAPSClient应用程序**远程查看所有相关数据，如血糖水平、活性碳水、活性胰岛素量等。 AAPS和AAPSClient应用程序中的设置必须相同。
-- 父母可以通过在手机上使用**xDrip+应用程序的跟随者模式**接收警报。
-- 使用受双重身份验证保护的[短信指令](../RemoteFeatures/SMSCommands.md)进行AAPS的远程控制。
-- 如果同步运行良好（即，您没有看到不需要的数据更改，如临时目标（TT）、临时基础率（TBR）等的自我修改），则建议使用AAPSClient应用程序进行远程控制。 有关更多详细信息，请参阅[2.8.1.1版发行说明](#important-hints-2-8-1-1)。
+- Kid's pump is controlled by kid's phone using __AAPS__.
+- Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchromise with __AAPSClient__ and vice versa.
+- Caregivers can be alarmed by using **xDrip+ app in follower mode** on their Android phone if xdrip companion mode is set up.
+- Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
+- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (ie. you don’t see unwanted data changes like self modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However synchonization is less likely to an issue if the user if usiing the latest version of __AAPS__ and __AAPSClient with NSClientv3/Nightscout15.
 
 ## 远程监控的工具和应用程序
 
 - 在网页浏览器中使用[Nightscout](https://nightscout.github.io/)（主要用于数据显示）
-- AAPSClient应用程序是AAPS的精简版，能够跟踪他人、切换配置、设置临时目标和输入碳水化合物。 有两个应用程序可供[下载](https://github.com/nightscout/AndroidAPS/releases/)：AAPSClient和AAPSClient2。 唯一的区别是应用程序名称。 这样，您可以在同一部手机上安装该应用程序两次，以便能够用它跟踪两个不同的个人/Nightscout。
+- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. 有两个应用程序可供[下载](https://github.com/nightscout/AndroidAPS/releases/)：AAPSClient和AAPSClient2。 AAPSClient should be used is the caregivers wishes to install the apk twice on the same phone to follow 2 different persons (e.g two children with type 1 each with their own nightscout acccount).
 - 如果使用的是Dexcom原版应用程序，则可以使用Dexcom跟踪（仅血糖值）
 - 在跟随者模式下使用[xDrip+](../CompatibleCgms/xDrip.md)（主要是血糖值和**警报**）
 - 在iOS上使用[Sugarmate](https://sugarmate.io/)或[Spike](https://spike-app.com/)（主要是血糖值和**警报**）
@@ -23,13 +23,12 @@ AAPS为儿童提供多种远程监控选项，并且还可以发送远程指令
 
 ## 智能手表选项
 
-智能手表在帮助儿童管理AAPS方面是一个非常有用的工具。 可以实现几种不同的配置：
+A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- 如果在父母的手机上安装了AAPSClient，则可以在与父母的手机连接的兼容智能手表上安装[AAPSClient WearOS应用程序](https://github.com/nightscout/AndroidAPS/releases/)。 这将显示当前的血糖值、Loop（闭环系统）状态和允许碳水化合物输入、临时目标设定以及配置更改。 但它不允许通过WearOS应用进行大剂量胰岛素注射。
-- 或者，可以在与孩子的手机连接但由父母佩戴的兼容智能手表上构建并安装[AAPS WearOS应用程序](../WearOS/WearOsSmartwatch.md)。 这包括上面列出的所有功能，以及大剂量注射胰岛素的能力。 家长可通过此功能实施胰岛素注射，无需取出孩子的手机，无论手机如何存放于孩子身边。
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. 但它不允许通过WearOS应用进行大剂量胰岛素注射。
+- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. 这包括上面列出的所有功能，以及大剂量注射胰岛素的能力。 This allows the caregiver o administer insulin without needing to remove the kid's phone from however it is kept on them.
 
 ## 需要考虑的事项
 
-- AAPS和AAPSClient应用程序中的设置必须相同。
-- 考虑到上传和下载所需的时间，以及AAPS主手机仅在循环运行后才会上传数据，因此主设备和跟随者设备之间会存在时间差。
-- 如果远程控制不起作用（_即_，出现网络问题或蓝牙连接丢失）时，您的应急计划是什么？  始终考虑如果您突然无法发送新指令，**AAPS**会发生什么。 **AAPS**会用当前配置值覆盖泵的基础率、胰岛素敏感因子（ISF）和碳水化合物比率（ICR）。 如果切换到更强的胰岛素配置，则只使用临时配置切换（_即_，设置持续时间），以防远程连接中断。 然后，当时间到期时，泵将恢复为原始配置。
\ No newline at end of file
+- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- 如果远程控制不起作用（_即_，出现网络问题或蓝牙连接丢失）时，您的应急计划是什么？  始终考虑如果您突然无法发送新指令，**AAPS**会发生什么。 **AAPS**会用当前配置值覆盖泵的基础率、胰岛素敏感因子（ISF）和碳水化合物比率（ICR）。 如果切换到更强的胰岛素配置，则只使用临时配置切换（_即_，设置持续时间），以防远程连接中断。 然后，当时间到期时，泵将恢复为原始配置。
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/ConfigBuilder.md b/docs/CROWDIN/zh_CN/SettingUpAaps/ConfigBuilder.md
index 7e5de92ebba8..59810906393e 100644
--- a/docs/CROWDIN/zh_CN/SettingUpAaps/ConfigBuilder.md
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/ConfigBuilder.md
@@ -98,7 +98,7 @@
 * [Poctech](../CompatibleCgms/PocTech.md)
 * Tomato App for MiaoMiao device
 * 用于Glunovo CGM系统的[Glunovo App](https://infinovo.com/)
-* [Ottai](../CompatibleCgms/OttaiM8.md)
+* [欧泰 (Ottai)](../CompatibleCgms/OttaiM8.md)
 * [Syai Tag](../CompatibleCgms/SyaiTagX1.md)
 * 随机 Random BG：生成随机BG数据（仅演示模式）
 
diff --git a/docs/CROWDIN/zh_TW/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/zh_TW/Maintenance/UpdateToNewVersion.md
index 35b610e00b99..2ceba177a9a3 100644
--- a/docs/CROWDIN/zh_TW/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/zh_TW/Maintenance/UpdateToNewVersion.md
@@ -6,10 +6,11 @@
 
 ## 重要提示
 
-* 請在有新版本發布後儘快更新到最新版本的 **AAPS**。
-* 當有新版本發布時，你將在 **AAPS** 應用中收到關於新版本的訊息橫幅。
-* 新版本也會在發布時於 Facebook 上公佈。
-* 發布後，請詳細閱讀[發布說明](ReleaseNotes.md)，如有任何疑問，請在Facebook或Discord社群中澄清後再進行更新。
+- 請在有新版本發布後儘快更新到最新版本的 **AAPS**。
+- 當有新版本發布時，你將在 **AAPS** 應用中收到關於新版本的訊息橫幅。
+- 新版本也會在發布時於 Facebook 上公佈。
+- 發布後，請詳細閱讀[發布說明](ReleaseNotes.md)，如有任何疑問，請在Facebook或Discord社群中澄清後再進行更新。
+- 別忘了匯出你的 **AAPS'** 設定。
 
 ## 使用瀏覽器版本更新 AAPS
 
@@ -23,8 +24,13 @@
 
 ### 檢查手機上的 AAPS 版本
 
-安裝新 apk 後，你可以點擊右上角的三點選單，然後選擇 "關於"，以檢查手機上的 AAPS 版本。 你應該能看到目前版本。
+檢查[發佈說明](../Maintenance/ReleaseNotes.md)以了解更新後是否有任何特定的指示。
 
-![已安裝的 AAPS 版本](../images/Update_VersionCheck.png)
+安裝新的 apk 之後：
 
-檢查[發佈說明](../Maintenance/ReleaseNotes.md)以了解更新後是否有任何特定的指示。
\ No newline at end of file
+- 你可以點選右上角的三點選單，接著按「關於」，在手機上查看 **AAPS'** 版本（如下方螢幕截圖所示）。 可以看到目前的 **AAPS'** 版本； 
+- 請確認已完成匯入設定；
+- 在 **NSClient** 底下執行「完整同步」，以確保 **AAPS** 以正確且完整的資料運作；以及
+- 請在 **Preferences**（偏好設定）中檢查你的 **AAPS'** 設定，並確保其仍然正確。
+
+![已安裝的 AAPS 版本](../images/Update_VersionCheck.png)
\ No newline at end of file
diff --git a/docs/CROWDIN/zh_TW/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/zh_TW/RemoteFeatures/RemoteControl.md
index 8fac92cf491e..50b563bf8cf1 100644
--- a/docs/CROWDIN/zh_TW/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/zh_TW/RemoteFeatures/RemoteControl.md
@@ -82,9 +82,9 @@
 ![WB2_截圖 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-用戶應確保 __AAPSClient__ 和 __AAPS__ 均在“NSClient”標籤下顯示“已連線”，並且當在 __AAPSClient__ 中選擇後，“設定檔切換”或“臨時目標”可以在 __AAPS__ 中正確啟動。
+使用者應確保兩支手機的「NSClient」分頁下，__AAPSClient__ 與 __AAPS__ 都顯示「已連線」，並且在 __AAPSClient__ 中選擇的「設定檔切換」或「臨時目標」能在 __AAPS__ 中正確啟用。
 
-用戶還應確保在 __AAPSClient__ 和 __AAPS__ 中的“治療”中紀錄碳水化合物，否則這可能表明用戶的設置存在問題。
+使用者也應確保，無論在 __AAPS__ 或 __AAPSClient__ 輸入碳水時，資料都會自動記錄到 __AAPSClient__ 與 __AAPS__ 的「Treatments」。 否則，這可能表示使用者的 __AAPS__ 或 __AAPSClient__ 設定有故障或異常。
 
 ### 問題排除“NS 查看權杖”配置問題
 
@@ -110,7 +110,7 @@
 
 ### AAPSClient 與智慧型手錶的選項
 
-智慧型手錶可以是一個非常有用的工具，幫助管理兒童的 **AAPS**。 有幾種不同的配置方式可供選擇。 如果**AAPSClient** 安裝在父母的手機上，則可以下載並安裝[**AAPSClient WearOS** 應用程式](https://github.com/nightscout/AndroidAPS/releases/)在與父母手機連線的相容智慧型手錶上。 這將顯示目前的血糖值、循環狀態，並允許輸入碳水化合物、設定臨時目標和更換設定檔。 無法從 WearOS 應用程式進行注射。 你可以在[這裡](#4-smartwatches)閱讀更多關於智慧型手錶的資訊。
+智慧型手錶可以是一個非常有用的工具，幫助管理兒童的 **AAPS**。 有幾種不同的配置方式可供選擇。 若在照護者的手機安裝了 **AAPSClient**，即可下載並安裝 [**AAPSClient WearOS** 應用程式](https://github.com/nightscout/AndroidAPS/releases/) 到與家長手機連線的相容智慧型手錶上。 這將顯示目前的血糖值、循環狀態，並允許輸入碳水化合物、設定臨時目標和更換設定檔。 無法從 WearOS 應用程式進行注射。 你可以在[這裡](#4-smartwatches)閱讀更多關於智慧型手錶的資訊。
 
 (RemoteControl_nightscout)=
 ## 3) Nightscout
diff --git a/docs/CROWDIN/zh_TW/RemoteFeatures/RemoteMonitoring.md b/docs/CROWDIN/zh_TW/RemoteFeatures/RemoteMonitoring.md
index a6ad167f28ba..b3ec6c5e51d3 100644
--- a/docs/CROWDIN/zh_TW/RemoteFeatures/RemoteMonitoring.md
+++ b/docs/CROWDIN/zh_TW/RemoteFeatures/RemoteMonitoring.md
@@ -2,20 +2,20 @@
 
 ![監控兒童](../images/KidsMonitoring.png)
 
-AAPS 提供多種遠端監控兒童的選項，並允許傳送遠端指令。 當然，你也可以使用遠端監控來追蹤你的夥伴或朋友。
+__AAPS__ 提供多項功能，用於遠端監控第一型糖尿病兒童，並且也支援遠端指令，可將操作指示遠端傳送至 __AAPS__。 同樣地，__AAPSClient__ 也可用於遠端監控，追蹤你伴侶或朋友的 __AAPS__。
 
 ## 功能
 
-- 孩子的幫浦是由孩子的手機使用 AAPS 控制的。
-- 父母可以透過他們的手機使用 **AAPSClient 應用程式** 遠端查看所有相關資料，如血糖值、活性碳水化合物、活性胰島素等。 AAPS 和 AAPSClient 應用程式中的設定必須相同。
-- 父母可以使用手機上的 **xDrip+ 應用程式** 在追蹤者模式中接收警報。
-- 透過[簡訊指令](../RemoteFeatures/SMSCommands.md)遠端控制 AAPS，由雙重身份驗證保護。
-- 僅在同步運作正常時（例如你沒有看到不需要的資料更改如 TT、TBR 自動修改等情況）建議使用 AAPSClient 應用程式進行遠端控制，有關詳情請參閱 [2.8.1.1 版的發行說明](#important-hints-2-8-1-1)。
+- 孩子的幫浦由孩子的手機透過 __AAPS__ 控制。
+- 照護者可以在其 Android 智慧型手機上使用 **AAPSClient apk** 進行遠端追蹤，查看所有相關資料，例如血糖值、活性碳水化合物（COB）、活性胰島素（IOB）等。 在 __AAPS__ 中變更的設定會與 __AAPSClient__ 同步，反之亦然。
+- 若已設定 xDrip 配套模式，照護者可在其 Android 智慧型手機上使用 **xDrip+ 追蹤者模式應用程式** 接收警報。
+- 使用 [簡訊指令](../RemoteFeatures/SMSCommands.md) 遠端控制 __AAPS__，會以兩步驟驗證來保護安全。
+- 僅當你的同步運作良好時，才建議透過 __AAPSClient__ 進行遠端控制（也就是不會出現不希望的資料變動，如自動修改臨時目標、臨時基礎率等）。更多詳情請參閱 [版本 2.8.1.1 的發行說明](#important-hints-2-8-1-1)。 然而，若使用者使用最新版本的 __AAPS__ 與 __AAPSClient，並搭配 NSClientv3/Nightscout15，發生同步問題的機率會較低。
 
 ## 遠端監控的工具和應用程式
 
 - 網頁瀏覽器中的 [Nightscout](https://nightscout.github.io/)（主要用於資料顯示）
-- AAPSClient 應用程式是 AAPS 的精簡版本，能夠追蹤某人、更換設定檔、設定臨時目標並輸入碳水化合物。 你可以下載兩個應用程式：[AAPSClient 及 AAPSClient2](https://github.com/nightscout/AndroidAPS/releases/)。 這兩個應用程式唯一的區別是應用程式名稱。 這樣，你可以在同一部手機上安裝兩個應用程式，從而能夠追蹤兩個不同人的nightscouts。
+- __AAPSClient__ apk 是 __AAPS__ 的精簡版，能用於追蹤他人、進行 __設定檔切換__、設定 __臨時目標__，以及輸入碳水。 你可以下載兩個應用程式：[AAPSClient 及 AAPSClient2](https://github.com/nightscout/AndroidAPS/releases/)。 若照護者希望在同一支手機上安裝該 apk 兩次以追蹤兩位不同的人（例如兩位第一型糖尿病兒童，各自擁有自己的 Nightscout 帳號），則應使用 AAPSClient。
 - 如果你使用的是原版 Dexcom 應用程式，你可以使用 Dexcom 追蹤應用程式（僅顯示血糖值）。
 - [xDrip+](../CompatibleCgms/xDrip.md) 在追蹤模式（主要是血糖值和**警報**）
 - 在 iOS 上使用 [Sugarmate](https://sugarmate.io/) 或 [Spike](https://spike-app.com/)（主要顯示血糖值和 **警報**）。
@@ -23,13 +23,12 @@ AAPS 提供多種遠端監控兒童的選項，並允許傳送遠端指令。 
 
 ## 智慧型手錶選項
 
-智慧型手錶在幫助管理 AAPS 和孩子的情況下可能是非常有用的工具。 可以進行幾種不同的配置：
+智慧型手錶在協助以 __AAPS__ 管理第一型糖尿病孩童時，非常有幫助。 有幾種不同的選項可供選擇：
 
-- 如果父母的手機上安裝了 AAPSClient，則可以在與父母手機相連的相容智慧型手錶上安裝 [AAPSClient WearOS 應用程式](https://github.com/nightscout/AndroidAPS/releases/)。 這將顯示目前的血糖值、循環狀態，並允許輸入碳水化合物、設定臨時目標和更換設定檔。 無法從 WearOS 應用程式進行注射。
-- 此外，可以在相容的智慧型手錶上構建並安裝[AAPS WearOS 應用程式](../WearOS/WearOsSmartwatch.md)，該手錶連接到孩子的手機，但由家長佩戴。 這包括上述所有功能，並具有注射胰島素的能力。 這允許家長在不需要將孩子的手機從身上取下來的情況下給予胰島素。
+- 選項 1 - 若照護者的手機已安裝 __AAPSClient__，即可在與照護者手機連線的相容智慧型手錶上安裝 [AAPSClient WearOS 應用程式](https://github.com/nightscout/AndroidAPS/releases/)。 這將顯示目前的血糖、循環狀態，並允許輸入碳水、設定臨時目標與變更設定檔。 無法從 WearOS 應用程式進行注射。
+- 選項 2 - 或者，可以建置並將 [AAPS WearOS 應用程式](../WearOS/WearOsSmartwatch.md) 安裝到相容的智慧型手錶上；該手錶連線到孩子的手機，但由家長佩戴。 這包括上述所有功能，並具有注射胰島素的能力。 如此一來，照護者無需將孩子隨身攜帶的手機取下，就能為其注射胰島素。
 
 ## 需考慮的事項
 
-- AAPS 和 AAPSClient 應用程式中的設定必須相同。
-- 考慮主裝置和追蹤者之間的時間差，因為上傳和下載需要時間，並且 AAPS 主手機只會在循環運作後上傳資料。
-- 當遠端控制無法工作時，你的應急計劃是什麼（_例如_網絡問題或藍牙連線丟失）？  始終考慮當你突然無法發送新指令時，**AAPS** 會發生什麼情況。 **AAPS** 會使用目前設定覆蓋幫浦的基礎率、ISF 和 ICR。 如果切換到更強的胰島素設定，請只使用臨時設定切換（_例如_設置特定的持續時間），以防止遠端連線中斷。 當時間到期時，幫浦將恢復到原始設定。
\ No newline at end of file
+- 請考量主端與追蹤端之間可能的時間差，這來自上傳與下載所需時間，以及 __AAPS__ 主手機僅會在循環執行後才上傳的事實。
+- 當遠端控制無法工作時，你的應急計劃是什麼（_例如_網絡問題或藍牙連線丟失）？  始終考慮當你突然無法發送新指令時，**AAPS** 會發生什麼情況。 **AAPS** 會使用目前設定覆蓋幫浦的基礎率、ISF 和 ICR。 如果切換到更強的胰島素設定，請只使用臨時設定切換（_例如_設置特定的持續時間），以防止遠端連線中斷。 當時間到期時，幫浦將恢復到原始設定。