Docs build cleanup

[evankanderson]

Fixes lint issues detected in #6405, speeds up docs build

Proposed Changes

• Fix misspell detected typos in threat model.
• Exclude vendored, minified typescript from linting.
• Fix missing newline at EOF in 6 files.
• Switch from 'git clone' to 'git worktree add', which cuts about 50% of the docs build time on my laptop.

[netlify]

✅ Deploy Preview for knative ready!

Name	Link
🔨 Latest commit	d83f749
🔍 Latest deploy log	https://app.netlify.com/projects/knative/deploys/68d5b9cc5f801100086cf3ef
😎 Deploy Preview	https://deploy-preview-6407--knative.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[dprotaso]

Confused the build error seems unrelated to your PR

3:49:54 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
3:49:54 PM:     - from: /community/*
      status: 301
      to: /docs/community/
    - from: /docs/help/contributor/*
      status: 301
      to: https://github.com/knative/docs/blob/main/contribute-to-docs/README.md
  redirectsOrigin: config
3:49:54 PM: Build failed due to a user error: Build script returned non-zero exit code: 2

/retest

[evankanderson]

Confused the build error seems unrelated to your PR

3:49:54 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
3:49:54 PM:     - from: /community/*
      status: 301
      to: /docs/community/
    - from: /docs/help/contributor/*
      status: 301
      to: https://github.com/knative/docs/blob/main/contribute-to-docs/README.md
  redirectsOrigin: config
3:49:54 PM: Build failed due to a user error: Build script returned non-zero exit code: 2

/retest

This was due to the git clone at Netlify not having fetched any recent branch data; it was all very old (release-1.7 era). I added a git fetch --prune origin to the code during CI to keep this up to date.

I do need to figure out why the ./hack/build.sh --strict failed, we shouldn't ignore that one (which seems to be another git worktree complaint).

[evankanderson]

Okay, I think I fixed the worktree stuff. Netlify and "strict" checks should both now pass.

[dprotaso]

Okay, I think I fixed the worktree stuff. Netlify and "strict" checks should both now pass.

What was the issue?

[dprotaso]

/lgtm
/approve

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, evankanderson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dprotaso,evankanderson]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[evankanderson]

Okay, I think I fixed the worktree stuff. Netlify and "strict" checks should both now pass.

What was the issue?

For some reason, the GitHub action wanted a refspec of origin/$BRANCH, and the netlify issue was needing to run git fetch (but the $BRANCH refspec worked fine).