diff --git a/docs/CROWDIN/it/CompatibleCgms/DexcomG7.md b/docs/CROWDIN/it/CompatibleCgms/DexcomG7.md
index 621ce6461699..b29b0fa47c08 100644
--- a/docs/CROWDIN/it/CompatibleCgms/DexcomG7.md
+++ b/docs/CROWDIN/it/CompatibleCgms/DexcomG7.md
@@ -25,7 +25,7 @@ Dexcom BYODA è ora una versione molto vecchia dell'app e non può essere aggior
- [Costruisci la tua app Dexcom](https://docs.google.com/forms/d/e/1FAIpQLScD76G0Y-BlL4tZljaFkjlwuqhT83QlFM5v6ZEfO7gCU98iJQ/viewform?fbzx=2196386787609383750) (BYODA) supporta la trasmissione locale su AAPS e/o xDrip+
-!\[BYODA broadcast options\](C:\Data\50 - My Projects\AAPS\OpenAPS\AndroidAPSdocs\docs\EN\images\BYODA.png)
+
- Questa app ti permette di utilizzare il tuo Dexcom G7 con qualsiasi smartphone Android.
- Disinstalla l'app Dexcom originale
diff --git a/docs/CROWDIN/it/CompatibleCgms/Libre3.md b/docs/CROWDIN/it/CompatibleCgms/Libre3.md
index 7aa43e5491f6..ad013996f54d 100644
--- a/docs/CROWDIN/it/CompatibleCgms/Libre3.md
+++ b/docs/CROWDIN/it/CompatibleCgms/Libre3.md
@@ -22,7 +22,7 @@ Questo metodo utilizza Juggluco per ricevere i dati grezzi dal sensore ogni minu
### Passo 1: Impostare Juggluco
Scarica e installa l'applicazione Juggluco da [qui](https://www.juggluco.nl/Juggluco/download.html). Segui le istruzioni [qui](https://www.juggluco.nl/Juggluco/libre3/)
-Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Make sure you send the glucose values to xDrip+: In Juggluco's settings you can configure Juggluco to send its glucose value to other apps.
+Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Juggluco can send three types of such broadcasts: The **Patched Libre broadcast** was originally used by the patched Librelink app and can be used to send glucose values to xDrip+ Make sure you send the glucose values to xDrip+: In Juggluco's settings you can configure Juggluco to send its glucose value to other apps.
### Passo 2: Impostare xDrip
diff --git a/docs/CROWDIN/it/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/it/CompatiblePumps/OmnipodDASH.md
index 9c2064149e3c..a795ad5bcea4 100644
--- a/docs/CROWDIN/it/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/it/CompatiblePumps/OmnipodDASH.md
@@ -19,8 +19,8 @@ Queste sono le specifiche dell' **Omnipod DASH** ('DASH') e ciò che lo differen
## Limitazioni/problemi noti di AAPS con Omnipod DASH
- Android 16 richiede **AAPS** versione 3.3.2.1 o successiva.
- Il consiglio generale è di usare **AAPS** su Android 14 o 16. Android 15 ha molti [problemi](https://github.com/nightscout/AndroidAPS/issues/3471) segnalati dalla comunità. Tuttavia, se si utilizza Android 15 sarà probabilmente necessario abilitare il Bluetooth Bonding per attivare e usare i Pod con successo, vedere [Risoluzione generale dei problemi](../GettingHelp/GeneralTroubleshooting.md) per maggiori informazioni sulle impostazioni di Bonding.
-- Aggiornamenti basali troppo frequenti possono causare [problemi](https://github.com/nightscout/AndroidAPS/issues/4158) di erogazione dell'insulina basale con Omnipod Dash. Quando si usa **SMB**, limitare l'intervallo a un minimo di 5 minuti per evitare questo problema.
-- Dash supporta solo la velocità basale in step di 0,05 U/h. Se si tenta di impostare la basale con step di 0,01 nel **profilo AAPS**, AAPS non darà un avviso anche se il pod arrotonderà la velocità a step di 0,05. Se si visualizza GESTIONE POD/Cronologia pod, mostrerà che è stata impostata una basale di 0,05. Ciò significa anche che la velocità basale minima consentita dal DASH in **AAPS** è 0,05 U/h.
+- Temporary Basal rate changes (which occur frequently when the loop is active, especially overnight) result in under-delivery of insulin. This is effectively a hardware limitation of the Omnipod DASH. The issue has been addressed in AAPS 3.4.2.3, but the functionality is currently opt-in. Follow the [Basal Drift Fix Instructions ](#omnipod-dash-Basal-drift-fix) instructions to enable it. For more information regarding the fix see [Github Issue - 4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more info.
+- Dash supporta solo la velocità basale in step di 0,05 U/h. If you try to set Basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. Se si visualizza GESTIONE POD/Cronologia pod, mostrerà che è stata impostata una basale di 0,05. Ciò significa anche che la velocità basale minima consentita dal DASH in **AAPS** è 0,05 U/h.
- Lo stato di attivazione di un Pod viene memorizzato nel file delle impostazioni. Se si esporta un file di impostazioni con un pod attivo, poi si passa a un nuovo pod e si ripristinano le impostazioni dall'esportazione precedente, si avrà ripristinato l'attivazione del vecchio pod e rimosso quella del nuovo. Per questo motivo si consiglia di esportare le impostazioni dopo ogni attivazione del pod per consentire il ripristino dello stato di attivazione del pod in caso di problemi.
- Quando si imposta un nuovo profilo basale, DASH sospenderà l'erogazione prima di impostare il nuovo **Profilo** basale. Se c'è un'interruzione della comunicazione o un errore, il profilo basale non ripartirà automaticamente. Vedere la sezione [Ripresa dell'erogazione di insulina](#omnipod-dash-resuming-insulin-delivery) per i dettagli.
- Se gli avvisi sono configurati e il pod sta per scadere, il pod continuerà a emettere segnali acustici finché gli avvisi non vengono silenziati; vedere [Silenziamento avvisi pod](#omnipod-dash-silencing-pod-alerts) per i dettagli.
@@ -67,7 +67,8 @@ Assicurarsi di aver letto e compreso questa intera guida, di aver letto e compre
Le velocità basali predefinite sono programmate sul pod all'attivazione come definite nel [**Profilo**](../SettingUpAaps/YourAapsProfile.md) attivo corrente. Finché **AAPS** è operativo, invierà comandi di regolazione della velocità basale che durano al massimo 120 minuti. Quando per qualche motivo il pod non riceve nuovi comandi (ad esempio perché la comunicazione è stata persa a causa della distanza Pod ➜ telefono), il pod tornerà automaticamente alle velocità basali predefinite definite nel tuo [**Profilo**](../SettingUpAaps/YourAapsProfile.md).
### **I Profili AAPS non supportano intervalli di tempo basali di 30 minuti**
-Se sei nuovo ad **AAPS** e stai configurando il tuo [**Profilo**](../SettingUpAaps/YourAapsProfile.md) di velocità basale per la prima volta, tieni presente che le velocità basali che iniziano a mezz'ora non sono supportate. Ad esempio, se sul tuo PDM Omnipod hai una velocità basale di 1,1 unità che inizia alle 09:30 e ha una durata di 2 ore fino alle 11:30, non è possibile replicare questo esatto **Profilo** basale in **AAPS**. Dovrai cambiare questa velocità basale di 1,1 unità in un intervallo di tempo di 9:00-11:00 o 10:00-12:00. Anche se l'hardware DASH stesso supporta gli incrementi di 30 minuti del **Profilo** di velocità basale, **AAPS** NON supporta questa funzione.
+Se sei nuovo ad **AAPS** e stai configurando il tuo [**Profilo**](../SettingUpAaps/YourAapsProfile.md) di velocità basale per la prima volta, tieni presente che le velocità basali che iniziano a mezz'ora non sono supportate. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact Basal **Profile** in **AAPS**.
+You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Anche se l'hardware DASH stesso supporta gli incrementi di 30 minuti del **Profilo** di velocità basale, **AAPS** NON supporta questa funzione.
### **Le velocità basali del Profilo a 0 U/h NON sono supportate in AAPS**
Sebbene il DASH supporti una velocità basale zero, **AAPS** usa multipli della velocità basale del **Profilo** dell'utente per determinare il trattamento automatico; non può funzionare con una velocità basale zero. In alternativa, una velocità basale temporanea zero può essere ottenuta tramite la funzione "Disconnetti microinfusore", o tramite una combinazione di Disabilita Loop/Basale Temporanea o Sospendi Loop/Basale Temporanea. **NOTA:** La velocità basale minima consentita dal DASH in **AAPS** è 0,05 U/h.
@@ -471,11 +472,46 @@ Nota aggiuntiva:
* **SMS** - Restituisce il valore o 50+ U per le risposte SMS
* **Nightscout** - Carica il valore di 50 quando supera le 50 unità su Nightscout (versione 14.07 e precedenti). Le versioni più recenti segnaleranno un valore di 50+ quando supera le 50 unità.
-(omnipod-dash-troubleshooting)=
+(omnipod-dash-known-issues-workarounds)=
+
+## Known Issues Workarounds
+
+This section covers common workarounds and settings that need to be changed to enable a feature to work around a community reported issue that has a fix. E.g. the Basal drift enable process is documented here.
+
+(#omnipod-dash-Basal-drift-fix)=
+
+### Basal Drift Fix Instructions
+
+The Omnipod Dash pump has a limitation that can cause it to deliver less basal insulin than **AAPS** expects, see [Issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) for more technical details.
+
+The Dash uses an internal timer to determine when a basal pulse of 0.05 U is delivered. Once the timer interval elapses, the pulse is delivered. However, this timer is restarted whenever a basal rate change occurs e.g when **AAPS** sends a new Basal rate.
+
+When used in combination with looping, this leads to under-delivery of basal insulin, as the algorithm updates the basal rate on the pump frequently.
+
+The issue is most apparent during the night. During daytime operation, SMBs often result in a basal rate of 0, which masks the effect. In observed usage, this results in approximately 10% of the expected Total Daily Dose (TDD) not being delivered over a 24-hour period. Additionally, glucose targets are often not reached overnight, particularly after meals with prolonged glucose impact (e.g. pasta).
+
+***NOTE:** This issue is especially important to understand for people on very small dosages of insulin, Children for example.*
+
+#### Enable Basal Drift Fix in AAPS
+
+You must be running AAPS Version 3.4.2.3 or later for this feature.
+
+The Basal Drift Fix is not enabled by default on AAPS.
+
+**To enable it:**
+
+1. Create an empty file named `omnipod_drift_compensation` (2) in the `extra` (1) subfolder of your phone [AAPS directory](#preferences-maintenance-settings).
+
+ 
+
+ ***NOTE:** Ensure you check in the AAPS settings where your AAPS Directory is, and that you placed the file in the correct one, a number of several have been caught out putting the file into the wrong folder.*
+
+2. Restart **AAPS**. This must be done for it to recognise the file is present and enable the drift compensation feature.
+3. Please visit this [Github issue #4783](https://github.com/nightscout/AndroidAPS/issues/4783) and thumbs up the first post indicating you are using this feature, we need this data to help demonstrate the feature is widely used. Once there is significant community adoption the removal of the enable file will be possible, we appreciate your support here.
## Risoluzione dei problemi
-(omnipod-dash-delivery-suspended)=
+(omnipod-dash-troubleshooting)=
Questa sezione copre i problemi noti comuni e le soluzioni per l'uso di Omnipod DASH con AAPS. È disponibile anche la sezione [Risoluzione generale dei problemi](../GettingHelp/GeneralTroubleshooting.md) nella documentazione che dovrebbe essere consultata poiché copre argomenti rilevanti anche per alcuni problemi del Pod.
@@ -488,6 +524,9 @@ Questa sezione copre i problemi noti comuni e le soluzioni per l'uso di Omnipod
Per problemi noti con le connessioni Bluetooth, disconnessioni di microinfusori/pod, o problemi di attivazione e connessione vedere [Risoluzione problemi Bluetooth](../GettingHelp/BluetoothTroubleshooting.md)
---
+
+(omnipod-dash-delivery-suspended)=
+
### Erogazione sospesa
- Non c'è più un pulsante di sospensione. Se si vuole "sospendere" il pod, è possibile impostare una **TBR** zero per x minuti.
@@ -500,7 +539,7 @@ Per problemi noti con le connessioni Bluetooth, disconnessioni di microinfusori/
- Se **AAPS** non riesce a riprendere l'erogazione da solo (questo accade se il pod non è raggiungibile, il suono è disattivato ecc.), il pod inizierà a emettere 4 segnali acustici ogni minuto per 3 minuti, poi ripetuti ogni 15 minuti se l'erogazione è ancora sospesa per più di 20 minuti.
- Per i comandi non confermati, "aggiorna stato pod" dovrebbe confermarli/negarli.
-********************************************************************NOTE:** When you hear beeps from the pod, do not assume that delivery will continue without checking the phone, delivery might stay suspended, ***so you need to check !*********************************************************************
+***********************************************************************NOTE:** When you hear beeps from the pod, do not assume that delivery will continue without checking the phone, delivery might stay suspended, ***so you need to check !************************************************************************
---
### Fallimenti Pod
diff --git a/docs/CROWDIN/it/ExchangeSiteCustomWatchfaces/index.md b/docs/CROWDIN/it/ExchangeSiteCustomWatchfaces/index.md
index ccf083144ddb..ff22018ab989 100644
--- a/docs/CROWDIN/it/ExchangeSiteCustomWatchfaces/index.md
+++ b/docs/CROWDIN/it/ExchangeSiteCustomWatchfaces/index.md
@@ -11,7 +11,7 @@ Durante l'unione della pull request il team della documentazione estrarrà il fi
| | | |
|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|
| [
**AAPS V2**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AAPS_V2.zip) | [
**AAPS**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AAPS.zip) | [
**AIMICO**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AIMICO-V1_1.zip) |
-| https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AAPS_BigChart.zip** | https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AAPS_Large.zip** | https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AAPS_NoChart.zip** |
+| https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AAPS_BigChart.zip*** | https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AAPS_Large.zip*** | https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AAPS_NoChart.zip*** |
| [
**Analog G-Watch**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Analog_G-Watch.zip) | [
**AAPS (Cockpit)**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Cockpit.zip) | [
**Digital G-Watch**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Digital_G-Watch.zip) |
| [
**DigitalBigGraph**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/DigitalBigGraph_v1.5.zip) | [
**Gears**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Gears.zip) | [
**Gota**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Gota_v2.4.zip) |
| [
**LuckyLoopKoeln**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/LuckyLoopKoeln.zip) | [
**P-Zero watchface**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/pzero_v1.0.zip) | [
**PinkFloydTheWall**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/PinkFloydTheWall.zip) |
diff --git a/docs/CROWDIN/it/Getting-Started/CompatiblesCgms.md b/docs/CROWDIN/it/Getting-Started/CompatiblesCgms.md
index 21dcd4c165ed..21ffadde9060 100644
--- a/docs/CROWDIN/it/Getting-Started/CompatiblesCgms.md
+++ b/docs/CROWDIN/it/Getting-Started/CompatiblesCgms.md
@@ -12,7 +12,8 @@ Questa sezione fornisce una breve panoramica di tutti i **sensori CGMs/FGMs** co
| CGM | Sorgenti BG [disponibili](#Config-Builder-bg-source) |
| --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| [Dexcom G7](../CompatibleCgms/DexcomG7.md) | BYODA, [xDrip+](../CompatibleCgms/xDrip.md) o [Juggluco](../CompatibleCgms/Juggluco.md) |
-| [Dexcom ONE+ and Stelo](../CompatibleCgms/DexcomG7.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
+| [Dexcom ONE+](../CompatibleCgms/DexcomG7.md) | [xDrip+](../CompatibleCgms/xDrip.md) or [Juggluco](../CompatibleCgms/Juggluco.md) |
+| [Dexcom Stelo](../CompatibleCgms/DexcomG7.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
| [Dexcom G6](../CompatibleCgms/DexcomG6.md) | BYODA o [xDrip+](../CompatibleCgms/xDrip.md) |
| [Dexcom ONE](../CompatibleCgms/DexcomG6.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
| [Libre 3/3+](../CompatibleCgms/Libre3.md) | [Juggluco](../CompatibleCgms/Juggluco.md) (con o senza xDrip+) |
@@ -27,7 +28,7 @@ Questa sezione fornisce una breve panoramica di tutti i **sensori CGMs/FGMs** co
| [Syai](../CompatibleCgms/SyaiTagX1.md) | Syai Tag App |
| Sibionics CGM | [Juggluco](../CompatibleCgms/Juggluco.md) o App SI patchata |
| Sinocare | Patched Sino App |
-| [Caresens](../CompatibleCgms/Caresens.md), Simplera, iCan, LinX, SmartGuide | xDrip+ Companion App |
+| [Caresens](../CompatibleCgms/Caresens.md), Simplera, iCan, LinX, SmartGuide | xDrip+ Companion App or [Juggluco](../CompatibleCgms/Juggluco.md) |
(GettingStarted-TrustedBGSource)=
@@ -39,13 +40,14 @@ Affinché **AAPS** possa identificarli correttamente, l'app che invia le letture
Le sorgenti dati affidabili consentono sempre l'erogazione di **SMB**.
-| Sensore | App CGM |
-| --------------------- |:-----------------------------------------------------------------------------------------------------------------------:|
-| Dexcom G6 | BYODA, xDrip+ (**Direct, Native**) |
-| Dexcom G7 | BYODA, xDrip+ (**Direct, Native**), Juggluco (**xDrip broadcast** without xDrip+) |
-| Dexcom ONE/ONE+/Stelo | xDrip+ (**Direct, Native**) |
-| Libre 2/2+ (EU) | xDrip+ (OOP2 **senza calibrazione**), Juggluco (**xDrip broadcast** senza xDrip+, o **Libre patchato** con xDrip+) |
-| Libre 2/2+/3/3+ | Juggluco (**xDrip broadcast** senza xDrip+, o **Libre patchato** con xDrip+) |
-| Syai | Syai App |
+| Sensore | App CGM |
+| ---------------- |:-----------------------------------------------------------------------------------------------------------------------:|
+| Dexcom G6 | BYODA, xDrip+ (**Direct, Native**) |
+| Dexcom G7 | BYODA, xDrip+ (**Direct, Native**), Juggluco (**xDrip broadcast** without xDrip+) |
+| Dexcom ONE+ | xDrip+ (**Direct, Native**), Juggluco (**xDrip broadcast** without xDrip+) |
+| Dexcom ONE/Stelo | xDrip+ (**Direct, Native**) |
+| Libre 2/2+ (EU) | xDrip+ (OOP2 **senza calibrazione**), Juggluco (**xDrip broadcast** senza xDrip+, o **Libre patchato** con xDrip+) |
+| Libre 2/2+/3/3+ | Juggluco (**xDrip broadcast** senza xDrip+, o **Libre patchato** con xDrip+) |
+| Syai | Syai App |
**Nota: le app companion di xDrip+ e le modalità follower (incluso 640G/Eversense) non sono sorgenti di dati affidabili.**
diff --git a/docs/CROWDIN/it/GettingHelp/ProfileTuning.md b/docs/CROWDIN/it/GettingHelp/ProfileTuning.md
index 6bef336bb999..025f654c5c01 100644
--- a/docs/CROWDIN/it/GettingHelp/ProfileTuning.md
+++ b/docs/CROWDIN/it/GettingHelp/ProfileTuning.md
@@ -17,7 +17,7 @@ L'uso del **circuito chiuso** può rendere più facile il test della basale e pu
3. Tieni d'occhio i modelli che si ripetono quasi ogni giorno alla stessa ora.
4. È importante farlo per diversi giorni. I risultati scadenti tendono a derivare dall'uso di dati osservati in un singolo giorno per prendere decisioni di regolazione del __Profilo__.
5. Dopo aver osservato un modello di comportamento ripetibile, ad esempio all'1:00 PM vedi un picco della __glicemia__ o un valore __IOB__ negativo, solo allora inizia ad apportare piccole modifiche al tuo __Profilo__.
-6. È importante limitare le modifiche a una cosa alla volta. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. increase your basal by 10% around 1PM.
+6. È importante limitare le modifiche a una cosa alla volta. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. E.g. increase your basal by 10% around 1PM.
7. Dopo ogni modifica, è importante monitorare l'impatto sulla tua __glicemia__ e __IOB__ per i giorni successivi.
8. Ripeti questo schema: osserva, decidi, aggiusta di nuovo se necessario.
diff --git a/docs/CROWDIN/it/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/it/SettingUpAaps/BrowserBuild.md
index 6e2649fb387a..71aa9e96875f 100644
--- a/docs/CROWDIN/it/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/it/SettingUpAaps/BrowserBuild.md
@@ -141,7 +141,7 @@ https://github.com/nightscout/aaps-ci-preparation/releases/latest
- Se anche il link esterno non è disponibile, puoi utilizzare questo file di backup per il download.
````
<<<<<<< Updated upstream AndroidAPS build requires private keys, that are stored in a Java KeyStore (JKS): - If this is your first time building AAPS (or you don't have a an Android Studio JKS), follow [AAPS-CI Option 1 – Generate JKS](#aaps-ci-option1) to complete the setup.
-- - - - - - - - - - - - - - If this is your first time building AAPS (or you don't have a an Android Studio JKS), follow [AAPS-CI Option 1 – Generate JKS](#aaps-ci-option1) to complete the setup.
+- - - - - - - - - - - Se vuoi utilizzare il tuo JKS (quello usato per una precedente compilazione di AAPS da computer in Android Studio), conosci la password e l'alias (key0), scegli [AAPS-CI Opzione 2 – Carica JKS esistente](#aaps-ci-option2).
```{warning}
@@ -156,7 +156,7 @@ Sarà necessario:
7. Ripristinare i dati da Nightscout.
```
-- - - - - - - - - - - Se vuoi utilizzare il tuo JKS (quello usato per una precedente compilazione di AAPS da computer in Android Studio), conosci la password e l'alias (key0), scegli [AAPS-CI Opzione 2 – Carica JKS esistente](#aaps-ci-option2).
+- - - - - - - - - - - - - - - If this is your first time building AAPS (or you don't have a an Android Studio JKS), follow [AAPS-CI Option 1 – Generate JKS](#aaps-ci-option1) to complete the setup.
diff --git a/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_enable_file.png b/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_enable_file.png
new file mode 100644
index 000000000000..917f90c264b5
Binary files /dev/null and b/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_enable_file.png differ
diff --git a/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png b/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png
new file mode 100644
index 000000000000..5b9a8485a40b
Binary files /dev/null and b/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_pod_mgmt.png differ
diff --git a/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png b/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png
new file mode 100644
index 000000000000..5b268b517df0
Binary files /dev/null and b/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_pod_stats_end.png differ
diff --git a/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png b/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png
new file mode 100644
index 000000000000..2863168f7b19
Binary files /dev/null and b/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_pod_stats_start.png differ
diff --git a/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png b/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png
new file mode 100644
index 000000000000..30a5edb90b1d
Binary files /dev/null and b/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_tab_pod_mgmt.png differ
diff --git a/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_tdd.png b/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_tdd.png
new file mode 100644
index 000000000000..28b7685fa5bd
Binary files /dev/null and b/docs/CROWDIN/it/images/DASH_images/DASH_Drift/dash_drift_tdd.png differ