Update 4-blockchain-indexing-services.md

[drewazarias-dev]

1. Updated Holesky to Hoodi
2. Grammar change (“Goldsky also allow us” to “Goldsky also allows us”)

Summary by CodeRabbit

• Documentation
  • Updated blockchain indexing services guide to reference Morph Hoodi instead of Morph Holesky in Goldsky and Envio sections.
  • Corrected grammar in the Goldsky description for readability.
  • Clarified wording around the live indexer link while keeping the URL unchanged.

[coderabbitai]

Walkthrough

Simple documentation edits in a single Markdown file: replace references to Morph Holesky with Morph Hoodi in Goldsky and Envio sections, fix a grammar issue (“allow” → “allows”), and slightly adjust wording without changing URLs.

Changes

Cohort / File(s)	Summary of edits
Docs: Blockchain indexing services wording updates docs/build-on-morph/developer-resources/use-ecosystem-developer-tools/4-blockchain-indexing-services.md	Replaced “Morph Holesky” with “Morph Hoodi” (Goldsky, Envio), corrected grammar (“allow” → “allows”), minor sentence wording update; URLs unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my nose at words anew,
From Holesky’s burrow to Hoodi’s view—
Goldsky gleams, Envio hums,
Grammar hops where clarity comes.
Small edits made, the trails align;
Docs now crisp—carrots divine! 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The title “Update 4-blockchain-indexing-services.md” correctly identifies the file affected but is overly generic and does not summarize the key changes such as renaming “Holesky” to “Hoodi” or the grammar fix. It fails to convey the substantive updates made in the pull request.	Please revise the title to clearly reflect the primary changes, for example “Rename Morph Holesky to Morph Hoodi and fix grammar in blockchain indexing services doc.”

✅ 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: 1

🧹 Nitpick comments (1)

docs/build-on-morph/developer-resources/use-ecosystem-developer-tools/4-blockchain-indexing-services.md (1)

28-28: Consider more descriptive link text for accessibility.

The link text "here" is not descriptive. Consider using more meaningful text that describes the link destination, such as "live indexer examples" or "Envio's live indexer explorer."

Apply this diff to improve link accessibility:

-Click [here](https://envio.dev/explorer) for live indexer examples to be inspired.  
+Click [Envio's live indexer explorer](https://envio.dev/explorer) for examples to inspire your implementation.

📜 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 3f3f6d3.

📒 Files selected for processing (1)

• docs/build-on-morph/developer-resources/use-ecosystem-developer-tools/4-blockchain-indexing-services.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

docs/build-on-morph/developer-resources/use-ecosystem-developer-tools/4-blockchain-indexing-services.md

28-28: Link text should be descriptive

(MD059, descriptive-link-text)

🔇 Additional comments (2)

docs/build-on-morph/developer-resources/use-ecosystem-developer-tools/4-blockchain-indexing-services.md (2)

12-12: Grammar correction is accurate.

The change from "allow" to "allows" correctly fixes the subject-verb agreement for the singular subject "Goldsky."

---

20-20: Network name update is consistent.

This change correctly updates the testnet name to "Morph Hoodi," maintaining consistency with the earlier change on line 10.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Network name update looks correct.

The change from "Morph Holesky" to "Morph Hoodi" appears to be part of a testnet rebranding. Ensure all references to the old testnet name have been updated consistently across the documentation.

Run the following script to check for any remaining references to "Holesky" that may need updating:

---

🏁 Script executed:

#!/bin/bash
# Description: Search for remaining references to "Holesky" in documentation

# Search for "Holesky" case-insensitively in all markdown files
rg -i "holesky" --type=md -n -C2

Length of output: 34708

---

Rename all remaining “Holesky” references to “Hoodi” across documentation.
Update every occurrence in docs/quick-start/, docs/build-on-morph/, docs/code-examples/**, SDK enumeration files, and other developer-resources.

🤖 Prompt for AI Agents

In
docs/build-on-morph/developer-resources/use-ecosystem-developer-tools/4-blockchain-indexing-services.md
around line 10, there remains the string “Holesky” that must be renamed to
“Hoodi”; search the repo (at minimum docs/quick-start/**,
docs/build-on-morph/**, docs/code-examples/**, SDK enumeration files, and any
developer-resources) for any case variants of “Holesky” and perform a safe
replace to “Hoodi” (preserve capitalization where appropriate), update affected
filenames and internal links/refs, adjust any enum keys or string constants in
SDK files to the new name, and run link checks/lint/tests to ensure no broken
references remain.