Philoul · Philoul · Oct 21, 2025 · Oct 9, 2025 · Oct 9, 2025 · Oct 9, 2025
diff --git a/.readthedocs.yaml b/.readthedocs.yaml
@@ -15,3 +15,4 @@ python:
 sphinx:
   builder: html
   fail_on_warning: false
+  configuration: docs/EN/conf.py
diff --git a/README.md b/README.md
@@ -14,4 +14,4 @@ The current build logs of the documentation can be found in [Github Actions](htt
 
 ### Broken links
 
-Detail of broken links in the doc can be found in the build logs. Select a build in Github Action "Deploy", then "Usage". Click on "build" and expand again the "Build line". Search for "WARNING".
+Detail of broken links in the doc can be found in the build logs. Select a build in Github Action "Deploy", then "Usage". Click on "build" and expand again the "Build line". Search for "WARNING".
diff --git a/docs/CROWDIN/cs/404.md b/docs/CROWDIN/cs/404.md
@@ -1,7 +1,3 @@
-- - -
-orphan: true
-- - -
-
 ![Page not found](./images/404.png)
 
 # Page not found

diff --git a/docs/CROWDIN/cs/AdvancedOptions/Autotune.md b/docs/CROWDIN/cs/AdvancedOptions/Autotune.md
@@ -1,8 +1,8 @@
 # How to use Autotune plugin (dev only)
 
-Documentation about Autotune algorythm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html).
+Documentation about Autotune algorithm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html).
 
-Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS.
+Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
 
 **Currently Autotune Plugin is only available in [dev branch](../AdvancedOptions/DevBranch.md) and with Engineering mode.**
 
@@ -18,7 +18,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS.
   - Note: each time you change Tune days parameter, previous results will be removed
 - Last Run is a link that recover your latest valid calculation. If you didn't launch Autotune on current day, or if previous results was removed with a modification of calculation parameter above, then you can recover parameters and results of the latest successful run.
 - Warning show you for example some information about selected profile (if you have several IC values or several ISF values)
-  - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorythm to tune a circadian IC or circadian ISF. If your input profile  has several values, you can see in warning section the average value taken into account to tune your profile.
+  - Note: Autotune calculation works with only a single IC and a single ISF value. There is currently no existing Autotune algorithm to tune a circadian IC or circadian ISF. If your input profile  has several values, you can see in warning section the average value taken into account to tune your profile.
 - Check Input Profile button open the Profile Viewer to allow you a quick verification of your profile (Units, DIA, IC, ISF, basal and target)
   - Note: Autotune will only tune your IC (single value), ISF (single value) and basal (with circadian variation). Units, DIA and target will remain unchanged in output profile.
 
@@ -43,7 +43,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS.
 
 - The "Compare profiles" button open the profile comparator view. Input profile is in blue, and output profile (named "Tuned") is in red.
 
-  - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+  - Note: in the example below input profile has circadian variation for IC and ISF, but output calculated profile has a single value. If it's important for you to get a circadian output profile see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
 
   ![Autotune Compare profiles](../images/Autotune/Autotune_5.png)
 
@@ -86,13 +86,13 @@ Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS.
 
 ![Autotune default screen](../images/Autotune/Autotune_11.png)
 
-- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated.
+- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#autotune-run-autotune-with-an-automation-rule) below. If you change this setting to On, the input profile will automatically be updated by the Tuned profile, and it will be activated.
   - **Be Careful, you must trust and verify during several following days, that after an update and activation of Tuned profile without modification, it improves your loop**
 
 - Categorize UAM as basal (default On): This setting is for the users using AndroidAPS without any carbs entered (Full UAM). It will prevent (when Off) to categorize UAM as basal.
   - Note: if you have at least one hour of Carbs absorption detected during one day, then all data categorized as "UAM" will be categorized as basal, whatever this setting (On or Off)
 - Number of days of data (default 5): You can define default value with this setting. Each time your select a new profile in Autotune plugin, Tune days parameter will be replaced by this default value
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#autotune-circadian-ic-or-isf-profile) below.
 
 ### Other settings
 
@@ -120,7 +120,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorythm within AAPS.
 
 ### Tune specific days of the week
 
-- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation)
+- If you click on the checkbox with the eye on the right of "Tune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation)
   - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below)
   - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation)
 
@@ -178,19 +178,19 @@ Always use Autotune several days manually to check results before applying them.
 
 It's also important to analyse Autotune results to understand (or try to understand) why Autotune propose these modifications
 
-- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more agressivity required) or below 100% (you are more sensitive)
-- Sometimes Autotune propose a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF)
+- you can have a whole increase or decrease of the strength of your profile (for example increase of total basal associated to decrease of ISF and IC values). it could be associated to several following days with autosens correction above 100% (more aggressivity required) or below 100% (you are more sensitive)
+- Sometimes Autotune proposes a different balance between basal rates and IC/ISF (for ex lower basal and more aggressive IC/ISF)
 
 We advise to not use Autotune in the following cases:
 
 - You don't enter all your carbs
-  - If you don't enter carbs correction for an hypoglycemia, Autotune will see an unexpected increase of your BG value and will increase your basal rates the 4 hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carbs especially correction for hypo.
-- You have a lot of period with UAM detected during the day.
-  - Do you have entered all your carbs and correctly estimated your Carbs ?
+  - If you don't enter carbs correction for hypoglycemia, Autotune will see an unexpected increase of your BG value and will increase your basal rates 4 hours earlier, it could be the opposite of what you need to avoid hypo, especially if it's in the middle of the night. That's why it's important to enter all carbs, especially correction for hypo.
+- You have a lot of periods with UAM detected during the day.
+  - Do you have entered all your carbs and correctly estimated your Carbs?
   - All UAM periods (except if you enter no carbs during a day and categorized UAM as basal is disabled), all your UAM periods will be categorized as basal, this can increase a lot your basal (much more than necessary)
 
 - Your carbs absorption is very slow: if most of your carbs absorption are calculated with min_5m_carbimpact parameter (you can see these periods with a little orange dot in the top of COB curve), the calculation of COB could be wrong and leads to wrong results.
   - When you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercise, it's usual to see some periods with slow carbs. But if you have too often unexpected slow carb absorption, then you may need a profile adjustment (higher value of IC) or a min_5m_carbimpact a bit too high.
-- You have a "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you got long periods of wrong BG values. If during the pas weeks you only have one or 2 "bad days", you can disable manually these days in autotune calculation to exclude them from calculation, and again **check carefully if you can trust the results**
+- You have "very bad days", for example stuck several hours in hyperglycemia with a huge amount of insulin to be able to go down within the range, or after a sensor change you have long periods of wrong BG values. If during the past weeks you only have one or 2 "bad days", you can disable manually these days in autotune calculation to exclude them from calculation, and again **check carefully if you can trust the results**
 - If the percentage of modification is too important
-  - You can try to increase the number of days to get smoother results
+  - You can try to increase the number of days to get smoother results
diff --git a/docs/CROWDIN/cs/AdvancedOptions/DevBranch.md b/docs/CROWDIN/cs/AdvancedOptions/DevBranch.md
@@ -11,4 +11,48 @@ Nicméně Dev větev je dobré místo, kde se ukazují testované funkce a můž
 
 Pokud najdete chybu nebo si myslíte, že se stalo něco špatného při používání Dev větve, pak se podívejte na záložku [Issues](https://github.com/nightscout/AndroidAPS/issues), abyste prověřili, jestli to už nenahlásil někdo jiný, pokud ne, tak problém rovnou nahlaste. The more information you can share here the better (don't forget you may need to share your [log files](../GettingHelp/AccessingLogFiles.md). O nových funkcích můžete diskutovat také na [Discordu](https://discord.gg/4fQUWHZ4Mw).
 
-Verze pro vývojáře má konečný datum vypršení platnosti. To se zdá nepříjemné při jeho uspokojivém používání, ale má to svůj smysl. Když je rozšířena pouze jedna vývojářská verze, je snažší sledovat nahlášené chyby. Vývojáři nechtějí být v situaci, kdy jsou mezi lidmi 3 různé vývojářské verze, v některých jsou opravené chyby a v jiných nejsou, a lidé stále znovu hlásí již vyřešené chyby.
+Verze pro vývojáře má konečný datum vypršení platnosti. To se zdá nepříjemné při jeho uspokojivém používání, ale má to svůj smysl. Když je rozšířena pouze jedna vývojářská verze, je snažší sledovat nahlášené chyby. Vývojáři nechtějí být v situaci, kdy jsou mezi lidmi 3 různé vývojářské verze, v některých jsou opravené chyby a v jiných nejsou, a lidé stále znovu hlásí již vyřešené chyby.
+
+(github-pr-test)=
+
+## Test items in a pull request (GitHub CI actions deploy)
+
+Available from 3.3.2.1.dev
+
+- Suitable for testers or those helping with testing.
+
+```{eval-rst}
+.. raw:: html
+
+    <!--crowdin: exclude-->
+    <div align="center" style="max-width: 360px; margin: auto; margin-bottom: 2em;">
+      <div style="position: relative; width: 100%; aspect-ratio: 9/16;">
+        <iframe
+          src="https://www.dailymotion.com/embed/video/x9rdx1q"
+          style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"
+          frameborder="0"
+          allowfullscreen>
+        </iframe>
+      </div>
+    </div>
+```
+
+![aaps_ci_pr_ci](../images/Building-the-App/CI/aaps_ci_pr_ci.png)
+
+- PR number: Please enter the PR number that you want to test.
+
+- PR reference types: PR reference types include two options:
+
+    - head:
+    - Fetches the actual content from the PR author’s branch (i.e., the original commit history without any merge operations).
+    - This is equivalent to the original state of the PR branch, as if it were fetched directly from a fork or feature branch.
+
+    - merge:
+
+    - Fetches the result of GitHub’s pre-simulated merge of the PR into the target branch (e.g., dev).
+    - This is a virtual merge commit automatically created by GitHub.
+    - This commit only exists when the PR has no conflicts and is mergeable.
+
+    - variant:
+
+    - Please refer to <variant>
diff --git a/docs/CROWDIN/cs/AdvancedOptions/EnablingEngineeringModeInXdrip.md b/docs/CROWDIN/cs/AdvancedOptions/EnablingEngineeringModeInXdrip.md
@@ -1,9 +1,3 @@
-* * *
-
-orphan: true
-
-* * *
-
 <head>
   <meta http-equiv="Refresh" content="0; URL=https://navid200.github.io/xDrip/docs/Engineering-Mode.html" />
 </head>
Original file line number	Diff line number	Diff line change
Expand Up		@@ -14,4 +14,4 @@ The current build logs of the documentation can be found in [Github Actions](htt

		### Broken links

		Detail of broken links in the doc can be found in the build logs. Select a build in Github Action "Deploy", then "Usage". Click on "build" and expand again the "Build line". Search for "WARNING".
		Detail of broken links in the doc can be found in the build logs. Select a build in Github Action "Deploy", then "Usage". Click on "build" and expand again the "Build line". Search for "WARNING".