Skip to content

docs(operate): one Discord support sentence, and past tense for op-geth #2312

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
palango merged 2 commits into from
Sep 7, 2026
Merged

docs(operate): one Discord support sentence, and past tense for op-geth #2312

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3b33e70
docs(operate): one Discord support sentence, and past tense for op-geth
palango Sep 3, 2026
53afff0
Merge branch 'main' into palango/2309-align-discord-support-sentence
GigaHierz Sep 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions operate/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,10 @@ sidebarTitle: "Start here"
description: Run and maintain a Celo L2 node, read the protocol specification, and track the upgrades that affect operators
---

This section is for node operators, RPC providers, and readers of the Celo L2 protocol specification. The fastest path to a synced node is [Run a node with Docker](/operate/operators/run-node). Ask in [#celo-L2-support](https://discord.com/channels/600834479145353243/1286649605798367252) on [Discord](https://chat.celo.org) if you get stuck.
This section is for node operators, RPC providers, and readers of the Celo L2 protocol specification. The fastest path to a synced node is [Run a node with Docker](/operate/operators/run-node). Ask in [#celo-L2-support](https://discord.com/channels/600834479145353243/1286649605798367252) on [Discord](https://chat.celo.org) if you have any questions.

<Warning>
Celo is replacing `op-geth` with `op-reth` as its execution client. See [End of Support for op-geth](/operate/notices/op-geth-deprecation) for each network's switch date.
Celo has replaced `op-geth` with `op-reth` as its execution client. See [End of Support for op-geth](/operate/notices/op-geth-deprecation) for each network's switch date.
</Warning>

## Run a node
Expand Down
4 changes: 2 additions & 2 deletions operate/notices/archive/celo-sepolia-launch.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,6 @@ Thank you to the first wave of our ecosystem partners supporting Celo Sepolia al
- **Talent Protocol** – Web3 Professional Network
- **Prosperity Pass** – Celo PG Onchain Access Pass

## Getting Help
## Getting help

@karlb karlb Sep 4, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are usually using title case for headings in the Celo docs. Why not here?

@palango palango Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?


Please reach out to our team on [Discord](https://chat.celo.org) in the [#celo-L2-support](https://discord.com/channels/600834479145353243/1286649605798367252) channel if you have any questions.
Ask in [#celo-L2-support](https://discord.com/channels/600834479145353243/1286649605798367252) on [Discord](https://chat.celo.org) if you have any questions.
4 changes: 2 additions & 2 deletions operate/notices/archive/l1-fusaka-upgrade.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,6 @@ There are no upgrades required for the Celo L2 client for the L1 Fusaka upgrade.
- `op-node` at [v2.1.0](https://github.com/celo-org/optimism/releases/tag/celo-v2.1.0)
- `eigenda-proxy` at [v1.8.2](https://github.com/layr-labs/eigenda/pkgs/container/eigenda-proxy/437919973?tag=v1.8.2)

## Getting Help
## Getting help

Please reach out to our team on [Discord](https://chat.celo.org) in the [#celo-L2-support](https://discord.com/channels/600834479145353243/1286649605798367252) channel if you have any questions.
Ask in [#celo-L2-support](https://discord.com/channels/600834479145353243/1286649605798367252) on [Discord](https://chat.celo.org) if you have any questions.
8 changes: 4 additions & 4 deletions operate/operators/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,12 +25,12 @@ See [Architecture](/operate/operators/architecture) for how these fit together.
## Execution client

- **op-reth** — Celo's primary execution client, built on `reth`. The guides in this section use `op-reth`.
- **op-geth** — the previous execution client. It is deprecated in favor of `op-reth` and remains supported only until your network's switch date.
- **op-geth** — the previous execution client. Support ended on each network's switch date; a node still running it can follow the wrong chain.

<Warning>
**op-geth is being deprecated**
**op-geth is no longer supported**

Celo is switching its execution client from `op-geth` to `op-reth`. All node operators must migrate to `op-reth` by their network's switch date. See [End of Support for op-geth](/operate/notices/op-geth-deprecation) for the switch dates and details, and follow the [celo-l2-node-docker-compose](https://github.com/celo-org/celo-l2-node-docker-compose) repository for release updates.
Celo has replaced `op-geth` with `op-reth` as its execution client. A node still running `op-geth` can follow the wrong chain. See [End of Support for op-geth](/operate/notices/op-geth-deprecation) for the switch dates and details, and follow the [celo-l2-node-docker-compose](https://github.com/celo-org/celo-l2-node-docker-compose) repository for release updates.
</Warning>

## Guides
Expand All @@ -47,4 +47,4 @@ Celo is switching its execution client from `op-geth` to `op-reth`. All node ope

## Getting help

Please reach out to our team on [Discord](https://chat.celo.org) in the [#celo-L2-support](https://discord.com/channels/600834479145353243/1286649605798367252) channel if you have any questions.
Ask in [#celo-L2-support](https://discord.com/channels/600834479145353243/1286649605798367252) on [Discord](https://chat.celo.org) if you have any questions.
4 changes: 2 additions & 2 deletions operate/operators/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,6 @@ If your node stalls or falls behind the sequencer, it usually has too few peers.

See the [Configuration reference](/operate/operators/configuration#networking-p2p) for these variables. Because op-node now syncs via the execution layer, healthy execution-client peer connectivity is required — see [Deprecation of Req/Res CL P2P Sync](/operate/notices/req-resp-cl-sync-deprecation).

## Getting Help
## Getting help

Please reach out to our team on [Discord](https://chat.celo.org) in the [#celo-L2-support](https://discord.com/channels/600834479145353243/1286649605798367252) channel if you have any questions.
Ask in [#celo-L2-support](https://discord.com/channels/600834479145353243/1286649605798367252) on [Discord](https://chat.celo.org) if you have any questions.