[Intermediate]: Refactor the What is Hiero? Hiero is fair... etc sections to be briefer

[aceppaluni]

🧩 Intermediate Contributors

This issue is intended for contributors who are already very familiar with the
Hiero Website codebase and its architectural patterns.

You should feel comfortable with:

• Netlify previews and tests
• The Hiero website repository structure
• understanding Hugo templating concepts without step-by-step guidance
• Editing and organizing Markdown at scale
• Making pull requests with minimal guidance
• navigating layouts/, content/, partials/, and static/
• following the standard PR workflow without additional onboarding

If this is your very first contribution to the project, we recommend starting with a few
Good First Issues before working on this one.

🐞 Problem Description

We have a Hiero is fair
Hiero is fast
Hiero is secure
Hiero is decentralized
Hiero is leaderless
Hiero is open

but these have large text sections
e.g

A ledger with a leader-based consensus protocol is inherently unfair, and either slow or susceptible to denial of service attacks. We believe in a future where every node can participate on an equal basis with a completely leaderless consensus protocol, safe from denial-of- service, and safe from centralization.

These are very informative, but too long for a home page.
Perhaps they are better tackled in a blog?

💡 Expected Solution

We can cut down all the sections eg

A ledger with a leader-based consensus protocol is inherently unfair, and either slow or susceptible to denial of service attacks. We believe in a future where every node can participate on an equal basis with a completely leaderless consensus protocol, safe from denial-of- service, and safe from centralization.

Into something that says the same key message but way more concise, so people can scan the website easily

🧠 Implementation Notes

Refactor these paragraphs more concise.

✅ Acceptance Criteria

To merge this issue, the pull request must:

• Fully address the problem described above
• Follow existing project conventions and patterns
• Include tests or example updates where appropriate
• Pass all CI checks
• Include a valid changelog entry
• Use DCO and GPG-signed commits

📚 Additional Context or Resources

• Website Developer Docs