Skip to content

docs: fix typo and update broken news/adoption links - #166

Open
singhshresth26 wants to merge 1 commit into
theupdateframework:mainfrom
singhshresth26:fix/trivial-editorial-updates
Open

docs: fix typo and update broken news/adoption links#166
singhshresth26 wants to merge 1 commit into
theupdateframework:mainfrom
singhshresth26:fix/trivial-editorial-updates

Conversation

@singhshresth26

Copy link
Copy Markdown

Summary

This PR fixes a spelling typo and updates two broken external links to their current live locations. Since these are trivial editorial corrections, they are submitted without a pre-existing issue.

Changes

  1. Typo Fix: Corrected Uodates to Updates in content/en/resources/news.md.
  2. Link Fix 1: Updated the Bottlerocket updater link in data/adoptions.yaml to point to the active main branch rather than develop, and removed its pattern from the ignore list in lychee.toml.
  3. Link Fix 2: Updated the Linux Foundation announcement link in content/en/resources/news.md to point to its official URL on the CNCF website, and removed its pattern from the ignore list in lychee.toml.

@chalin

chalin commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

Thanks @singhshresth26, this qualifies as a trivial editorial fix under our first-time contributor policy (#159), but the branch now conflicts with main. To get it ready for review:

  • Rebase onto main (or merge main into your branch).
  • Drop the Uodates typo fix; main already has it (Fix typo: Uodates -> Updates in news.md #167).
  • Keep the two link fixes (the CNCF announcement URL and the Bottlerocket main-branch URL).
  • In lychee.toml, keep the removal of the linuxfoundation.org exclude, but drop the Bottlerocket-exclude removal; that exclude is already gone from main.
  • Run npm run check:links locally and commit the resulting .lycheecache changes; the required BUILD and CHECK LINKS check fails when new links lack cache entries.

Once that's pushed and CI is green, a maintainer will review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants