Thanks. That definitely seems like an improvement. A few comments:
Your camera came with one of these Canon firmware versions and cannot be changed to another
This is technically not always true, Canon does sometimes issue public updates. So maybe just remove the "cannot be changed" part.
There's also a few cases where a Canon update was available before the port was made, and we only support the updated versions. The "Firmware version missing" section could include something like "check if there is a canon update to a supported version"
(there is a very old, outdated list of official updates on the wiki, but most of the links are broken https://chdk.fandom.com/wiki/Official_Canon_firmware_updates)
I think the "update an existing install" link for the small files is probably confusing. It suggests it's an easier or better option for updates, when it really isn't. The only real advantage is a 400kb download instead of 800kb, and you'd miss updates to official scripts. I'd vote for leaving it out entirely.
It's a bit odd that the stable builds come from your github, while the trunk builds come from the autobuild. I'm not saying this is a problem and I don't mind direct links to the autobuild, but note old files are removed when the build is updated. It looks like the page pulls build_info.json dynamically so assuming it uses the link from that it should be fine. Like the autobuild page itself, there's a tiny chance an autobuild will happen while someone is looking at the page, but it should be rare.
The tooltip on the github download count is strange: "Downloads of this file, counted by GitHub. Staff only." 🤨
If it doesn't count actual downloads, I'd just leave the whole thing out.
