diff --git a/docs/hackathon/liquity.md b/docs/hackathon/liquity.md
index 9c154e1e..d51815a9 100644
--- a/docs/hackathon/liquity.md
+++ b/docs/hackathon/liquity.md
@@ -27,10 +27,11 @@ Open the project's [GitHub page](https://github.com/liquity/bold) and search for
- `getRoundData`
- `latestRoundData`
-Since the method is called from a smart contract (.sol file), the dApp is eligible. If they were called from the frontend (.ts, .js, .tsx, or .jsx files), the dApp would be unsuitable for the Super Hackathon.
-
+
+
+Since the method is called from a smart contract (.sol file), the dApp is eligible. If they were called from the frontend (.ts, .js, .tsx, or .jsx files), the dApp would be unsuitable for the Super Hackathon.
## 1. Clone the repository
diff --git a/docs/hackathon/rules.md b/docs/hackathon/rules.md
index f45cc179..c0fd3ef1 100644
--- a/docs/hackathon/rules.md
+++ b/docs/hackathon/rules.md
@@ -7,9 +7,11 @@ sidebar_position: 2
## Choosing a dApp for migration
+One way to find eligible dApps is to use the [Chainlink Ecosystem search tool](https://www.chainlinkecosystem.com/ecosystem) and filter by Ethereum, Polygon, and BNB Chain, selecting projects that use Chainlink Data Feeds.
+
### Eligibility requirements
-The original dApp must already use Chainlink Data Feeds in its on-chain logic. See the [list of supported data feeds](/hackathon/data-feeds).
+The original dApp must use Chainlink Data Feeds in its on-chain logic. See the [list of supported data feeds](/hackathon/data-feeds).
The interface methods (`latestAnswer`, `getAnswer`, `latestRound`, `getRoundData`, `latestRoundData`) must be called from a smart contract (.sol file). If they are called from the frontend (.ts, .js, .tsx, or .jsx files), the dApp will not be accepted.
@@ -25,10 +27,6 @@ Frontends are welcome but optional—evaluation is based solely on the deployed
The project’s license must allow forking and reuse (acceptable licenses include MIT, Apache 2.0, GPL-family, or equivalent).
-### Recommendations
-
-One way to find eligible dApps is to use the [Chainlink Ecosystem search tool](https://www.chainlinkecosystem.com/ecosystem) and filter by Ethereum, Polygon, and BNB Chain, selecting projects that use Chainlink Data Feeds.
-
## Deploying to opBNB
All projects must be migrated to opBNB no earlier than the official hackathon start on October 13, 2025, at 11:00 UTC and no later than October 31, 2025, at 11:00 UTC.
diff --git a/docs/hackathon/venus-protocol.md b/docs/hackathon/venus-protocol.md
index f145bb71..d4f828a7 100644
--- a/docs/hackathon/venus-protocol.md
+++ b/docs/hackathon/venus-protocol.md
@@ -26,14 +26,15 @@ Open the project's [GitHub page](https://github.com/VenusProtocol) and search fo
- `getRoundData`
- `latestRoundData`
-Since the method is called from a smart contract (.sol file), the dApp is eligible. If they were called from the frontend (.ts, .js, .tsx, or .jsx files), the dApp would be unsuitable for the Super Hackathon.
-
+
+
+Since the method is called from a smart contract (.sol file), the dApp is eligible. If they were called from the frontend (.ts, .js, .tsx, or .jsx files), the dApp would be unsuitable for the Super Hackathon.
## 1. Clone the repository
-Clone the [Venus Protocol oracle repository](https://github.com/VenusProtocol/oracle):
+Clone the [VenusProtocol/oracle repository](https://github.com/VenusProtocol/oracle):
```bash
git clone https://github.com/VenusProtocol/oracle.git