diff --git a/pages/cloudflare/_meta.json b/pages/cloudflare/_meta.json
index aff2153..e0d3688 100644
--- a/pages/cloudflare/_meta.json
+++ b/pages/cloudflare/_meta.json
@@ -7,7 +7,8 @@
   "examples": "",
   "community": "Community projects",
   "troubleshooting": "",
-  "migrate-from-0.3-to-0.4": "Migrate from 0.3",
+  "migrate-from-0.4-to-0.5": "Migrate from 0.4",
+  "migrate-from-0.3-to-0.4": "",
   "0.3": "Release 0.3",
   "migrate-from-0.2-to-0.3": "",
   "0.2": "Release 0.2"
diff --git a/pages/cloudflare/migrate-from-0.3-to-0.4.mdx b/pages/cloudflare/migrate-from-0.3-to-0.4.mdx
index 81c9df5..00c78f8 100644
--- a/pages/cloudflare/migrate-from-0.3-to-0.4.mdx
+++ b/pages/cloudflare/migrate-from-0.3-to-0.4.mdx
@@ -1,9 +1,9 @@
 import { SITE } from '../../config';
 import { Callout } from 'nextra/components';
 
-### Migrate from 0.3 (to 0.4)
+### Migrate from 0.3 to 0.4
 
-The `@opennextjs/cloudflare@0.4.0` introduced a new `initOpenNextCloudflareForDev` utility and made `getCloudflareContext` synchronous,
+`@opennextjs/cloudflare@0.4.0` introduced a new `initOpenNextCloudflareForDev` utility and made `getCloudflareContext` synchronous,
 we'll explore those two differences below, and how they effect applications built using `0.3.x` versions of the adapter.
 
 ##### `initOpenNextCloudflareForDev`
diff --git a/pages/cloudflare/migrate-from-0.4-to-0.5.mdx b/pages/cloudflare/migrate-from-0.4-to-0.5.mdx
new file mode 100644
index 0000000..26d371d
--- /dev/null
+++ b/pages/cloudflare/migrate-from-0.4-to-0.5.mdx
@@ -0,0 +1,3 @@
+### Migrate from 0.4 (to 0.5)
+
+`@opennextjs/cloudflare@0.5.0` did not introduce any breaking change, meaning that there are no migration steps from `0.4` to `0.5`.