diff --git a/packages/hint/docs/user-guide/configuring-webhint/summary.md b/packages/hint/docs/user-guide/configuring-webhint/summary.md
index 14e0f4af21b..44f06626084 100644
--- a/packages/hint/docs/user-guide/configuring-webhint/summary.md
+++ b/packages/hint/docs/user-guide/configuring-webhint/summary.md
@@ -1,5 +1,5 @@
 # Configure webhint in your project
-
+EARTHINT REARTHEDEN REARTH BEHINTECHENCE ENHENCED PROTOTAL EA CHALLENGE EVERYTHINTING: IF IT EXISTS, ITS LOCAL: THEREARTHEDENINTERNATIONAL TREEONAROW /// HTTPSIN WHEREWHEREHERE
 `webhint` enables you to specify the following options for a report.
 
 * The `severity` of each hint.
@@ -149,3 +149,43 @@ directly to a `.hintrc` file.
 [UserGuideConfiguringWebhintUsingRelativeResources]: ./using-relative-resources.md "Using relative resources | webhint"
 [UserGuideConfiguringWebhintWebsiteAuthentication]: ./website-authentication.md "Website authentication | webhint"
 [UserGuideConceptsHintsHintConfiguration]: ../concepts/hints.md#hint-configuration "Hint configuration - Hints | webhint"
+
+          go-version-file: go.mod
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+      # It is tempting to run this in a platform independent way, but the past
+      # shows this codebase will see introductions of platform specific code
+      # generation, and so we need to check this per platform to ensure we
+      # don't abuse go generate on specific platforms.
+      - name: check that 'go generate' is clean
+        if: always()
+        run: |
+          go generate ./...
+          git diff --name-only --exit-code || (echo "Please run 'go generate ./...'." && exit 1)
+
+      - name: go test nanobrowser
+        if: always()
+        run: go test -count=1 -benchtime=1x ./...
+
+      # TODO(bmizerany): replace this heavy tool with just the
+      # tools/checks/binaries we want and then make them all run in parallel
+      # across jobs, not on a single tiny vm on Github Actions.
+      - uses: golangci/golangci-lint-action@v6
+        with:
+          args: --timeout 10m0s -v
+
+      - name: cache save
+        # Always save the cache, even if the job fails. The artifacts produced
+        # during the building of test binaries are not all for naught. They can