diff --git a/_posts/2024-12-09-quarkus-rpi-bare-metal.asciidoc b/_posts/2024-12-09-quarkus-rpi-bare-metal.asciidoc
index 37381e80541..fa1b0207363 100644
--- a/_posts/2024-12-09-quarkus-rpi-bare-metal.asciidoc
+++ b/_posts/2024-12-09-quarkus-rpi-bare-metal.asciidoc
@@ -120,11 +120,10 @@ NOTE: Currently, the Dev UI is not available in the remote dev mode for security
 === Step 4 - Run in production
 
 Of course, you can run your Quarkus app in a JVM on the target Raspberry Pi.
-But the startup is a bit slow, more than ten seconds even for simple apps.
-Also Raspberry Pi is not endowed with a large amount of memory.
+However, Raspberry Pi is not endowed with a large amount of memory.
 So what about native image?
 That might be a perfect fit.
-However, there's one problem - Raspberry Pi is an ARM-based single-board computer (`aarch64` architecture for Raspberry Pi 4 Model B).
+There's one problem though - Raspberry Pi is an ARM-based single-board computer (`aarch64` architecture for Raspberry Pi 4 Model B).
 But your machine might be Intel-based (`x86_64` architecture).
 In other words, usually you cannot build the native image of your machine and run it on Raspberry Pi.