Skip to content

Conversation

@viral-sangani
Copy link
Collaborator

This PR fixes issue #2087 by renaming the 'Consensus' section to 'Security Council' to accurately reflect that Celo is now an L2 and no longer has a consensus mechanism.

Changes

  • Renamed home/protocol/consensus.mdx to home/protocol/security-council.mdx
  • Updated title and description to reflect Security Council instead of consensus mechanism
  • Updated navigation references in docs.json
  • Updated redirects to point to new security-council path

Related Issue

Fixes #2087

- Rename consensus.mdx to security-council.mdx
- Update title and description to reflect Security Council instead of consensus mechanism
- Update navigation references in docs.json
- Update redirects to point to new security-council path

Fixes #2087
@viral-sangani viral-sangani requested review from a team as code owners November 6, 2025 15:21
@viral-sangani viral-sangani requested review from ezdac and palango and removed request for a team November 6, 2025 15:21
@GigaHierz GigaHierz merged commit 931607b into main Nov 7, 2025
3 checks passed
@GigaHierz GigaHierz deleted the fix/rename-consensus-to-security-council branch November 7, 2025 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs confuse "Consensus" with "Security Council"

3 participants