--- a/toolkit/components/telemetry/docs/data/main-ping.rst
+++ b/toolkit/components/telemetry/docs/data/main-ping.rst
@@ -422,21 +422,19 @@ Telemetry Experiments uses it to note wh
 
 webrtc
 ------
 Contains special statistics gathered by WebRTC related components.
 
 So far only a bitmask for the ICE candidate type present in a successful or
 failed WebRTC connection is getting reported through C++ code as
 IceCandidatesStats, because the required bitmask is too big to be represented
-in a regular enum histogram. Further this data differentiates between Loop
-(aka Firefox Hello) connections and everything else, which is categorized as
-WebRTC.
+in a regular enum histogram.
 
-Note: in most cases the webrtc and loop dictionaries inside of
+Note: in most cases the webrtc dictionary inside of
 IceCandidatesStats will simply be empty as the user has not used any WebRTC
 PeerConnection at all during the ping report time.
 
 Structure:
 
 .. code-block:: js
 
     "webrtc": {
@@ -444,25 +442,16 @@ Structure:
         "webrtc": {
           "34526345": {
             "successCount": 5
           },
           "2354353": {
             "failureCount": 1
           }
         },
-        "loop": {
-          "2349346359": {
-            "successCount": 3
-          },
-          "73424": {
-            "successCount": 1,
-            "failureCount": 5
-          }
-        }
       }
     },
 
 gc
 --
 Contains statistics about selected garbage collections. To avoid
 bloating the ping, only a few GCs are included. There are two
 selection strategies. We always save the two GCs with the worst