diff --git a/docs/EN/Usage/Automation.md b/docs/EN/Usage/Automation.md
index f108b862138f..4935b858abb2 100644
--- a/docs/EN/Usage/Automation.md
+++ b/docs/EN/Usage/Automation.md
@@ -1,169 +1,300 @@
 # Automation
 
-## What is Automation
+## What is an Automation?
 
-For the same frequent events, you might always have to change the same settings. To avoid the extra work, you can just try to automate the event if you can specify it well enough and let it do it for you automatically.
+**Automation** is a feature within **AAPS** designed to simplify a user’s **AAPS** management and be personalised to fit within their lifestyle needs.
 
-I.e. when your BG is too low, you can decide to have automatically a high temp target. Or if you are at your fitness center, you get automatically a temp target.
+An **Automation** instructs **AAPS** to carry out a certain action ‘automatically’ and on a regular basis like exercise or eating soon. **Automation** can also be set up to create a rule for a one off event planned into the future, or triggered if the user is located within a certain radius distance of GPS location or WIFI SSID area.
 
-Before using Automation, you should be confident with manual [temp targets](./temptarget.html) or profile switches.
+The primary benefit of **Automation** is to relieve the user from the burden of having to constantly action a **Temp Target** or similar **AAPS** setting. According to research conduct by [*Stanford university*](https://www.stanford.edu/) there are on average per day 180 health decisions that have to be made by a user when living with Type 1 (and discussed further here:  https://www.ncbi.nlm.nih.gov/pmc/art Stanford university icles/PMC6286423/#ref4) . **Automations** can therefore help simplify diabetic management by:
 
-Make sure you really understand how automation works before setting up your first simple rule. **Instead of action, let AAPS first display only a notification.** When you are sure automation is triggered at the right time, replace notification by real action.
+* **Decrease decision fatigue:** **Automations** can lessen the mental load of constant decision-making and free up the user’s mental energy for other aspects of life.
 
-```{image} ../images/Automation_ConditionAction_RC3.png
-:alt: Automation condition + action
-```
+* **Improve adherence:** **Automations** should help ensure **AAPS** is optimised correctly in the future and avoid **Temp Targets** being missed during busy schedules or periods of forgetfulness. We have all been there!
 
-## How to use it
+* **Personalised management:** **Automations** can be tailored to the user’s specific needs and preferences, by creating a rules with **AAPS** that integrate into the user's lifestyle.
 
-To set up an automation, you have to give it a title, select at least one condition and one action.
+* **Promote data-driven decisions:** when data is gathered with **AAPS**, **Automations** will be invoked and make adjustments within the parameters as set by the user. For instance, for predicted low **BG**, the user can set an **Automation** to reduce insulin and raise **BG**.  This can lead to better diabetic management.
 
-(Automation-important-note)=
-### Important note
+The example below illustrates what steps are eliminated by an **Automation** than compared with no **Automation** set up in **AAPS**. The user has set an **Automation** to trigger a 5am ‘Temp Target Exercise’ to ensure their **BG** is at the optimal rate in time for their 6am exercise:
 
-**Automation is still active when you disable loop!**
+![Alt text](../images/automation_2024-02-12_20-54-49.png)
 
-So make sure to deactivate automation rules during these occasions if necessary. You can do so by unticking the box left of the name of your automation rule.
+However, it's important to remember that:
 
-```{image} ../images/Automation_ActivateDeactivate.png
-:alt: Activate and deactivaten automation rule
-```
+**Automations** are not a replacement for expert guidance and users should consult with their healthcare team. This is particularly so if the user feels the **Automation** is compensating for sub-optimal insulin base settings (discussed further below).
 
-### Where to find Automation
+As with any other technology, **CGMs** or **Pumps** can malfunction: Technical issues or sensor errors could disrupt the **Automation** actions, and will require manual intervention. **AAPS** should be monitored and alarms & notifications responded to.
 
-Depending on your [settings in config builder](Config-Builder-tab-or-hamburger-menu) you will either find [Automation](Config-Builder#automation) in hamburger menu or as a tab.
+Before setting up an **Automation**, a user should have a reasonable BG control within their Closed Loop as well as be comfortable with their **Temp Targets** and **Profile** settings and switches.
 
-### General
+## Why is Automation when AAPS is in Closed Loop mode?
 
-There are some limits:
+Why is **Automation** required if **AAPS** is in **Closed Loop** mode? Because even in **Closed Loop**, the user may require further flexibility to attain optimal **BG** for regular lifestyle events like: 
+Attending the exercise at a regular time: an **Automation** can be created to _automatically_  to drive **BG** to optimal level;
 
-- The glucose value has to be between 72 and 270 mg/dl or 4 and 15 mmol/l.
-- The profile percentage has to be between 70 % and 130%.
-- There is a 5 min. time limit between executions (and first execution).
 
-**Please be careful:**
+Eating a certain meal regular time, an **Automation** can be created to _automatically_ drive **BG** to optimal level;
 
-- **less than -2 means: -3 and lower (-4,-10, etc)**
-- **more than -2 means: -1 and higher (-1, 0, +10, etc)**
 
-### Condition
+For low BG, an **Automation** can be created to _automatically_ activate a high **Temp Target** .
 
-You can choose between several conditions. Here are some things explained, but most of it should be easy to understand and is not all described here:
+## When can I start using Automation?
 
-- connect conditions: you can have several conditions and can link them with
+It is recommended that new users do not rush into **Automations* without first dummy testing their proposed rule by activating the ‘notification’ option under ‘Actions’. 
 
-  - "And"
-  - "Or"
-  - "Exclusive or" (which means that if one - and only one of the - conditions applies, the action(s) will happen)
+This will trigger **AAPS** to first display to the user a notification rather than automating an action. When the user is comfortable that the notification has been triggered at the correct time, the **Automation’s** rule can be updated to replace the ‘Notification’ with a real ‘Action’.
 
-- Time vs. recurring time
+![Alt text](../images/automation_2024-02-12_20-55-05.png)
 
-  - time =  single time event
-  - recurring time = something that happens regularly (i.e. once a week, every working day etc.)
+## How to set up an Automation?
 
-- location: in the config builder (Automation), you can select which location service you want to use:
+To set up an **Automation** the user must create a ‘rule’ with **AAPS**. To do this the user must action in **AAPS**:
 
-  - Use passive location: AAPS only takes locations when other apps are requesting it
-  - Use network location: Location of your Wifi
-  - Use GPS location (Attention! May cause excessive battery drain!)
+* give their ‘rule’ a title;
+* select at least one ‘Condition’; and
+* select one ‘Action’;
+* check the right box to the **Automation** event is ‘ticked’ to ensure it is activated.
 
-### Action
+![Alt text](../images/automation_2024-02-12_20-55-35.png)
 
-You can choose one or more actions:
+:::{admonition} Important note
+:class: note
 
-- start temp target
+Automation is still active when the Loop is disabled!
+:::
 
-  - must be between 72 mg/dl and 270 mg/dl (4 mmol/l and 15 mmol/l)
-  - works only if there is no previous temp target
+To deactivate an **Automation** rule when Loop is disabled the user should untick the box left of the name of the **Automation** rule. The example below  illustration an **Automation**  entitled ‘Low Glucose TT’ as be activated (‘ticked) and deactivated (‘unticked’).
 
-- stop temp target
+![Alt text](../images/automation_2024-02-12_20-56-08.png)
 
-- notification
+## Where are Automations located in AAPS?
 
-- profile percentage
+Depending on the user’s settings in [config builder](../Installing-AndroidAPS/change-configuration.md#config-builder), an **Automation** is located in the ‘hamburger’ menu or as a tab with **AAPS**.
 
-  - must be between 70% and 130%
-  - works only if the previous percentage is 100%
+## Safety limits
 
-After adding your action, **don't forget to change the default values** to what you need by clicking in the default values.
+There are safety limits set as a general rule for **Automations**:
 
-```{image} ../images/Automation_Default_V2_5.png
-:alt: Automation default vs. set values
-```
+* The glucose value has to be between 72 and 270 mg/dl or 4 and 15 mmol/l.
+* The **Profile** percentage has to be between 70% and 130%.
+* There is a 5 minute time limit between executions of  **Automation** (and first execution).
 
-(Automation-sort-automation-rules)=
-### Sort automation rules
+:::{admonition} Warning
+:class: warning
 
-To sort automation rules click and hold the four-lines-button on the right side of the screen and move up or down.
+Please be careful when selecting a negative value in Automation
+:::
 
-```{image} ../images/Automation_Sort.png
-:alt: Sort automation rules
-```
+Caution must be taken when selecting a ‘negative value’ within the ‘Condition’ like "less than" in **Automations**. Selecting ‘less than’ with a negative value will trigger a negative number. For example:
 
-### Delete automation rules
+![Alt text](../images/automation_2024-02-12_20-56-25.png-500x.png)
 
-To delete an automation rule click on trash icon.
+**Example 1:** Creating a Condition __lesser than -1__ will:
 
-```{image} ../images/Automation_Delete.png
-:alt: Delete automation rule
-```
+* trigger an **Automation** for any number **strictly lesser than** -1. This includes numbers like -2, -3, -4 and so on.
 
-(Automation-good-practice-caveats)=
-## Good practice & caveats
+It's crucial to remember that -1 itself **is not** included in this condition. 
 
-- When you start using automation or create a new rule, first add a notification only until you are sure the rule is working well.
+**Example 2:** Creating a Condition  __more than -1__ will:
 
-- Watch the rule results.
+* trigger an **Automation**  opposite to Example 1 above. This means the Condition will be trigger any number **greater than or equal to -1**.
 
-- Don't try to make conditions too easy (i.e.: IF bg > 80 mg/dl AND bg \< 180 mg/dl)
+This includes numbers like 0, 1, 10, and any other positive number.
 
-  **Doubly important if action is a profile switch!**
+It is therefore important to carefully consider the intention of your **Automation** when choosing a value. Selecting the wrong combination could lead to unintended consequences.
 
-- Try to use Temp Targets instead of Profile Switches. Temp Targets do not reset [Autosens](Open-APS-features-autosens) back to 0.
+## Condition
 
-- Make sure Profile switches are made sparingly and preferably at a last resort.
+There are various ‘Conditions’ that can be selected by the user in  **Automation*. The list below is non exhaustive:
 
-  - Profile switching renders [Autosens](Open-APS-features-autosens) useless for a min of 6 hours.
+**Condition:** connect conditions
 
-- Profile switching will not reset the profile back to your base profile
+**Options:** 
 
-  - You have to make another rule to set this back or do it manually!
-  - Increased risk of hypoglycemia if profile switch does not expire or reset back to base profile.
+Several conditions can be linked with
+* “And”
+* “Or”
+* “Exclusive or” (which means that if one - and only one of the - conditions applies, the action(s) will happen)
 
-## Examples
+**Condition:** time vs. recurring time
 
-These are just setup examples, no advises. Don't reproduce them without being aware what you are actually doing or why you need them.
+**Options:** 
 
-- Switching profiles for your daily activities (like school, gym, weekend, workday...) using geolocation, wifi, time etc.
-- Setting temp target for activities based on time, location, connection to a bluetooth device...
-- Setting eating soon temp targets based on time, location...
+* time = single time event
+* recurring time = something that happens regularly (i.e. once a week, every working day etc.)
+
+**Condition:** location
+
+**Options:**
+
+* in the **config builder** (Automation), the user can select their required location service..
+
+**Condition:** location service
+
+**Options:**
+
+* Use passive location: **AAPS** only takes locations when other apps are requesting it.
+* Use network location: Location of your Wifi.
+* Use GPS location (Attention! This can cause excessive battery drain!)
+
+## Action
+
+**Actions:** start **Temp Target**
+
+**Options:** 
+
+* **BG** must be between 72 mg/dl and 270 mg/dl (4 mmol/l and 15 mmol/l)
+* **TT** works only if there is no previous Temp Target
+
+**Actions:** stop **Temp Target**
+
+**Options:**
+
+none
+
+**Actions:** **Profile** percentage
+
+**Options:**
+
+* **Profile** must be between 70% and 130%
+* works only if the previous percentage is 100%
+
+Once the ‘Action’ is added,  the default values must be changed to the desired number by clicking and adjusting the default values.
+
+![Alt text](../images/automation_2024-02-12_20-57-07.png)
+
+![Alt text](../images/automation_2024-02-12_20-57-29.png)
+
+## Reprioritising Automation rules to improve AAPS’ performance
+
+ The performance of **AAPS** can be affected by the set up arrangement organised for **Automations** rules. **AAPS** will automate the rules created in the order of preference in a sliding scale starting from the top of the user’s  **Automation** list. For example, if the ‘low hypoglycemia’  **Automation** is the most preferred  **Automation**, above all other rules, then this  **Automation** should appear at the top of the user’s **Automation** list as demonstrated below:
+
+
+![Alt text](../images/automation_2024-02-12_20-57-48.png-500x.png)
+
+To reprioritise the **Automation** rules, click and hold the four-lines-button on the right side of the screen and reorganise the  **Automations** by moving the rules up or down.
+
+![Alt text](../images/automation_2024-02-12_20-58-00.png-500x.png)
+
+## How to delete Automation rules
+
+To delete an **Automation** rule click on the trash icon.
+
+![Alt text](../images/automation_2024-02-12_20-58-26.png-500x.png)
+
+## Best practice & caveats
+
+* When using **Automation** for the first time, create a new rule, first add a notification only until you are sure the rule is working effectively.  Watch the **Automation** results.
+* Do not try to make the ‘conditions’ too easy (i.e.: IF BG > 80 mg/dl AND bg < 180 mg/dl) as otherwise it is unlikely the **Automation**will be triggered. This is important if the ‘action’ is a Profile switch!
+* Try to use **Temp Targets** instead of **Profile Switches**. 
+**Temp Targets** do not reset Autosens back to 0.
+* Make sure **Profile Switches** are used sparingly and preferably as a last resort. **Profile Switches** renders Autosens useless for a minimum of 6 hours.
+* **Profile Switches** will not reset the **Profile** back to the user’s base Profile
+* The user must must create another **Automation** rule to revert to the original**Profile**. Otherwise. the user must action the **Profile**  switch manually!
+* **Profile Switches** actioned by an **Automation** should be used sparingly. Frequent use of  **Profile Switches** could be indicative of an underperforming diabetic management due to poor **AAPS** set up.
+* There is increased risk of hypoglycemia if the**Profile Switches** does  not expire or reset back to the user’s base **Profile**.
+
+
+## Examples of Automations created
+
+Below are examples of **Automations** created. Further discussion on **Automations** and how users have individualised their  **Automation** can be found in Facebook discussions groups or on Discord. 
+
+As explained above, users should style their **Automation** to suit their own demands and needs.  The examples below should not be replicated without the user having a good understanding of the rudimentals **Automation**, it's potential impact it can have on their **AAPS** management.  The rules should not be replicated by users without dummy testing (as discussed above) and checking if these parameters below are correct for them. Diabetic management varies from user to user, especially in **AAPS**.
 
 ### Low Glucose Temp Target
 
-```{image} ../images/Automation2.png
-:alt: Automation2
-```
+This **Automation**  triggers an automatic ‘Temp Target Hypo’ when low **BG** is at a certain threshold. 
+
+![Alt text](../images/automation_2024-02-12_21-04-01.png-500x.png)
+
+### Lunch Time Temp Target (with ‘Location’)
+
+![Alt text](../images/automation_2024-02-12_21-04-25.png-500x.png)
+
+This **Automation** has been created for a user who eats their lunch at work around the same time every weekday but triggered only if the user is situated within a set ‘location’.  So if the user is not at work one day, this Automation will be activated.
+
+This **Automation** will set a low Temp Target (Eating Soon) at 13:00 to drive ‘BG, to 90mg (or 5 mmls) in preparation for lunch. 
+
+The ‘Trigger’ location is set by inputting the latitude and longitude GPS coordinates as below:
+
+![Alt text](../images/automation_2024-02-12_21-04-40.png-500x.png)
+
+Because of the ‘And’ connection, the **Automation** only happens during the ‘chosen time’ and if the user is at the selected location. 
+
+The **Automation** will not be triggered on any other time at this location or on this time outside of 100 metres set GPS coordinates.
+
+### WIFI SSID Location Automation
+
+Using WIFI SSID is a good option to trigger an **Automation** while within range of a specific wifi network (than compared with GPS), it is fairly precise, uses less battery and works in enclosed spaces where GPS and other location services might not be available.   
+
+Here is another example of setting up a **Temp Target** for work days only before breakfast(1). 
+
+
+The **Automation** will trigger at 05:30am only on Monday-Friday(2)  
+and while being connected to a home wifi network (3).
 
-This is made by someone who wants to get a hypo temp target automatically when having low glucose.
 
-### Lunch Time Temp Target
+It will then set a**Temp Target**  of 75mg/dl for 30 minutes (4). 
+One of the advantages of including the location is that it will not trigger if the user is travelling on vacation for instance. 
 
-```{image} ../images/Automation3.png
-:alt: Automation3
-```
+![Alt text](../images/automation_2024-02-12_21-05-02.png-500x.png)
 
-This example is made by someone who has lunch at work at the same time every day during the week. If he or she stays at a certain time in his or her lunch location, automation will set a low temp target (eating soon) while waiting for the lunch. Because of the "And" connection, it only happens during the chosen time and if he or she is at the chosen location. So it does not work on any other time at this location or on this time when the person stays at home.
+Here is the screenshot detailing the **Automation**  triggers:
 
-### Incorrect use of automation
+1) Under the main “AND” (both conditions need to be met to trigger)
+1) Recurring time = M,T,W,T,F At 5:30am  
+1) WIFI SSID = My_Home_Wifi_Name
 
-Please be aware to use automation incorrectly. This might lead to difficulties and even danger for your health. Examples for incorrect use are for instance:
+![Alt text](../images/automation_2024-02-12_21-05-16.png-500x.png)
 
-- Trying to override algorithm at all instead of help only (i.e. by changing profile instead of tunning basal, IC etc.)
-- Setting profile to compensate food
-- Setting profile without duration
-- Creating one way rules (i.e. do something but don't undo it by another rule)
-- Creating long term rules
+## Incorrect use of Automation
+
+Using **Automation** incorrectly can lead to difficulties and even danger to the user’s health. Examples for incorrect use are instance:
+* Trying to constantly override **AAPS** rather than pause and properly evaluate the users **Profile** and tuning basal, IC etc.
+* Setting a **Profile switch** to compensate for the food.
+* Setting a **Profile switch** without inputting a duration.
+* Creating one way rules (i.e. failing to create another rule in order to undo the original rule).
+* Creating long term rules.
+
+## Automation Logs
+
+**AAPS** has a log of the most recent **Automation** triggered at the bottom of the screen under the **Automation** tab. 
+
+In the example below the logs indicate:
+
+(1) at 01:58 am, the “Low BG triggers temp hypo profile” is activated 
+* glucose value is less than 75mg/dl;
+* delta is negative (ie: the BG is going down);
+* time is within 01:00 am and 06:00 am.
+
+The **Automation** will:
+* set a **Temp Target** to 110mg/dl for 40 minutes;
+* start a temporary **Profile** at 50% for 40 minutes.
+
+(2) at 03:38 am,  the “High carb after low at night” is triggered
+* time is between 01:05 am and 06:00 am;
+* glucose value is greater than 110mg/dl. .
+
+The **Automation** will:
+* change **Profile** to LocalProfile1 (ie: cancel the temporary profile if any)
+* stop **Temp Target** (if any)
+
+![Alt text](../images/automation_2024-02-12_21-05-56.png-500x.png)
+
+## Troubleshooting
+
+* Problem: __My automations are not being triggered by AAPS?__
+
+Check the box to the right of  **Automation** event is ‘ticked’ to ensure the rule is activated.
+
+![Alt text](../images/automation_2024-02-12_21-06-12.png-500x.png)
+
+* Problem: __My automations are being triggered in the wrong order.__
+
+Check your rule prioritisation order as discussed above here.
 
 ## Alternatives
 
-For advanced users, there are other possibilities to automate tasks using IFTTT or a third party Android app called Automate. Some examples can be found [here](./automationwithapp.html).
+For advanced users, there are other possibilities to automate tasks using IFTTT or a third party Android app called Automate. Some examples can be found here.
+
diff --git a/docs/EN/Usage/automation_2024-02-12_20-54-49.png b/docs/EN/Usage/automation_2024-02-12_20-54-49.png
new file mode 100644
index 000000000000..3ae39bb7bdd8
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_20-54-49.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_20-55-05.png b/docs/EN/Usage/automation_2024-02-12_20-55-05.png
new file mode 100644
index 000000000000..8fbba53ac755
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_20-55-05.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_20-55-35.png b/docs/EN/Usage/automation_2024-02-12_20-55-35.png
new file mode 100644
index 000000000000..6e3663bb0d59
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_20-55-35.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_20-56-08.png b/docs/EN/Usage/automation_2024-02-12_20-56-08.png
new file mode 100644
index 000000000000..c144122594c5
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_20-56-08.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_20-56-25.png b/docs/EN/Usage/automation_2024-02-12_20-56-25.png
new file mode 100644
index 000000000000..b312bc6534e7
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_20-56-25.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_20-57-07.png b/docs/EN/Usage/automation_2024-02-12_20-57-07.png
new file mode 100644
index 000000000000..d065ddf9c027
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_20-57-07.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_20-57-29.png b/docs/EN/Usage/automation_2024-02-12_20-57-29.png
new file mode 100644
index 000000000000..738415987100
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_20-57-29.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_20-57-48.png b/docs/EN/Usage/automation_2024-02-12_20-57-48.png
new file mode 100644
index 000000000000..b91bcb32d3a8
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_20-57-48.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_20-58-00.png b/docs/EN/Usage/automation_2024-02-12_20-58-00.png
new file mode 100644
index 000000000000..f24c3db14c2e
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_20-58-00.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_20-58-26.png b/docs/EN/Usage/automation_2024-02-12_20-58-26.png
new file mode 100644
index 000000000000..78c65b0f9794
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_20-58-26.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_21-04-01.png b/docs/EN/Usage/automation_2024-02-12_21-04-01.png
new file mode 100644
index 000000000000..cec11c69a2ea
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_21-04-01.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_21-04-25.png b/docs/EN/Usage/automation_2024-02-12_21-04-25.png
new file mode 100644
index 000000000000..cbdfb0f840b3
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_21-04-25.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_21-04-40.png b/docs/EN/Usage/automation_2024-02-12_21-04-40.png
new file mode 100644
index 000000000000..ec9fad1d95f4
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_21-04-40.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_21-05-02.png b/docs/EN/Usage/automation_2024-02-12_21-05-02.png
new file mode 100644
index 000000000000..7bf2a121ac77
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_21-05-02.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_21-05-16.png b/docs/EN/Usage/automation_2024-02-12_21-05-16.png
new file mode 100644
index 000000000000..71d56024dbcf
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_21-05-16.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_21-05-56.png b/docs/EN/Usage/automation_2024-02-12_21-05-56.png
new file mode 100644
index 000000000000..3684643c0ded
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_21-05-56.png differ
diff --git a/docs/EN/Usage/automation_2024-02-12_21-06-12.png b/docs/EN/Usage/automation_2024-02-12_21-06-12.png
new file mode 100644
index 000000000000..92bfafe58c8e
Binary files /dev/null and b/docs/EN/Usage/automation_2024-02-12_21-06-12.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-54-49.png b/docs/EN/images/automation_2024-02-12_20-54-49.png
new file mode 100644
index 000000000000..3ae39bb7bdd8
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-54-49.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-55-05.png b/docs/EN/images/automation_2024-02-12_20-55-05.png
new file mode 100644
index 000000000000..8fbba53ac755
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-55-05.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-55-35.png b/docs/EN/images/automation_2024-02-12_20-55-35.png
new file mode 100644
index 000000000000..6e3663bb0d59
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-55-35.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-56-08.png b/docs/EN/images/automation_2024-02-12_20-56-08.png
new file mode 100644
index 000000000000..c144122594c5
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-56-08.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-56-25.png b/docs/EN/images/automation_2024-02-12_20-56-25.png
new file mode 100644
index 000000000000..b312bc6534e7
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-56-25.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-56-25.png-500x.png b/docs/EN/images/automation_2024-02-12_20-56-25.png-500x.png
new file mode 100644
index 000000000000..6b28576229ad
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-56-25.png-500x.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-57-07.png b/docs/EN/images/automation_2024-02-12_20-57-07.png
new file mode 100644
index 000000000000..d065ddf9c027
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-57-07.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-57-29.png b/docs/EN/images/automation_2024-02-12_20-57-29.png
new file mode 100644
index 000000000000..738415987100
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-57-29.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-57-48.png b/docs/EN/images/automation_2024-02-12_20-57-48.png
new file mode 100644
index 000000000000..b91bcb32d3a8
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-57-48.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-57-48.png-500x.png b/docs/EN/images/automation_2024-02-12_20-57-48.png-500x.png
new file mode 100644
index 000000000000..698be1368d58
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-57-48.png-500x.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-58-00.png b/docs/EN/images/automation_2024-02-12_20-58-00.png
new file mode 100644
index 000000000000..f24c3db14c2e
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-58-00.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-58-00.png-500x.png b/docs/EN/images/automation_2024-02-12_20-58-00.png-500x.png
new file mode 100644
index 000000000000..4975505e078f
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-58-00.png-500x.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-58-26.png b/docs/EN/images/automation_2024-02-12_20-58-26.png
new file mode 100644
index 000000000000..78c65b0f9794
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-58-26.png differ
diff --git a/docs/EN/images/automation_2024-02-12_20-58-26.png-500x.png b/docs/EN/images/automation_2024-02-12_20-58-26.png-500x.png
new file mode 100644
index 000000000000..bde5f66498f6
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_20-58-26.png-500x.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-04-01.png b/docs/EN/images/automation_2024-02-12_21-04-01.png
new file mode 100644
index 000000000000..cec11c69a2ea
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-04-01.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-04-01.png-500x.png b/docs/EN/images/automation_2024-02-12_21-04-01.png-500x.png
new file mode 100644
index 000000000000..19d27582f063
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-04-01.png-500x.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-04-25.png b/docs/EN/images/automation_2024-02-12_21-04-25.png
new file mode 100644
index 000000000000..cbdfb0f840b3
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-04-25.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-04-25.png-500x.png b/docs/EN/images/automation_2024-02-12_21-04-25.png-500x.png
new file mode 100644
index 000000000000..51f66e1d7746
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-04-25.png-500x.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-04-40.png b/docs/EN/images/automation_2024-02-12_21-04-40.png
new file mode 100644
index 000000000000..ec9fad1d95f4
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-04-40.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-04-40.png-500x.png b/docs/EN/images/automation_2024-02-12_21-04-40.png-500x.png
new file mode 100644
index 000000000000..a776beb3eb2d
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-04-40.png-500x.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-05-02.png b/docs/EN/images/automation_2024-02-12_21-05-02.png
new file mode 100644
index 000000000000..7bf2a121ac77
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-05-02.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-05-02.png-500x.png b/docs/EN/images/automation_2024-02-12_21-05-02.png-500x.png
new file mode 100644
index 000000000000..90607dd5912d
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-05-02.png-500x.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-05-16.png b/docs/EN/images/automation_2024-02-12_21-05-16.png
new file mode 100644
index 000000000000..71d56024dbcf
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-05-16.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-05-16.png-500x.png b/docs/EN/images/automation_2024-02-12_21-05-16.png-500x.png
new file mode 100644
index 000000000000..6defe892b593
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-05-16.png-500x.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-05-56.png b/docs/EN/images/automation_2024-02-12_21-05-56.png
new file mode 100644
index 000000000000..3684643c0ded
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-05-56.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-05-56.png-500x.png b/docs/EN/images/automation_2024-02-12_21-05-56.png-500x.png
new file mode 100644
index 000000000000..a74e67641061
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-05-56.png-500x.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-06-12.png b/docs/EN/images/automation_2024-02-12_21-06-12.png
new file mode 100644
index 000000000000..92bfafe58c8e
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-06-12.png differ
diff --git a/docs/EN/images/automation_2024-02-12_21-06-12.png-500x.png b/docs/EN/images/automation_2024-02-12_21-06-12.png-500x.png
new file mode 100644
index 000000000000..0c1b7d9d0bd8
Binary files /dev/null and b/docs/EN/images/automation_2024-02-12_21-06-12.png-500x.png differ