Cleanup

NullVoxPopuli · NullVoxPopuli · commit 8409d4d4a21a · 2026-02-19T19:07:44.000-05:00
diff --git a/README.md b/README.md
diff --git a/docs/rules/template-builtin-component-arguments.md b/docs/rules/template-builtin-component-arguments.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 The builtin `Input` component has several arguments that match attributes
 of the lower-case `input` HTML element. These arguments should be set via e.g.
 `@type`, instead of `type`, but it is easy to forget and can cause subtle
diff --git a/docs/rules/template-deprecated-inline-view-helper.md b/docs/rules/template-deprecated-inline-view-helper.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 In Ember 1.12, support for invoking the inline View helper was deprecated.
 
 ## Examples
diff --git a/docs/rules/template-no-args-paths.md b/docs/rules/template-no-args-paths.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 Arguments that are passed to components are prefixed with the `@` symbol in Angle bracket syntax.
 Ember Octane leverages this in the component's templates by allowing users to directly refer to an argument using the same prefix:
 
diff --git a/docs/rules/template-no-aria-hidden-body.md b/docs/rules/template-no-aria-hidden-body.md
@@ -4,10 +4,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
-🔧 The `--fix` option on the command line can automatically fix some of the problems reported by this rule.
-
 The aria-hidden attribute should never be present on the `<body>` element, as it hides the entire document from assistive technology.
 
 ## Examples
diff --git a/docs/rules/template-no-attrs-in-components.md b/docs/rules/template-no-attrs-in-components.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 This rule prevents the usage of `attrs` property to access values passed to the component since all the values can be accessed directly from the template.
 
 ## Examples
diff --git a/docs/rules/template-no-duplicate-id.md b/docs/rules/template-no-duplicate-id.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 Valid HTML requires that `id` attribute values are unique.
 
 This rule does a basic check to ensure that `id` attribute values are not the same.
diff --git a/docs/rules/template-no-empty-headings.md b/docs/rules/template-no-empty-headings.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 Headings relay the structure of a webpage and provide a meaningful, hierarchical order of its content. If headings are empty or its text contents are inaccessible, this could confuse users or prevent them accessing sections of interest.
 
 Disallow headings (h1, h2, etc.) with no accessible text content.
diff --git a/docs/rules/template-no-forbidden-elements.md b/docs/rules/template-no-forbidden-elements.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 This rule disallows the use of forbidden elements in template files.
 
 The rule is configurable so teams can add their own disallowed elements.
diff --git a/docs/rules/template-no-heading-inside-button.md b/docs/rules/template-no-heading-inside-button.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 Assistive technology allows users to browse a page by heading elements (`<h1>` - `<h6>`). However, if those heading elements are nested inside of button elements, they will automatically be marked as presentational by browsers. Any HTML element where ["children presentational" is true](https://w3c.github.io/aria/#button) should be coerced by the browser to be presentational, and therefore not included in the accessibility tree.
 
 As such, nesting a heading element inside of a button element will cause failures for WCAG requirement 1.3.1, Info and Relationships, because the heading has lost semantic meaning.
diff --git a/docs/rules/template-no-inline-styles.md b/docs/rules/template-no-inline-styles.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 Inline styles are not the best practice because they are hard to maintain and usually make the overall size of the project bigger. This rule forbids inline styles. Use CSS classes instead.
 
 ## Examples
diff --git a/docs/rules/template-no-input-block.md b/docs/rules/template-no-input-block.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 Use of the block form of the handlebars `input` helper will result in an error at runtime.
 
 ## Examples
diff --git a/docs/rules/template-no-input-tagname.md b/docs/rules/template-no-input-tagname.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 `{{input tagName=x}}` will result in obtuse errors. Typically, the input will simply fail to render, whether used in block form or inline. The only valid `tagName` for the input helper is `input`. For `textarea`, `button`, and other input-like elements, you should instead create a new component or better use the DOM!
 
 ## Examples
diff --git a/docs/rules/template-no-obsolete-elements.md b/docs/rules/template-no-obsolete-elements.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 Some elements are entirely obsolete and must not be used by authors.
 
 This rule forbids the use of obsolete elements.
diff --git a/docs/rules/template-no-quoteless-attributes.md b/docs/rules/template-no-quoteless-attributes.md
@@ -4,10 +4,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
-🔧 The `--fix` option on the command line can automatically fix some of the problems reported by this rule.
-
 In HTML, all attribute values are considered strings, regardless of whether they are quoted or not.
 
 The following two examples are _identical_ from the perspective of the browser:
diff --git a/docs/rules/template-no-this-in-template-only-components.md b/docs/rules/template-no-this-in-template-only-components.md
@@ -4,8 +4,6 @@
 
 <!-- end auto-generated rule header -->
 
-🔧 The `--fix` option on the command line can automatically fix some of the problems reported by this rule.
-
 There is no `this` context in template-only components.
 
 ## Examples
diff --git a/docs/rules/template-no-unbound.md b/docs/rules/template-no-unbound.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 `{{unbound}}` is a legacy hold over from the days in which Ember's template engine was less performant. Its use today
 is vestigial, and it no longer offers performance benefits.
 
diff --git a/docs/rules/template-no-unnecessary-concat.md b/docs/rules/template-no-unnecessary-concat.md
@@ -6,8 +6,6 @@
 
 💅 The `extends: 'stylistic'` property in a configuration file enables this rule.
 
-🔧 The `--fix` option on the command line can automatically fix some of the problems reported by this rule.
-
 This rule forbids unnecessary use of quotes (`""`) around expressions like `{{myValue}}`.
 
 ## Examples
diff --git a/docs/rules/template-no-unnecessary-curly-strings.md b/docs/rules/template-no-unnecessary-curly-strings.md
@@ -4,10 +4,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
-🔧 The `--fix` option on the command line can automatically fix some of the problems reported by this rule.
-
 Strings need not be wrapped in the curly braces (mustache expressions).
 
 ## Examples
diff --git a/docs/rules/template-no-valueless-arguments.md b/docs/rules/template-no-valueless-arguments.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 Similar to HTML attributes, component arguments will default to an empty string when they are not explicitly assigned a value. This behavior isn't documented anywhere so depending on it isn't recommended and usually the result of a user-error. Since it _is_ valid syntax, accidental use of this behavior can be hard to detect and cause confusing bugs.
 
 ## Examples
diff --git a/docs/rules/template-no-with.md b/docs/rules/template-no-with.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 The use of `{{with}}` has been deprecated, you should replace it with either `{{let}}` or a combination of `{{let}}`, `{{if}}` and `{{else}}`.
 
 ## Examples
diff --git a/docs/rules/template-require-iframe-title.md b/docs/rules/template-require-iframe-title.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 ## `<iframe>`
 
 `<iframe>` elements must have a unique title property to indicate its content to the user.
diff --git a/docs/rules/template-require-valid-alt-text.md b/docs/rules/template-require-valid-alt-text.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 Enforce that all elements that require alternative text have meaningful information to relay back to the end user. This is a critical component of accessibility for screenreader users in order for them to understand the content's purpose on the page. By default, this rule checks for alternative text on the following elements: `<img>`, `<area>`, `<input type="image">`, and `<object>`.
 
 Enforce `img` alt attribute does not contain the word image, picture, or photo. Screen readers already announce `img` elements as an image. There is no need to use words such as _image_, _photo_, and/or _picture_. The rule will first check if `aria-hidden` is true to determine whether to enforce the rule. If the image is hidden, then rule will always succeed.
diff --git a/docs/rules/template-splat-attributes-only.md b/docs/rules/template-splat-attributes-only.md
@@ -2,8 +2,6 @@
 
 <!-- end auto-generated rule header -->
 
-✅ The `extends: 'recommended'` property in a configuration file enables this rule.
-
 It is easy to introduce typos when typing out `...attributes` or to use e.g.
 `...arguments` instead. Unfortunately, that leads to a cryptic runtime error,
 but does not fail the build.
