New Crowdin updates

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+ 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+ 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
 

docs/CROWDIN/it/CompatiblePumps/OmnipodDASH.md

@@ -500,7 +500,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

docs/CROWDIN/it/ExchangeSiteCustomWatchfaces/CustomWatchfaceReference.md

@@ -10,7 +10,7 @@ Custom Watchface è un formato aperto progettato per AAPS, associato al nuovo qu
 
 Il file del quadrante è un semplice file zip, ma per essere riconosciuto come file di quadrante, il file zip deve contenere i seguenti file:
 
-- Un file immagine chiamato CustomWatchface (può essere un file bitmap `CustomWatchface.jpg`, `CustomWatchface.png` o un vettoriale `CustomWatchface.svg`) Un file immagine chiamato CustomWatchface (può essere un file bitmap `CustomWatchface.jpg`, `CustomWatchface.png` o un vettoriale `CustomWatchface.svg`) Questo file è la piccola icona usata per selezionare il quadrante quando clicchi sul pulsante "Carica Quadrante", ed è anche l'immagine visibile nel plugin AAPS Wear.
+- Un file immagine chiamato CustomWatchface (può essere un file bitmap `CustomWatchface.jpg`, `CustomWatchface.png` o un vettoriale `CustomWatchface.svg`) Un file immagine chiamato CustomWatchface (può essere un file bitmap `CustomWatchface.jpg`, `CustomWatchface.png` o un vettoriale `CustomWatchface.svg`) Questo file è la piccola icona usata per selezionare il quadrante quando clicchi sul pulsante "Carica Quadrante", ed è anche l'immagine visibile nel plugin AAPS Wear. Un file immagine chiamato CustomWatchface (può essere un file bitmap `CustomWatchface.jpg`, `CustomWatchface.png` o un vettoriale `CustomWatchface.svg`) Questo file è la piccola icona usata per selezionare il quadrante quando clicchi sul pulsante "Carica Quadrante", ed è anche l'immagine visibile nel plugin AAPS Wear.
 - Un file denominato `CustomWatchface.json` (vedi [struttura JSON](#cwf-reference-json-structure) sotto). Questo secondo file è il file principale che contiene tutte le informazioni necessarie per progettare il quadrante. Il file json deve essere valido (questo è probabilmente il punto più delicato quando si modifica manualmente il file con un editor di testo, perché una virgola mancante o in più è sufficiente a invalidare il formato json). Il file JSON deve anche includere un blocco `"metadata"` con una chiave `"name"` non vuota. Questo sarà il nome del tuo quadrante personalizzato (vedi [Impostazioni Metadata](#cwf-reference-metadata-settings) sotto).
 - - the size of this zip should be as small as possible (less than about 500kb). Se questo file è troppo grande, verrà semplicemente bloccato e non trasmesso all'orologio.
 

docs/CROWDIN/it/ExchangeSiteCustomWatchfaces/index.md

@@ -11,7 +11,7 @@ Durante l'unione della pull request il team della documentazione estrarrà il fi
 |                                                                                                                                                                                                                                                                     |                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                    |
 |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|
 |               [![Watchface AAPS_V2](../images/ExchangeSiteCustomWatchfaces/AAPS_V2-CustomWatchface.png) <br>**AAPS V2**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AAPS_V2.zip)               |                               [![AAPS](../images/ExchangeSiteCustomWatchfaces/AAPS-CustomWatchface.png) <br>**AAPS**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/AAPS.zip)                                |                [![AIMICO](../images/ExchangeSiteCustomWatchfaces/AIMICO-V1_1-CustomWatchface.png) <br>**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](../images/ExchangeSiteCustomWatchfaces/Analog_G-Watch-CustomWatchface.png) <br>**Analog G-Watch**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Analog_G-Watch.zip)      |                      [![Cockpit](../images/ExchangeSiteCustomWatchfaces/Cockpit-CustomWatchface.png) <br>**AAPS (Cockpit)**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Cockpit.zip)                      |   [![Digital G-Watch](../images/ExchangeSiteCustomWatchfaces/Digital_G-Watch-CustomWatchface.png) <br>**Digital G-Watch**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Digital_G-Watch.zip)    |
 | [![DigitalBigGraph](../images/ExchangeSiteCustomWatchfaces/DigitalBigGraph-CustomWatchface.png) <br/>**DigitalBigGraph**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/DigitalBigGraph_v1.5.zip) |                             [![Gears](../images/ExchangeSiteCustomWatchfaces/Gears-CustomWatchface.jpg) <br>**Gears**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Gears.zip)                              |                       [![Gota](../images/ExchangeSiteCustomWatchfaces/Gota-CustomWatchface.png) <br>**Gota**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/Gota_v2.4.zip)                       |
 |      [![LuckyLoopKoeln](../images/ExchangeSiteCustomWatchfaces/LuckyLoopKoeln-CustomWatchface.png) <br>**LuckyLoopKoeln**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/LuckyLoopKoeln.zip)      |             [![P-Zero watchface](../images/ExchangeSiteCustomWatchfaces/pzero_v1.0-CustomWatchface.png) <br/>**P-Zero watchface**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/pzero_v1.0.zip)             | [![PinkFloydTheWall](../images/ExchangeSiteCustomWatchfaces/PinkFloydTheWall-CustomWatchface.png) <br/>**PinkFloydTheWall**](https://github.com/openaps/AndroidAPSdocs/raw/refs/heads/master/docs/_static/ExchangeSiteCustomWatchfaces/PinkFloydTheWall.zip) |

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. 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. 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.
 

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.
-- - - - - - - - - - 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.
 </br>
 
 ```{warning}
@@ -156,7 +156,7 @@ Sarà necessario:
 7. Ripristinare i dati da Nightscout.
 ```
 
-- - - - - - - - - - - - - - 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).
 
 </br>