Update index.html

[Mr-HoDL58]

Update text to Aerium Network.

Summary by CodeRabbit

• Style
  • Updated the homepage hero heading text from “Aerium Blockchain” to “Aerium Network” to reflect current branding.
  • No changes to layout, navigation, logo, tagline, links, footer, scripts, or styling.
  • This is a visual copy update only; functionality and behavior remain unchanged.

[coderabbitai]

Walkthrough

The hero heading text in index.html is updated from "Aerium Blockchain" to "Aerium Network" within the existing brand block. No other DOM structure, attributes, styling, or scripts are changed.

Changes

Cohort / File(s)	Change Summary
Hero text update index.html	Changed h1 text from "Aerium Blockchain" to "Aerium Network"; no other modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled the headline, crisp and neat,
Swapped “Blockchain” for “Network” sweet.
A tiny hop, a gentle tweak,
Brand-new name for the hero’s peak.
Thump-thump! my paws in tidy sync—
One word changed, quicker than a wink.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR changes the hero heading in index.html from "Aerium Blockchain" to "Aerium Network" per the raw_summary and PR description, so the title "Update index.html" correctly identifies the modified file and is related to the main change. The title is concise but generic and does not state the specific text change, though that level of specificity is not required to pass this check.
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

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

index.html (2)

6-13: Sync page title and Open Graph with “Aerium Network”.

Recommend updating these tags to reflect the new brand for search and share previews.

-  <title>Aerium — Coming Soon</title>
+  <title>Aerium Network — Coming Soon</title>
-  <meta name="description" content="Aerium is a next-generation blockchain. We're launching soon.">
+  <meta name="description" content="Aerium Network is a next-generation blockchain network. We're launching soon.">
-  <meta property="og:title" content="Aerium — Coming Soon">
+  <meta property="og:title" content="Aerium Network — Coming Soon">
-  <meta property="og:description" content="Aerium is a next-generation blockchain. We're launching soon.">
+  <meta property="og:description" content="Aerium Network is a next-generation blockchain network. We're launching soon.">

---

136-136: Either open external link in a new tab securely, or drop the inert rel attribute.

rel="noopener" has effect only with target="_blank". Choose one:

Option A (new tab, safer):

-      <a class="btn" href="https://github.com/aerium-network" rel="noopener">GitHub</a>
+      <a class="btn" href="https://github.com/aerium-network" target="_blank" rel="noopener noreferrer">GitHub</a>

Option B (same tab, cleaner):

-      <a class="btn" href="https://github.com/aerium-network" rel="noopener">GitHub</a>
+      <a class="btn" href="https://github.com/aerium-network">GitHub</a>

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c5e2fb2 and 4ff320f.

📒 Files selected for processing (1)

• index.html (1 hunks)

🔇 Additional comments (1)

index.html (1)

134-134: Brand text change looks good; align metadata for consistency and SEO.

H1 updated to "Aerium Network" is clear. Ensure the rest of the page (title/OG/meta) uses the same brand to avoid mixed signals in SERP and link previews.