Run codespell on src/tools/telemetry.

tools/telemetry/telemetry/web_perf/metrics/webrtc_rendering_stats.py

Index: tools/telemetry/telemetry/web_perf/metrics/webrtc_rendering_stats.py
diff --git a/tools/telemetry/telemetry/web_perf/metrics/webrtc_rendering_stats.py b/tools/telemetry/telemetry/web_perf/metrics/webrtc_rendering_stats.py
index 55c72d0f46caa39d88a5433ad9508c820100731d..43276b6f5db293612b3eed785f7dcc3c4e95eadf 100644
--- a/tools/telemetry/telemetry/web_perf/metrics/webrtc_rendering_stats.py
+++ b/tools/telemetry/telemetry/web_perf/metrics/webrtc_rendering_stats.py
@@ -98,16 +98,16 @@ class WebMediaPlayerMsRenderingStats(object):
     In this paragraph I will be using regex notation. What is intended by the
     word cadence is a sort of extended instantaneous 'Cadence' (thus not
     necessarily periodic). Just as an example, a normal 'Cadence' could be
-    something like [2 3] which means possibly an observed frame persistance
+    something like [2 3] which means possibly an observed frame persistence
     progression of [{2 3}+] for an ideal 20FPS video source. So what we are
-    calculating here is the list of frame persistance, kind of a
+    calculating here is the list of frame persistence, kind of a
     'Proto-Cadence', but cadence is shorter so we abuse the word.
 
     Args:
       relevant_events: list of Telemetry events.
 
     Returns:
-      a list of frame persistance values.
+      a list of frame persistence values.
     """
     cadence = []
     frame_persistence = 0
@@ -136,7 +136,7 @@ class WebMediaPlayerMsRenderingStats(object):
     and p=Card(k in C).
 
     Args:
-      cadence: list of frame persistance values.
+      cadence: list of frame persistence values.
 
     Returns:
       a dictionary containing the distribution