chore: edits for professionalism of our comments (#18346)

Author: mmalerba

src/cdk/a11y/interactivity-checker/interactivity-checker.spec.ts

@@ -390,7 +390,7 @@ describe('InteractivityChecker', () => {
 
         appendElements([objectEl]);
 
-        // This is a hack to create an empty contentDocument for the frame element.
+        // This creates an empty contentDocument for the frame element.
         objectEl.type = 'text/html';
         objectEl.contentDocument!.body.appendChild(button);
 

src/material/datepicker/datepicker-content.scss

@@ -33,12 +33,12 @@ $mat-datepicker-touch-max-height: 788px;
 
 .mat-datepicker-content-touch {
   display: block;
-  // make sure the dialog scrolls rather than being cropped on ludicrously small screens
+  // Make sure the dialog scrolls rather than being cropped on ludicrously small screens
   max-height: 80vh;
   overflow: auto;
 
-  // TODO(mmalerba): hack to offset the padding of the dialog. Can be removed when we switch away
-  // from using dialog.
+  // Offsets the padding of the dialog.
+  // TODO(mmalerba): Remove when we switch away from using dialog.
   margin: -24px;
 
   .mat-calendar {

src/material/form-field/form-field-outline.scss

@@ -81,7 +81,7 @@ $mat-form-field-outline-subscript-padding:
   }
 
   .mat-form-field-outline-gap {
-    // hack for Chrome's treatment of borders with non-integer (scaled) widths
+    // Workaround for Chrome's treatment of borders with non-integer (scaled) widths
     // refer to https://github.com/angular/components/issues/10710
     border-radius: 0.000001px;
 

src/material/form-field/form-field.ts

@@ -251,8 +251,8 @@ export class MatFormField extends _MatFormFieldMixinBase
   @ContentChild(MatFormFieldControl) _controlNonStatic: MatFormFieldControl<any>;
   @ContentChild(MatFormFieldControl, {static: true}) _controlStatic: MatFormFieldControl<any>;
   get _control() {
-    // TODO(crisbeto): we need this hacky workaround in order to support both Ivy
-    // and ViewEngine. We should clean this up once Ivy is the default renderer.
+    // TODO(crisbeto): we need this workaround in order to support both Ivy and ViewEngine.
+    //  We should clean this up once Ivy is the default renderer.
     return this._explicitFormFieldControl || this._controlNonStatic || this._controlStatic;
   }
   set _control(value) {