Update 1-deploy-contract-on-morph.md

[drewaz]

1. Updated Holesky to Hoodi
2. Grammatical changes

Summary by CodeRabbit

• Documentation
  • Updated build guide to reference the Morph Hoodi Testnet instead of Holesky across names, tips, and headers.
  • Replaced faucet, bridge, explorer URLs, and API references with Hoodi equivalents.
  • Revised Hardhat/Foundry narratives and node/yarn link text to Hoodi domains.
  • Adjusted deployment, verification, and post-deploy steps to target Hoodi.
  • Applied minor grammar and capitalization improvements for clarity.

[coderabbitai]

Walkthrough

Renames Holesky references to Hoodi across a single documentation page, updating testnet names, links (faucet, bridge, explorer/API), and tool narratives (Hardhat/Foundry). Adjusts wording and capitalization to align with Hoodi terminology. No code, API, or control-flow changes—documentation-only updates.

Changes

Cohort / File(s)	Summary of Changes
Docs: Testnet rename to Hoodi docs/build-on-morph/code-examples/1-deploy-contract-on-morph.md	Replaced Holesky with Hoodi across text, tips, and headers; updated faucet/bridge/explorer URLs and API endpoints; aligned Hardhat/Foundry narratives and node/yarn link text to Hoodi domains; minor grammar/style fixes; deployment and verification steps now reference Morph Hoodi Testnet.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I thump with glee on the Hoodi plain,
Holesky’s footprints washed by rain.
Links hop fresh, explorers new,
Faucets burble testnet dew.
Docs now nibble crisp and clean—
On Morph we bound, a Hoodi scene! 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The title only references the filename and does not describe the substantive changes made, which include renaming network references from Holesky to Hoodi and applying grammatical updates.	Please revise the title to clearly summarize the primary change, for example “Replace Holesky with Hoodi in deployment guide and update grammar.”

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🧪 Early access (Sonnet 4.5): enabled

We are currently testing the Sonnet 4.5 model, which is expected to improve code review quality. However, this model may lead to increased noise levels in the review comments. Please disable the early access features if the noise level causes any inconvenience.

Note:

• Public repositories are always opted into early access features.
• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.

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

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9549a05 and fe4ec98.

📒 Files selected for processing (1)

• docs/build-on-morph/code-examples/1-deploy-contract-on-morph.md (6 hunks)

🔇 Additional comments (6)

docs/build-on-morph/code-examples/1-deploy-contract-on-morph.md (6)

8-10: LGTM! Introduction updated correctly.

The testnet name has been properly updated to "Morph Hoodi Testnet" and the demo repository reference is clear.

---

36-36: LGTM! Installation links are correct.

The nodejs and yarn installation links point to official sources.

---

98-99: LGTM! Explorer URLs updated consistently.

The API and browser URLs correctly use the "hoodi" subdomain pattern.

---

119-119: LGTM! Grammatical improvement.

The phrase "Once successful" is grammatically correct and the explorer link is properly updated to Hoodi.

---

178-178: LGTM! Consistent with Hardhat section.

The success message maintains consistency with the Hardhat section and correctly links to the Hoodi explorer.

---

183-183: LGTM! Closing message updated correctly.

The thank you message properly references "Morph Hoodi Testnet" and provides appropriate support channel information.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix naming inconsistency: "Hodi" should be "Hoodi".

Line 14 references "Hodi" while the rest of the document consistently uses "Hoodi". This appears to be a typo.

Apply this diff to fix the inconsistency:

-  [bridge](https://bridge-hoodi.morphl2.io) to transfer some test ETH from _Hodi_ to _Morph Hoodi_. 
+  [bridge](https://bridge-hoodi.morphl2.io) to transfer some test ETH from _Hoodi_ to _Morph Hoodi_. 

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Before you start deploying the contract, you need to request test tokens from a Hoodi faucet and use the
	[bridge](https://bridge-hoodi.morphl2.io) to transfer some test ETH from _Hodi_ to _Morph Hoodi_.
	Before you start deploying the contract, you need to request test tokens from a Hoodi faucet and use the
	[bridge](https://bridge-hoodi.morphl2.io) to transfer some test ETH from _Hoodi_ to _Morph Hoodi_.

🤖 Prompt for AI Agents

In docs/build-on-morph/code-examples/1-deploy-contract-on-morph.md around lines
13 to 14, there is a naming inconsistency where "_Hodi_" is used instead of the
correct "_Hoodi_"; update the typo so the sentence consistently reads "Hoodi"
(e.g., replace "Hodi" with "Hoodi") to match the rest of the document.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix grammatical error: "initialing" should be "initial".

The word "initialing" is not standard English in this context. It should be "initial" (adjective) or "initialization" (noun).

Apply this diff to fix the grammar:

-Then run the following command to deploy the contract on the Morph Hoodi Testnet. This will run the deployment script that set the initialing parameters, you can edit the script in scripts/deploy.ts
+Then run the following command to deploy the contract on the Morph Hoodi Testnet. This will run the deployment script that sets the initial parameters, you can edit the script in scripts/deploy.ts

Note: Also fixed "set" → "sets" for subject-verb agreement.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Then run the following command to deploy the contract on the Morph Hoodi Testnet. This will run the deployment script that set the initialing parameters, you can edit the script in scripts/deploy.ts
	Then run the following command to deploy the contract on the Morph Hoodi Testnet. This will run the deployment script that sets the initial parameters, you can edit the script in scripts/deploy.ts

🤖 Prompt for AI Agents

In docs/build-on-morph/code-examples/1-deploy-contract-on-morph.md around line
74, fix the grammar in the sentence "This will run the deployment script that
set the initialing parameters, you can edit the script in scripts/deploy.ts" by
changing "set" to "sets" for correct subject-verb agreement and replacing
"initialing" with "initial" (or "initialization" if you prefer the noun form),
ensuring the sentence reads clearly (e.g., "...that sets the initial parameters;
you can edit the script in scripts/deploy.ts").