diff --git a/content/waku/updates/2024-10-14.md b/content/waku/updates/2024-10-14.md
index e8499d8b7..5bdf433d5 100644
--- a/content/waku/updates/2024-10-14.md
+++ b/content/waku/updates/2024-10-14.md
@@ -11,7 +11,7 @@ date: 2024-10-14
   - achieved:
     - [research] progress on Waku Sync 2.0 POC
     - [research] Received input on store sync test goals and made progress on a test plan
-    - [nwaku] Enhance error response instead of ambiguous numerical in waku_sync. We need two pull requests, one for negentropy and another one for nwaku. [](https://github.com/waku-org/nwaku/pull/3102) [](https://github.com/waku-org/negentropy/pull/13)
+    - [nwaku] Enhance error response instead of ambiguous numerical in waku_sync. We need two pull requests, one for negentropy and another one for nwaku. [1](https://github.com/waku-org/nwaku/pull/3102) [2](https://github.com/waku-org/negentropy/pull/13)
   - next:
     - [research] finishing Waku Sync 2.0 POC
     - [research] get store sync enabled again on status.staging and implement docker-compose to run multiple store sync nodes with their own DB for simulations
@@ -118,7 +118,7 @@ date: 2024-10-14
   - [nwaku] Remove spammy log [fix: remove spammy log](https://github.com/waku-org/nwaku/pull/3091)
   - [nwaku] Temporarily skip flaky test [chore: improving and temporarily skipping flaky rln test](https://github.com/waku-org/nwaku/pull/3094)
   - [nwaku] Analyzed perf logs of nodes getting stuck. Progressed with the investigation and seem close to a resolution, asked DST for some extra information [bug: node getting stuck and missing messages](https://github.com/waku-org/nwaku/issues/2921)
-  - [js-waku] refined API for connecting to the network [chore: make waitForRemotePeer part of the waku interface](https://github.com/waku-org/js-waku/issues/1761)
+  - [js-waku] refined API for connecting to the network [chore: make waitForRemotePeer part of the waku interface](https://github.com/waku-org/js-waku/issues/1761)
   - [js-waku] improved gathering of metrics for frequently occurring events
   - [js-waku] expose peerId and protocols from main object for better API [feat: expose peerId and protocols from WakuNode](https://github.com/waku-org/js-waku/pull/2166)
   - [js-waku] improve API for awaiting peers in the network by enabling it on the main object [feat: replace waitForRemotePeers() with waku.waitForPeer() method](https://github.com/waku-org/js-waku/pull/2161)