diff --git a/i18n/en/docusaurus-plugin-content-docs/current/reference/configuration/vehicles.mdx b/i18n/en/docusaurus-plugin-content-docs/current/reference/configuration/vehicles.mdx
index be29ceb0f..17cb8f86f 100644
--- a/i18n/en/docusaurus-plugin-content-docs/current/reference/configuration/vehicles.mdx
+++ b/i18n/en/docusaurus-plugin-content-docs/current/reference/configuration/vehicles.mdx
@@ -10,7 +10,7 @@ import SponsorshipRequired from "/docs/_sponsorship_required.mdx";
 
 A vehicle represents a specific electric vehicle (EV) with its battery. When a vehicle is configured and assigned to a [charger](loadpoints#vehicle), the user interface can display the charging status, state of charge (SoC), remaining charging time, and other data automatically retrieved and processed from the vehicle.
 
-It is also possible to limit the charge to a specific state of charge (SoC). Since most chargers cannot be aware of this (it is only transmitted in very specific charger combinations), evcc can communicate directly with the vehicle through the online interface (API) of the vehicle manufacturer using this configuration.
+It is also possible to limit the charge to a specific state of charge (SoC, UI only). Since most chargers cannot be aware of this (it is only transmitted in very specific charger combinations), evcc can communicate directly with the vehicle through the online interface (API) of the vehicle manufacturer using this configuration.
 
 The `vehicles` configuration is a list of different vehicles.