better align prereleases section with that of the aws package

Author: dario-piotrowicz

README.md

@@ -21,19 +21,20 @@ The repository contains two directories:
 
 You can simply install the package from npm as specified in the [OpenNext documentation](https://opennext.js.org/cloudflare/get-started).
 
-> [!note]
-> There are also prerelease packages that we automatically publish on branch pushes (using [`pkg.pr.new`](https://github.com/stackblitz-labs/pkg.pr.new)):
->
-> - `https://pkg.pr.new/@opennextjs/cloudflare@main`:
->
->   Updated with every push to the `main` branch, this prerelease contains the most up to date yet (reasonably) stable version of the package.
->
-> - `https://pkg.pr.new/@opennextjs/cloudflare@experimental`
->
->   Updated with every push to the `experimental` branch (when present), this prerelease contains the latest experimental version of the package (containing features
->   that we want to test/experiment on before committing to).
->
-> Which you can simply install directly with your package manager of choice, for example: `npm i https://pkg.pr.new/@opennextjs/cloudflare@experimental`
+#### Preleases
+
+Besides the standard npm releases we also automatically publish prerelease packages on branch pushes (using [`pkg.pr.new`](https://github.com/stackblitz-labs/pkg.pr.new)):
+
+- `https://pkg.pr.new/@opennextjs/cloudflare@main`:
+  Updated with every push to the `main` branch, this prerelease contains the most up to date yet (reasonably) stable version of the package.
+- `https://pkg.pr.new/@opennextjs/cloudflare@experimental`
+  Updated with every push to the `experimental` branch, this prerelease contains the latest experimental version of the package (containing features that we want to test/experiment on before committing to).
+
+Which you can simply install directly with your package manager of choice, for example:
+
+```bash
+npm i https://pkg.pr.new/@opennextjs/cloudflare@main
+```
 
 ### How to develop in the repository