[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

[freya-docs]

@aceppaluni Hello, do you think I can try this? If I understand correctly, technically it isn't complex - texts are in content/_index.md and they need to be made shorter (more concise, the same value), is that correct? Are there any other changes expected related to layout or design, or is it only about texts?

[exploreriii]

Assigned @freya-docs
The challenge is to keep the same intention and meaning, or what is reasonable, but say this in fewer words. May require some thought, but, yes it is a documentation change

[freya-docs]

@exploreriii Could you confirm that, for example, this is an expected change? Should it go in this direction?

Public forums should be equally accessible. No one should manipulate your transactions to their advantage. Hashgraph is leaderless - toward a fairer world.

instead of:

Everybody should have equal access to all public forums. No one should have the ability to re-prioritize your transactions, or drop them, or front-run, or sandwich trade, or otherwise disadvantage you. The hashgraph algorithm is leaderless. We all deserve a more fair world.

[exploreriii]

I would vote this is great, thanks!