Add QEMU screenshot

blog/content/edition-3/posts/02-booting/index.md

@@ -13,7 +13,7 @@ icon = '''
 </svg>
 '''
 
-extra_content = ["uefi.md"]
+extra_content = ["uefi/index.md"]
 +++
 
 In this post, we explore the boot process on both BIOS and UEFI-based systems. We combine the [minimal kernel] created in the previous post with a bootloader to create a bootable disk image. We then show how this image can be started in the [QEMU] emulator and run on real hardware.
@@ -148,7 +148,7 @@ As it is probably clear at this point, the UEFI interface is very powerful and c
 
 To keep this post focused, we won't cover the creation of an UEFI bootloader here. Instead, we will use the already mentioned [`bootloader`] crate, which allows loading our kernel on both UEFI and BIOS systems. If you're interested in how to create an UEFI bootloader yourself, check out our extra post about [**UEFI Booting**].
 
-[**UEFI Booting**]: @/edition-3/posts/02-booting/uefi.md
+[**UEFI Booting**]: @/edition-3/posts/02-booting/uefi/index.md
 
 ### The Multiboot Standard
 

blog/content/edition-3/posts/02-booting/uefi/index.md

@@ -436,7 +436,7 @@ The result of this command is a `.fat` and a `.img` file next to the given `.efi
 
 [run-instructions]: @/edition-3/posts/02-booting/index.md#running-our-kernel
 
-TODO screenshot
+![QEMU screenshot showing some UEFI firmware output](minimal-uefi-qemu.png)
 
 We don't see any output from our `uefi_app` on the screen yet since we only `loop {}` in our `efi_main`. Instead, we see some output from the UEFI firmware itself that was created before our application was started.