diff --git a/README.md b/README.md
index 4651010..9df33fd 100644
--- a/README.md
+++ b/README.md
@@ -29,7 +29,29 @@
 | --------------------------------- | --------------------------------- |
 | ![dashboard 3](screenshots/3.png) | ![dashboard 4](screenshots/4.png) |
 
+## Smart Contracts overview ⌨️
+
+We closely analyzed [Vitalik Buterin's blog post](https://vitalik.eth.limo/general/2023/08/16/communitynotes.html) to understand the implementation of the x dot com algorithm and created a simplified version for our smart contracts. Our system has two types of participants: **NoteAuthors** and **NoteVoters**. Each author can vote on a contract only once, and each voter can vote on a note only once. The available voting options are **SOMEWHAT_HELPFUL**, **HELPFUL**, and **NOT_HELPFUL**.
+
+Notes can be tagged as `consideredHelpful` similar to x dot com's community notes. A note needs a score of 40 or more, with over 10 votes, to be tagged as such. The score is calculated using the following formula:
+
+```
+((x * 80) + (y * 40)) / z
+```
 
+**Where**:
+
+x = amount of **HELPFUL** votes
+y = amount of **SOMEWHAT_HELPFUL** votes
+z = total amount of votes
+
+If a note's score falls below 10 after being tagged as `consideredHelpful`, the tag will be removed. We may adjust these values in the future, but for now, this serves as our MVP. Only `consideredHelpful` notes are displayed on the dashboard, and the highest voted note is shown in the MetaMask snap.
+
+We also track each user's positive vs. negative ratio to potentially implement a voting prediction system similar to x dot com's, which would require some off-chain computation.
+
+For chains that support World ID, it serves as an identification layer for writing and voting on notes.
+
+The note text is stored on IPFS, with only the URI stored within the contract.
 
 ## Bounties 😎
 
@@ -87,30 +109,6 @@ We deployed our contracts on Zircuit and manually added the config for the front
 - [Manual network config](https://github.com/chain-notes-brussels/chain-notes-snap/blob/d71b19303b4d260dab5b9d66f40d89af665c750b/packages/nextjs/utils/scaffold-eth/morechains.ts)
 - [Notes.sol on Zircuit](https://explorer.zircuit.com/address/0x77C461C1E180DD6A08A17E74bFb5207e44c7aC7f)
 
-## Smart Contracts overview ⌨️
-
-We closely analyzed [Vitalik Buterin's blog post](https://vitalik.eth.limo/general/2023/08/16/communitynotes.html) to understand the implementation of the x dot com algorithm and created a simplified version for our smart contracts. Our system has two types of participants: **NoteAuthors** and **NoteVoters**. Each author can vote on a contract only once, and each voter can vote on a note only once. The available voting options are **SOMEWHAT_HELPFUL**, **HELPFUL**, and **NOT_HELPFUL**.
-
-Notes can be tagged as `consideredHelpful` similar to x dot com's community notes. A note needs a score of 40 or more, with over 10 votes, to be tagged as such. The score is calculated using the following formula:
-
-```
-((x * 80) + (y * 40)) / z
-```
-
-**Where**:
-
-x = amount of **HELPFUL** votes
-y = amount of **SOMEWHAT_HELPFUL** votes
-z = total amount of votes
-
-If a note's score falls below 10 after being tagged as `consideredHelpful`, the tag will be removed. We may adjust these values in the future, but for now, this serves as our MVP. Only `consideredHelpful` notes are displayed on the dashboard, and the highest voted note is shown in the MetaMask snap.
-
-We also track each user's positive vs. negative ratio to potentially implement a voting prediction system similar to x dot com's, which would require some off-chain computation.
-
-For chains that support World ID, it serves as an identification layer for writing and voting on notes.
-
-The note text is stored on IPFS, with only the URI stored within the contract.
-
 ## Links
 
 - [Live dApp on Vercel](https://chain-notes.vercel.app/)