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 @@

Sensor APIs concepts and usage

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 low-level and high-level respectively. The latter type of sensor is also called a fusion sensor (alternatively, virtual or synthetic sensors).

-

Feature Detection

+

Feature detection

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.