From 63a08cd550560c7436b589097a9c4232eb7c4fd5 Mon Sep 17 00:00:00 2001
From: Trefor Southwell <48591903+springfall2008@users.noreply.github.com>
Date: Sat, 27 Jan 2024 13:57:03 +0000
Subject: [PATCH 1/2] Update customisation.md

---
 docs/customisation.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/docs/customisation.md b/docs/customisation.md
index e3822ecf9..8c3c096e5 100644
--- a/docs/customisation.md
+++ b/docs/customisation.md
@@ -148,11 +148,12 @@ a single low usage day in your average calculation. By default is feature is ena
 Car charging hold is a feature where you try to filter out previous car charging from your historical data so that
 future predictions are more accurate.
 
-When **car_charging_hold** is enabled loads of above the power threshold **car_charging_threshold** then you are
-assumed to be charging the car and **car_charging_rate** will be subtracted from the historical load data.
+When **car_charging_hold** is enabled when for loads of above the power threshold **car_charging_threshold** are
+assumed to be car charging and **car_charging_rate** will be subtracted from the historical load data.
 
-For more accurate results can you use an incrementing energy sensor set with **car_charging_energy** in the apps.yml
-then historical data will be subtracted from the load data instead.
+For more accurate results can you use an incrementing energy sensor set with **car_charging_energy** in the apps.yml 
+In this case when **car_charging_hold** is enabled historical data will be subtracted from the load data instead of using
+the fixed threshold method.
 
 **car_charging_energy_scale** Is used to scale the **car_charging_energy** sensor, the default units are kWh so
 if you had a sensor in watts you might use 0.001 instead.

From 4f6e7b3de9a4da262579fe32c44d6000b3be016d Mon Sep 17 00:00:00 2001
From: "pre-commit-ci-lite[bot]"
 <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
Date: Sat, 27 Jan 2024 13:58:33 +0000
Subject: [PATCH 2/2] [pre-commit.ci lite] apply automatic fixes

---
 docs/customisation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/customisation.md b/docs/customisation.md
index 8c3c096e5..e39ac0026 100644
--- a/docs/customisation.md
+++ b/docs/customisation.md
@@ -151,7 +151,7 @@ future predictions are more accurate.
 When **car_charging_hold** is enabled when for loads of above the power threshold **car_charging_threshold** are
 assumed to be car charging and **car_charging_rate** will be subtracted from the historical load data.
 
-For more accurate results can you use an incrementing energy sensor set with **car_charging_energy** in the apps.yml 
+For more accurate results can you use an incrementing energy sensor set with **car_charging_energy** in the apps.yml
 In this case when **car_charging_hold** is enabled historical data will be subtracted from the load data instead of using
 the fixed threshold method.