docs(operate): one Discord support sentence, and past tense for op-geth - #2312
Conversation
Four Operate pages carried a longer wording of the same #celo-L2-support pointer than the landing page added in #2308. Settle on one sentence for all five and fix the heading case on the three that said "Getting Help". Both op-geth switch dates have passed, so the landing page and the node operator overview now say the switch happened instead of announcing it. Closes #2309
| - **Prosperity Pass** – Celo PG Onchain Access Pass | ||
|
|
||
| ## Getting Help | ||
| ## Getting help |
There was a problem hiding this comment.
We are usually using title case for headings in the Celo docs. Why not here?
There was a problem hiding this comment.
AGENTS.md:70-72:
Sentence case for new and rewritten headings:
## How it works, not## How It Works. Do not mass-retitle old pages just for case; fix headings on pages you are already editing.
It came in with AGENTS.md in #2269 (a9b0a19c, 24 Aug, @GigaHierz) and hasn't been touched since. No other style page mentions capitalisation.
You're right that title case is still the majority: ~420 title-case H2s against ~372 sentence-case across the repo. If you'd rather flip the standard, that's one bullet in AGENTS.md and its own PR. @GigaHierz, any view since you wrote the rule?
karlb
left a comment
karlb
left a comment
There was a problem hiding this comment.
Looks good. Independently from this PR, let's decide on the headline casing rules. Either is fine, it should just be consistent.
3 participants
Four Operate pages pointed readers at
#celo-L2-supportin a longer sentence than the landing page added in #2308 used for the same thing, so the tab read two ways. All five now carry one sentence. The landing page is in the diff because leaving it on its own wording would move the inconsistency rather than remove it, and AGENTS.md says a page that conflicts with the standard is the page that gets fixed. While in these files I also put the op-geth switch in the past tense, since both switch dates have passed.The support sentence
"Ask in #celo-L2-support on Discord if you have any questions", on
operate/index.mdx,operate/operators/overview.mdx,operate/operators/troubleshooting.mdx,operate/notices/archive/l1-fusaka-upgrade.mdxandoperate/notices/archive/celo-sepolia-launch.mdx.The two archived notices are in scope. They are still published pages a reader can land on, and the edit is one line each with no link changes.
Three of the pages also said
## Getting Help. AGENTS.md asks for sentence case on pages you are already editing, so they now say## Getting help. The slug stays#getting-help, so no anchors break.The op-geth tense
/operate/notices/op-geth-deprecationgives the switch dates as June 24, 2026 for Celo Sepolia and July 22, 2026 for mainnet. Both are past, so "Celo is replacing op-geth" and "op-geth is being deprecated" were announcing something that already happened. The landing page and the operators overview now say it happened, and the overview's Warning says what an operator still runningop-gethrisks, which the notice already states at line 19.The deprecation notice itself is future tense start to finish, as are
run-node.mdx:12andarchive-node.mdx:16. That needs a rewrite rather than a verb swap, so it is issue #2311 rather than more of this diff.Verification
Closes #2309