diff --git a/content/waku/collaboration/nwaku-release-process.md b/content/waku/collaboration/nwaku-release-process.md
index b362d993d..1f6ef1ac5 100644
--- a/content/waku/collaboration/nwaku-release-process.md
+++ b/content/waku/collaboration/nwaku-release-process.md
@@ -8,6 +8,18 @@ date: 2024-07-22
 lastmod: 2024-07-22
 ---
 
+## Testing week
+
+On each release, we establish a testing period of one week, when we lock the `waku.test` fleet so that it only runs the target version. During that period, we need to continuously stress that fleet from the sandbox machine, for example.
+
+It is important to make sure the `waku-simulator` works as expected and the nodes can establish connections among themselves.
+
+During that week, the release owner needs to check the *Kibana* logs from the previous month (since the last release was deployed) looking for possible crashes or errors in `waku.test` & `waku.sandbox`. These are the most relevant logs to check:
+
+- `(fleet: "waku.test" OR fleet: "waku.sandbox") AND message: "SIGSEGV"`
+
+Make sure that Status client works properly when connected to a fleet running on the release candidate version. For it, please follow its corresponding [guide](waku/collaboration/test-nwaku-on-status.md).
+
 ## Release Calendar
 
 | Name   | Date   | Release Owner   | nwaku-version   | Comment   |
@@ -34,16 +46,3 @@ lastmod: 2024-07-22
 | waku.sandbox deployment | 2024-09-25 | Zoltan  | 0.33.x |  |
 | waku.test deployment    | 2024-10-28 | Gabriel | 0.34.0 |  |
 | waku.sandbox deployment | 2024-10-30 | Gabriel | 0.34.x |  |
-
-
-## Testing week
-
-On each release, we establish a testing period of one week, when we lock the `waku.test` fleet so that it only runs the target version. During that period, we need to continuously stress that fleet from the sandbox machine, for example.
-
-It is important to make sure the `waku-simulator` works as expected and the nodes can establish connections among themselves.
-
-During that week, the release owner needs to check the *Kibana* logs from the previous month (since the last release was deployed) looking for possible crashes or errors in `waku.test` & `waku.sandbox`. These are the most relevant logs to check:
-
-- `(fleet: "waku.test" OR fleet: "waku.sandbox") AND message: "SIGSEGV"`
-
-Make sure that Status client works properly when connected to a fleet running on the release candidate version. For it, please follow its corresponding [guide](waku/collaboration/test-nwaku-on-status.md).
\ No newline at end of file