FIX TYPOs

_posts/2024-04-18-ship-cars-leverages-quarkus-to-reach-its-goals.adoc

@@ -96,7 +96,7 @@ image::memory.png[Memory usage,title="Memory usage of a Quarkus native image"]
 
 - Reduced container size: Being fully self-contained, the container images for native images are more efficient to distribute due to their reduced size.
 This leads to faster start-up times in containerized environments like Kubernetes.
-For example, the size comparison between `Quarkus Native (85.1 MB)`, `Quarkus Non-Native (648.4 MB) `and `Spring Boot (861.9 MB)` provides a clear picture of the difference in resource efficiency between them.
+For example, the size comparison between `Quarkus Native (85.1 MB)`, `Quarkus Non-Native (648.4 MB)` and `Spring Boot (861.9 MB)` provides a clear picture of the difference in resource efficiency between them.
 
 With Quarkus, you can compile your application into a native image by leveraging the GraalVM native-image compiler, allowing your Java applications to experience these advantages in cloud platforms, containerization, and serverless architectures due to their swift startup times and lower resource consumption.
 
@@ -113,7 +113,7 @@ With Quarkus, you can compile your application into a native image by leveraging
 
 5. **Unified config**: All of the application's configurations are consolidated in one place, improving accessibility.
 
-6. Standards-based
+6. **Standards-based**
 
 == Embracing Quarkus extensions