From 0625e7c4a1c8eff7a721b695d5de1f21a91f91d7 Mon Sep 17 00:00:00 2001
From: Ruth John <Rumyra@users.noreply.github.com>
Date: Tue, 16 Mar 2021 12:00:45 +0000
Subject: [PATCH] Sentence case

---
 files/en-us/web/api/sensor_apis/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/files/en-us/web/api/sensor_apis/index.html b/files/en-us/web/api/sensor_apis/index.html
index 6a42eabf3d07480..112289c3393e48e 100644
--- a/files/en-us/web/api/sensor_apis/index.html
+++ b/files/en-us/web/api/sensor_apis/index.html
@@ -22,7 +22,7 @@ <h2 id="sensor_apis_concepts_and_usage">Sensor APIs concepts and usage</h2>
 
 <p>Sensors may or may not correspond exactly to a physical device sensor. For example, the {{domxref('Gyroscope')}} interface corresponds exactly to a physical device interface. Alternatively, the {{domxref('AbsoluteOrientationSensor')}} interface provides information that is algorithmically agregated from two or more device sensors. These sensor types are referred to as <em>low-level</em> and <em>high-level</em> respectively. The latter type of sensor is also called a fusion sensor (alternatively, virtual or synthetic sensors).</p>
 
-<h3 id="feature_detection">Feature Detection</h3>
+<h3 id="feature_detection">Feature detection</h3>
 
 <p>Sensor interfaces are only proxies for the underlying device sensors. Consequently, feature detection is more complicated for sensors than it is for other APIs. The presence of a sensor API does not tell you whether that API is connected to a real hardware sensor, whether that sensor works, if it's still connected, or even whether the user has granted access to it. Making all this information consistently available is costly to performance and battery life.</p>