Fix devlog section links (#605)

Author: mattnite

website/content/devlog.smd

@@ -11,8 +11,7 @@
 .draft = false,
 ---
 
-[]($section.id('about'))
-## About
+## [About]($section.id('about'))
 
 This is a non-exhaustive, curated list of changes meant to help users quickly
 see what has improved since they last checked.
@@ -21,9 +20,7 @@ You can [subscribe to this page via RSS]($link.alternative('rss')).
 
 ## Changes
 
-[]($section.id('regz-wizard').data('date','2025-04-28'))
-
-### Regz Wizard
+### [Regz Wizard]($section.id('regz-wizard').data('date','2025-06-22'))
 
 []($image.asset('regz-wizard-01.png'))
 
@@ -39,17 +36,13 @@ exist](https://github.com/embassy-rs/stm32-data) just to provide consistent
 data structure between MCUs. This consistency makes it easier to write HALs
 that are portable across multiple MCUs.
 
-[]($section.id('initial-microbit-support').data('date','2025-04-28'))
-
-### Initial micro:bit support
+### [Initial micro:bit support]($section.id('initial-microbit-support').data('date','2025-06-19'))
 
 Add support for the micro:bit 5x5 led display.
 
 []($image.asset('microbit-display.jpeg'))
 
-[]($section.id('linker-script-generation').data('date','2025-06-18'))
-
-### Linker Script Generation
+### [Linker Script Generation]($section.id('linker-script-generation').data('date','2025-06-18'))
 
 Every firmware needs a linker script that places stuff where it belongs in
 memory. When porting microzig to a new target you must face the challenge of
@@ -215,9 +208,7 @@ INSERT BEFORE .flash_start;
   This applies to the rp2040 target where the section tagged as ram is
   executable.
 
-[]($section.id('start').data('date','2025-04-28'))
-
-### Devlog Begins!
+ ### [Devlog Begins!]($section.id('2025-04-28'))
 
-The MicroZig devlog is now set up for contributors to showcase their work. When
-adding your work, add to the top of the list.
+ The MicroZig devlog is now set up for contributors to showcase their work. When
+ adding your work, add to the top of the list.