Revise introduction for clarity on reports and changelogs

Reworded the introduction to clarify the purpose of the monthly report and the limitations of changelogs.

Author: castrojo

blog/2026-02-01-automated-reports-changelogs.md

@@ -9,7 +9,7 @@ tags: [announcements]
 
 Hi everyone,
 
-It can be difficult to keep track of things if you're not paying attention. I've been working on ways to collate all of the things happening from across the community into a regular monthly report. Here's [Jurassic January](https://docs.projectbluefin.io/reports/2026/01).
+It can be difficult to keep track of things if you're not paying attention regularly, and even if you are there's always stuff all over the place. I've been working on ways to collate all of the things happening from across the community into a regular monthly report. Here's [Jurassic January](https://docs.projectbluefin.io/reports/2026/01).
 
 Changelogs are actually pretty weird in bootc land. We usually extract the package version info from the last rechunking step to generate the changelogs - however that doesn't really cover the entire project, just the things in that repository. There's also a new upstream rechunker coming down the pipeline so that means that we'll need to rework how we generate the changelogs (thanks to [@renner0e](https://github.com/renner0e) for investigating this!). The existing changelogs also really only tell you about the things in the image, and not the "whole" of Bluefin. These will always continue to be published on [changelogs.projectbluefin.io](https://changelogs.projectbluefin.io)