Fix linter error

content/blog/2024-08-01-gsoc-multiboot2.mdx

@@ -54,13 +54,14 @@ For the purpose of debugging, I needed the `.module` files.
 Obviously, the first module I looked into was `relocator.module`.
 I then needed to determine the base address where I had added my breakpoint.
 The plan was to:
+
 - print the address of the function using `__builtin_return_address(0)`
 - object dump the module to find the offset of the function
 - get the base address by substracting the offset from the address
 
 Pretty straightforward, right?
 Normally, yes.
-But here...
+But here?
 Well, not quite.
 After performing this process with the printed address, `gdb` was showing code from `malloc_in_range` instead of `grub_relocator_alloc_chunk_align`.
 Additionally, it did not match the assembly (which was an infinite loop with a dummy value).
@@ -77,7 +78,7 @@ But after the preprocessor replaced the call with the definition including `grub
 The backtrace also revealed the culprit for the "out of memory" error: the `grub_relocator32_boot` function had been called earlier with a null relocator.
 To see when the relocator changed to null, I set a watchpoint, which quickly indicated the obstacle and allowed for an easy fix.
 
-Drumroll, please...
+Drumrolls, please!
 Ladies and gentlemen, we successfully booted into Unikraft! 🎉
 
 ## Monkey see, Monkey do