rmoff commented on PR #825: URL: https://github.com/apache/flink-web/pull/825#issuecomment-3883614453
@davidradl I've left some more comments. You're right that AI sucks for writing copy—but it's _excellent_ for reviewing it :) FWIW [this is the prompt that I use](https://github.com/rmoff/rmoff-blog/blob/main/.claude/skills/proofread-blog/SKILL.md). It identified the following on your current draft which would be worth at least checking through before shipping: ## Typos and Grammar 1. **"a inflight shard rotation"** — should be "**an** in-flight shard rotation". Wrong article ("a" before a vowel sound), and "in-flight" is conventionally hyphenated. 2. **"JAVA"** — should be "**Java**". Java is not an acronym. 3. **"as usual this update will summarise"** — this is the first community update in six years. "As usual" is factually wrong. Remove it or rewrite, e.g. "This update summarises what happened in January." 4. **"Flink HTTP connector, addressed all outstanding raised PRs."** — comma splice. The comma separates the subject from its verb. Should be: "The Flink HTTP connector addressed all outstanding PRs." ("raised" is also redundant alongside "outstanding".) 5. **"commits, improvements to the blue-green deployment stood out."** — this is a sentence fragment. It reads like rough notes. Something like: "There were N commits; improvements to blue-green deployment stood out." 6. **"long awaited"** — should be hyphenated: "long-awaited" (compound adjective before a noun). 7. **"connector specific repository"** + **"their own"** — two issues: "connector-specific" needs a hyphen, and "the rest of the connector code is in **their** own" should be "**its** own" (singular antecedent). 8. **"Preparing for releasing it."** — awkward phrasing. Simply: "Preparing for release." 9. **"Enterprise ready."** — should be hyphenated: "Enterprise-ready" (compound adjective). 10. **"slack"** — should be capitalised: "Slack" (proper noun). 11. **"Previous Blog :"** — spurious space before the colon. 12. **"a monthly blog, that will highlight"** — unnecessary comma. The clause is restrictive, so no comma: "a monthly blog that will highlight". ## Formatting Issues 13. **Bare `<p>` HTML tags** appear in the markdown. These are unnecessary and render as empty paragraph breaks. Use a blank line instead. 14. **Double space in heading**: `# Flink Community update` has two spaces after `#`. 15. **Title inconsistency**: the YAML frontmatter says `Flink Community Update - February'26` (capitalised "Update", abbreviated year) but the H1 heading says `Flink Community update for February 2026` (lowercase "update", full year). Pick one and be consistent. 16. **Inconsistent FLIP link formatting**: FLIP-339, FLIP-487, FLIP-558 have a colon `:` after the link, but FLIP-560, FLIP-557, FLIP-563 do not. Should be consistent. ## Content / Logic Issues 17. **"k8s experience."** (under "Bringing us up to date") — this bullet point is too vague to be useful. What improved about the Kubernetes experience? 18. **"SUM" acronym** — the FLIP-558 description uses "SUM" as an acronym for "Sink Upsert Materializer". This is confusing because SUM universally means summation. Either introduce it more carefully or just spell it out without abbreviating. 19. **"Deprecation of older APIs, leaving the strategic ones."** — "the strategic ones" is vague. Which APIs? 20. **The post is trying to do too much**: it bridges a 6-year gap *and* does a monthly recap. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
