docs: network upgrade

[jcstein]

Overview

Resolves #1676

Summary by CodeRabbit

• New Features

  • Updated terminology from "hardfork" to "network upgrade" across various documentation pages for improved clarity.
  • Enhanced descriptions of upgrade processes, including distinctions between breaking and non-breaking upgrades.

• Bug Fixes

  • Corrected references to ensure consistency in terminology throughout the documentation.

• Documentation

  • Improved clarity and accuracy of network upgrade documentation, including specific updates related to the Lemongrass upgrade.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces significant terminology updates across multiple documentation files, replacing "hardfork" with "network upgrade" to ensure consistency and clarity. This includes changes in sidebar configurations and references within various documents, aligning the language used to describe upgrade processes. The updates aim to enhance understanding of the upgrade mechanisms while maintaining the content's relevance and structure.

Changes

File	Change Summary
.vitepress/config.ts	Updated sidebar label from "Hardfork process" to "Network upgrade process."
nodes/arabica-devnet.md	Replaced "Hardfork Upgrades" with "network upgrades" and updated references to "Lemongrass hardfork."
nodes/hardfork-process.md	Changed title and terminology from "Celestia hardfork process" to "Celestia network upgrade process," clarifying upgrade types.
nodes/mainnet.md	Updated references from "Hardfork process page" to "network upgrade process page."
nodes/mocha-testnet.md	Replaced "Hardfork process page" with "network upgrade process page" and updated "Lemongrass hardfork."
nodes/participate.md	Changed "hardforks in coordination" to "breaking network upgrades in coordination" and updated references to "Lemongrass hardfork."

Assessment against linked issues

Objective	Addressed	Explanation
Use consistent terminology across docs (1676)	✅

Possibly related issues

• docs: link network upgrades section to hardfork/network upgrade section #1675: The changes in terminology align with the objective of linking network upgrades to the hardfork/network upgrade section.

Possibly related PRs

• docs: Lemongrass hardfork #1641: This PR also addresses terminology changes related to the Lemongrass hardfork, aligning with the updates made here.
• docs: arabica upgrade height #1666: This PR includes updates to the hardfork process documentation, which relates to the terminology changes in this PR.
• docs: link to hardfork page on Participate.md #1677: This PR enhances navigation related to the hardfork process, which is relevant to the changes made in this PR.

Suggested labels

documentation, enhancement

Poem

🐇 In the meadow where upgrades bloom,
The terms now dance, dispelling gloom.
From hardforks to network grace,
Clarity found in every space.
Hops of joy for changes bright,
In our docs, all feels just right! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai generate interesting stats about this repository and render them as a table.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

PR Preview Action v1.4.7
🚀 Deployed preview to https://celestiaorg.github.io/docs-preview/./pr-1711/
on branch main at 2024-09-16 13:45 UTC