chore: remove 'matches upstream' comments — describe behavior directly

Author: johanrd

lib/rules/template-require-form-method.js

@@ -27,8 +27,8 @@ function parseConfig(config) {
   }
 
   // Invalid configuration (e.g. unknown method in allowedMethods). Throw a
-  // descriptive error to surface the problem to the user, matching upstream
-  // ember-template-lint (which throws instead of silently disabling).
+  // descriptive error to surface the problem to the user rather than silently
+  // disabling the rule.
   throw new Error(
     'template-require-form-method: invalid configuration. Expected one of:\n' +
       '  * boolean - `true` to enable / `false` to disable\n' +
@@ -91,10 +91,9 @@ module.exports = {
   },
 
   create(context) {
-    // Match upstream ember-template-lint: when no options are provided,
-    // parseConfig(undefined) returns false and the rule is disabled. This
-    // rule must be enabled explicitly via `true` or an `allowedMethods`
-    // object.
+    // When no options are provided, parseConfig(undefined) returns false and
+    // the rule is disabled. It must be enabled explicitly via `true` or an
+    // `allowedMethods` object.
     const rawOption = context.options[0];
     const config = parseConfig(rawOption);