Fix typo in sensor documentation.

PiperOrigin-RevId: 633872551
Change-Id: I033a8227c19da2feebf286f4b3c24635f5625372
This commit is contained in:
Kyle Bayes
2024-05-15 03:02:22 -07:00
committed by Copybara-Service
parent b8a8d811e1
commit 6e58cedb47
+3 -3
View File
@@ -6787,7 +6787,7 @@ See :ref:`collision-sensors` for more details about sensors of this type.
.. _sensor-distance-cutoff:
:at:`cutoff`
See :ref:`collision-sensors` for the sematics of this attribute, which is different than for other sensor catagories.
See :ref:`collision-sensors` for the sematics of this attribute, which is different than for other sensor categories.
If no collision is detected, the distance sensor returns the :at:`cutoff` value, so in this case
:at:`cutoff` acts as a maximum clipping value, in addition to the special semantics.
@@ -6834,7 +6834,7 @@ See :ref:`collision-sensors` for more details about sensors of this type.
.. _sensor-normal-cutoff:
:at:`cutoff`
See :ref:`collision-sensors` for the sematics of this attribute, which is different than for other sensor catagories.
See :ref:`collision-sensors` for the sematics of this attribute, which is different than for other sensor categories.
If no collision is detected, the :ref:`normal<sensor-normal>` sensor returns (0, 0, 0), otherwise it returns a
normalized direction vector. For this sensor, :at:`cutoff` does not lead to any clamping.
@@ -6882,7 +6882,7 @@ See :ref:`collision-sensors` for more details about sensors of this type.
.. _sensor-fromto-cutoff:
:at:`cutoff`
See :ref:`collision-sensors` for the sematics of this attribute, which is different than for other sensor catagories.
See :ref:`collision-sensors` for the sematics of this attribute, which is different than for other sensor categories.
If no collision is detected, the :ref:`fromto<sensor-fromto>` sensor returns 6 zeros.
For this sensor, :at:`cutoff` does not lead to any clamping.