improve depthmeter comment

Author: Wumpf

crates/re_types/definitions/rerun/archetypes/depth_image.fbs

@@ -35,7 +35,7 @@ table DepthImage (
   /// For instance: with uint16, perhaps meter=1000 which would mean you have millimeter precision
   /// and a range of up to ~65 meters (2^16 / 1000).
   ///
-  /// Note that the effect on 2D views is what physical depth values are shown when interacting with the image,
+  /// Note that the only effect on 2D views is the physical depth values shown when hovering the image.
   /// In 3D views on the other hand, this affects where the points of the point cloud are placed.
   meter: rerun.components.DepthMeter ("attr.rerun.component_optional", nullable, order: 3100);
 

crates/re_types/definitions/rerun/components/depth_meter.fbs

@@ -15,7 +15,7 @@ namespace rerun.components;
 /// For instance, if a depth map uses millimeters and the world uses meters,
 /// this value would be `1000`.
 ///
-/// Note that the effect on 2D views is what physical depth values are shown when interacting with the image,
+/// Note that the only effect on 2D views is the physical depth values shown when hovering the image.
 /// In 3D views on the other hand, this affects where the points of the point cloud are placed.
 struct DepthMeter (
   "attr.python.aliases": "float",