From c4a496f9f00430ddcd61ddd6c6288bd1686c1f7e Mon Sep 17 00:00:00 2001
From: yousaf465 <83491212+yousaf465@users.noreply.github.com>
Date: Tue, 3 Dec 2024 23:38:09 +0500
Subject: [PATCH] Update bh1750.rst

fixed
---
 components/sensor/bh1750.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/components/sensor/bh1750.rst b/components/sensor/bh1750.rst
index 5e3165ca6c..307087611d 100644
--- a/components/sensor/bh1750.rst
+++ b/components/sensor/bh1750.rst
@@ -47,7 +47,7 @@ I²C Configuration when using Higher I²C Frequencies
 
 When using the **IDF framework** and **I²C frequencies greater than 50-100kHz**, the I²C configuration needs to include a **timeout** option.
 On an ESP32, the Arduino framework has a default I²C timeout of 50ms whereas on IDF framework, the default timeout is 100us.
-At these higher I²C frequencies, the default I²C timeout on IDF framework causes a "Communication with SHT3xD failed" error on setup.
+At these higher I²C frequencies, the default I²C timeout on IDF framework causes a "Communication with BH1750 failed!" error on setup.
 A solution that has been tested on ESP32 at 800kHz, is to increase the I²C timeout to 10ms as per the following example.
 
 .. code-block:: yaml