RPP: Fix misspellings en masse

It's annoying to see the gerrit spelling suggestions sprinkled in each
CL, so now we can be done with it.

Thx to http://cl/723317254

Bug: none
Change-Id: I9246ddf46602bc2990b34b6a65ae8f5673150b8b
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6231217
Reviewed-by: Jack Franklin <[email protected]>
Commit-Queue: Jack Franklin <[email protected]>
Auto-Submit: Paul Irish <[email protected]>

Author: paulirish

front_end/models/cpu_profile/CPUProfileDataModel.ts

@@ -91,7 +91,7 @@ export class CPUProfileDataModel extends ProfileTreeModel {
     this.samples = profile.samples;
 
     // Lines are available only in profiles coming from tracing.
-    // Elements in the lines array have a 1 to 1 correspondance with
+    // Elements in the lines array have a 1 to 1 correspondence with
     // samples, by array position. They can be 1 or 0 and indicate if
     // there is line data for a given sample, i.e. if a given sample
     // needs to be included to calculate the line level execution time
@@ -334,7 +334,7 @@ export class CPUProfileDataModel extends ProfileTreeModel {
     // apart when they shouldn't.
     // Here's a workaround for that. When there's a single (program) sample
     // between two call stacks sharing the same bottom node, it is replaced
-    // with the preceeding sample.
+    // with the preceding sample.
     const samples = this.samples;
     if (!samples) {
       return;

front_end/models/trace/LanternComputationData.ts

@@ -354,7 +354,7 @@ function createNetworkRequests(
     }
 
     // Apply the `:redirect` requestId convention: only redirects[0].requestId is the actual
-    // requestId, all the rest have n occurences of `:redirect` as a suffix.
+    // requestId, all the rest have n occurrences of `:redirect` as a suffix.
     for (let i = 1; i < requestChain.length; i++) {
       requestChain[i].requestId = `${requestChain[i - 1].requestId}:redirect`;
     }

front_end/models/trace/extras/MainThreadActivity.test.ts

@@ -52,7 +52,7 @@ describe('MainThreadActivity', function() {
     // Therefore, the window focuses on the time period of 1 to 280ms (280 is
     // the end time of the event that starts at 230ms).
     // The right number looks odd because when we zoom the window we adjust it
-    // postively by 5% for the upper bound to give it some breathing room.
+    // positively by 5% for the upper bound to give it some breathing room.
     assert.strictEqual(win.min, milliToMicro(1));
     assert.strictEqual(win.max, milliToMicro(293.95));
   });

front_end/models/trace/extras/TraceTree.test.ts

@@ -343,7 +343,7 @@ describeWithEnvironment('TraceTree', () => {
       const mainThread = getMainThread(parsedTrace.Renderer);
       const bounds = Trace.Helpers.Timing.traceWindowMilliSeconds(parsedTrace.Meta.traceBounds);
 
-      // Replicate the filters as they would be when renderering in the actual panel.
+      // Replicate the filters as they would be when rendering in the actual panel.
       const textFilter = new Timeline.TimelineFilters.TimelineRegExp();
       const modelFilters = [
         Timeline.TimelineUIUtils.TimelineUIUtils.visibleEventsFilter(),

front_end/models/trace/handlers/LayoutShiftsHandler.test.ts

@@ -171,7 +171,7 @@ describe('LayoutShiftsHandler', function() {
           assert.strictEqual(cluster.scoreWindows.needsImprovement.min, event.ts);
         }
 
-        // Here we have transitioned from eiter Good or NI to Bad, so
+        // Here we have transitioned from either Good or NI to Bad, so
         // again we assert that the Bad window starts when expected,
         // and that either the NI or Good window finishes just prior.
         if (scoreBeforeEvent < Trace.Handlers.ModelHandlers.LayoutShifts.LayoutShiftsThreshold.BAD &&

front_end/models/trace/handlers/MetaHandler.ts

@@ -44,7 +44,7 @@ const traceBounds: Types.Timing.TraceWindowMicro = {
  * Note that these Maps will have the same values in them; these are just keyed
  * differently to make look-ups easier.
  *
- * We also additionally maintain an array of only navigations that occured on
+ * We also additionally maintain an array of only navigations that occurred on
  * the main frame. In many places in the UI we only care about highlighting
  * main frame navigations, so calculating this list here is better than
  * filtering either of the below maps over and over again at the UI layer.
@@ -236,7 +236,7 @@ export function handleEvent(event: Types.Events.Event): void {
           mainFrameURL = frame.url;
         }
       } else if (traceHasOutermostMainFrameFlag) {
-        // Less ideal: "guess" at the main thread by using this falg.
+        // Less ideal: "guess" at the main thread by using this flag.
         if (frame.isOutermostMainFrame) {
           mainFrameId = frame.frame;
           mainFrameURL = frame.url;
@@ -376,7 +376,7 @@ export async function finalize(): Promise<void> {
   // the previous page. This doesn't matter too much except we often use this
   // URL as the visual name of the trace shown to the user (e.g. in the history
   // dropdown). We can be more accurate by finding the first main frame
-  // navigaton, and using its URL, if we have it.
+  // navigation, and using its URL, if we have it.
   // However, to avoid doing this in a case where the first navigation is far
   // into the trace's lifecycle, we only do this in situations where the first
   // navigation happened very soon (0.5 seconds) after the trace started

front_end/models/trace/handlers/PageLoadMetricsHandler.test.ts

@@ -60,7 +60,7 @@ describeWithEnvironment('PageLoadMetricsHandler', function() {
       if (!pageLoadEventsForMainFrame) {
         assert.fail('Page load events for main frame were unexpectedly null.');
       }
-      // Single FCP event that occured after the refresh.
+      // Single FCP event that occurred after the refresh.
       assert.strictEqual(pageLoadEventsForMainFrame.size, 1);
       const scoresByMetricName = [...pageLoadEventsForMainFrame.values()];
       const fcpCount =
@@ -88,7 +88,7 @@ describeWithEnvironment('PageLoadMetricsHandler', function() {
       if (!pageLoadEventsForMainFrame) {
         assert.fail('Page load events for main frame were unexpectedly null.');
       }
-      // Single FCP event that occured after the refresh.
+      // Single FCP event that occurred after the refresh.
       assert.strictEqual(pageLoadEventsForMainFrame.size, 1);
       const events = pageLoadEventsForMainFrame.get(navigationId);
       const allFoundMetricScoresForMainFrame = events ? Array.from(events.values()) : [];

front_end/models/trace/handlers/PageLoadMetricsHandler.ts

@@ -442,7 +442,7 @@ export interface MetricScore {
   metricName: MetricName;
   classification: ScoreClassification;
   event?: Types.Events.PageLoadEvent;
-  // The last navigation that occured before this metric score.
+  // The last navigation that occurred before this metric score.
   navigation?: Types.Events.NavigationStart;
   estimated?: boolean;
   timing: Types.Timing.Micro;

front_end/models/trace/handlers/RendererHandler.ts

@@ -248,7 +248,7 @@ export function assignThreadName(
 /**
  * Removes unneeded trace data opportunistically stored while handling events.
  * This currently does the following:
- *  - Deletes processes with an unkonwn origin.
+ *  - Deletes processes with an unknown origin.
  */
 export function sanitizeProcesses(processes: Map<Types.Events.ProcessID, RendererProcess>): void {
   const auctionWorklets = auctionWorkletsData().worklets;

front_end/models/trace/handlers/ScreenshotsHandler.ts

@@ -53,7 +53,7 @@ export async function finalize(): Promise<void> {
       ph,
       pid,
       tid,
-      // TODO(paulirish, crbug.com/41363012): investigate why getPresentationTimestamp(snapshotEvent) seems less accurate. Resolve screenshot timing innaccuracy.
+      // TODO(paulirish, crbug.com/41363012): investigate why getPresentationTimestamp(snapshotEvent) seems less accurate. Resolve screenshot timing inaccuracy.
       // `getPresentationTimestamp(snapshotEvent) - snapshotEvent.ts` is how many microsec the screenshot should be adjusted to the right/later
       ts: snapshotEvent.ts,
       args: {