Rename mumP2P to mump2p throughout documentation

[swarna1101]

Summary by CodeRabbit

Documentation

• Standardized protocol naming from "mumP2P" to "mump2p" throughout documentation, navigation, and guides for consistent branding.
• Enhanced getting started guides with Docker setup, parameter configurations, and experimental documentation.
• Clarified protocol terminology and improved examples across learning materials and technical references.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ready	Preview	Comment	Oct 22, 2025 1:32pm

[coderabbitai]

Walkthrough

This pull request updates documentation and configuration files to rebrand the protocol name from "mumP2P" to "mump2p" (lowercase 'p'). Changes include configuration sidebar labels, guide headings, and documentation text across multiple files. No functional code or logic modifications are present.

Changes

Cohort / File(s)	Summary
Configuration & sidebar labels .vitepress/config.mts	Sidebar navigation text updated from "mumP2P Protocol" to "mump2p Protocol" in two locations (Overview and Research sections).
Getting started guides docs/guides/02-getting-started-docker.md, docs/guides/03-parameters.md, docs/guides/04-experiments.md, docs/guides/05-faq-glossary.md, docs/guides/overview.md	Protocol name rebranded from "mumP2P" to "mump2p" in headings, descriptions, labels, and code examples. NODE_MODE listings adjusted to include gossipsub mode; minor content additions to RLNC mode details.
Learning documentation docs/learn/overview/intro.md, docs/learn/overview/p2p.md	Comprehensive renaming of "mumP2P" to "mump2p" across all sections including introductions, node architecture, mesh topology, control messages, and security model. Added verification-oriented descriptions for pollution attack avoidance.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

This diff consists of homogeneous, repetitive changes—a consistent branding rename across documentation files with no logic, structural, or behavioral modifications. The pattern is uniform and easily verifiable.

Poem

🐰 The protocol gets a makeover clean,
From mumP2P to mump2p keen,
Across the docs it hops about,
A naming dance, no doubt!
Consistency shines, oh what a sight,
CodeRabbit approves with all its might! 🌟

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "Rename mumP2P to mump2p throughout documentation" directly and accurately describes the primary change evident across all modified files in the changeset. The raw summary confirms that all changes across multiple documentation files and configuration are focused on this single, consistent renaming effort from "mumP2P" to "mump2p". The title is concise, specific, and clearly communicates the main objective of the pull request without vague language or unnecessary details. A teammate scanning the repository history would immediately understand the purpose and scope of this change.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch rename-mump2p-to-lowercase

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b4f57fb and a0283a2.

📒 Files selected for processing (8)

• .vitepress/config.mts (2 hunks)
• docs/guides/02-getting-started-docker.md (6 hunks)
• docs/guides/03-parameters.md (4 hunks)
• docs/guides/04-experiments.md (6 hunks)
• docs/guides/05-faq-glossary.md (1 hunks)
• docs/guides/overview.md (3 hunks)
• docs/learn/overview/intro.md (2 hunks)
• docs/learn/overview/p2p.md (7 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/guides/04-experiments.md

[style] ~99-~99: ‘under stress’ might be wordy. Consider a shorter alternative.
Context: ...when mump2p vs GossipSub starts to fail under stress. How: * Test both `NODE_MODE=goss...

(EN_WORDINESS_PREMIUM_UNDER_STRESS)

🔇 Additional comments (22)

docs/learn/overview/intro.md (2)

15-20: LGTM! Consistent branding update.

The renaming from "mumP2P" to "mump2p" is applied consistently throughout the introduction, including the product section header and the associated links.

---

43-43: LGTM! Consistent update in "Start here" section.

The CLI reference correctly uses the new "mump2p" branding.

docs/guides/05-faq-glossary.md (1)

110-110: LGTM! Link label updated correctly.

The documentation link label is updated to "mump2p Documentation" while maintaining the correct link target.

.vitepress/config.mts (2)

195-196: LGTM! Sidebar navigation updated.

The sidebar label in the Overview section correctly reflects the new "mump2p Protocol" branding.

---

253-253: LGTM! Research section navigation updated.

The sidebar label in the Research section is consistently updated to "mump2p Protocol".

docs/guides/02-getting-started-docker.md (3)

6-20: LGTM! Architecture descriptions updated.

The deployment mode descriptions and image references are correctly updated to use "mump2p" branding.

---

35-44: LGTM! Mode comparison table updated.

The table comparing deployment modes consistently uses the new "mump2p" terminology.

---

122-122: LGTM! Section heading updated correctly.

The Mode A section heading properly reflects the "mump2p" branding.

docs/guides/03-parameters.md (3)

1-17: LGTM! Parameters guide heading and mode descriptions updated.

The main heading and protocol mode descriptions are consistently updated to use "mump2p" throughout.

---

137-137: LGTM! Configuration example label updated.

The quick-start configuration section correctly references "mump2p Mode".

---

203-203: LGTM! Reference note updated.

The production defaults note correctly references "mump2p nodes".

docs/guides/overview.md (2)

19-26: LGTM! Quick start section updated.

The "Try mump2p" heading and CLI references are correctly updated with the new branding.

---

80-84: LGTM! Glossary and technical reference updated.

The control messages definition and technical overview link correctly use "mump2p" terminology.

docs/guides/04-experiments.md (3)

20-36: LGTM! Experiment descriptions updated consistently.

The experiment titles, goals, and expected results correctly use "mump2p" terminology throughout.

---

140-142: LGTM! Code example updated with new enum name.

The trace handler example correctly references MessageTraceOptimump2p in both the case statement and printf output.

---

16-16: Unable to verify protobuf definition in repository.

The repository contains no .proto files to verify against. While the documentation is internally consistent—all references use MessageTraceOptimump2p (lowercase 'p2p') in both the descriptive text and Go code example—the actual gRPC protobuf enum definition cannot be confirmed in this codebase.

Please confirm that MessageTraceOptimump2p matches the actual enum name in your protobuf definition file (typically in a separate protobuf repository or subdirectory).

docs/learn/overview/p2p.md (6)

1-8: LGTM! Protocol page title and introduction updated.

The main heading and introduction consistently use "mump2p" branding throughout, including the "How mump2p Works" section.

---

12-18: LGTM! Node architecture description updated.

The node architecture section correctly references "mump2p node" terminology.

---

63-74: LGTM! Control messages and configuration sections updated.

The control messages table introduction and RLNC encoding sections are correctly updated to reference "mump2p".

---

84-90: LGTM! Mesh topology documentation updated.

The mesh topology explanation correctly uses "mump2p" when describing its relationship to libp2p's GossipSub.

---

94-136: LGTM! Use cases section updated consistently.

The use cases section, including validators, AI, DePIN, and gaming scenarios, consistently uses "mump2p" terminology throughout.

---

141-160: LGTM! Security model updated.

The security model section heading and pollution attack mitigation subsection correctly reference "mump2p".

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}