Apply suggestions from code review

Co-authored-by: Jiri Herrmann <jherrman@redhat.com>

Author: MichalMaler

_posts/2025-10-23-mmaler-blogpost-2-quarkus-runtime-and-framework-for-cloud-native-java.adoc

@@ -86,24 +86,25 @@ Rapid startup improves elasticity and recovery, while resilience prevents local
 For a broader industry perspective, see the link:https://cacm.acm.org/practice/application-frameworks/[ACM article on application frameworks].
 
 Quarkus shifts work from runtime to build time, thus enabling faster cold starts.
-Additionally, it offers the option to generate native executables with GraalVM's native-image, enabling cold starts in milliseconds and a minimal memory footprint, resulting in higher pod density, quicker horizontal scaling, and lower idle costs.
+Additionally, it offers the option to generate native executables with GraalVM's native-image, enabling cold starts in milliseconds and a minimal memory footprint.
+This results in higher pod density, quicker horizontal scaling, and lower idle costs.
 As such, it enables cost-effective deployment in containers and serverless environments.
 
-Native images often give faster startup and lower RSS; however, they can deliver lower peak throughput and exhibit scaling limits on multi-core machines.
+Native images often provide faster startup and lower RSS. However, they can deliver lower peak throughput and exhibit scaling limits on multi-core machines.
 Current native images typically use a single-threaded garbage collector, which is inefficient for large heaps and does not benefit from multiple cores.
-We generally recommend native execution for services that run on smaller instances up to two vCPUs with roughly two to four gigabytes of RAM, where startup time and memory footprint dominate cost and user experience.
+We generally recommend native execution for services that run on smaller instances, up to 2 vCPUs with roughly 2-4 gigabytes of RAM, where startup time and memory footprint dominate cost and user experience.
 
 JVM execution, by contrast, takes longer to start and warm up.
-However, it can achieve higher peak performance through just-in-time compilation, it scales well beyond two cores, and it offers more capable garbage collectors and tuning options.
+However, it can achieve higher peak performance through just-in-time compilation. It also scales well beyond two cores and it offers more capable garbage collectors and tuning options.
 
 Choose the mode that matches your workload profile, cold-start targets, and cost envelope, and let Quarkus maintain a consistent development model across both paths.
 
-* If you optimize for native execution, audit reflection and resource usage, enable dead-code elimination friendly patterns, and consider profile-guided optimizations where appropriate.
-* If you optimize for JVM execution, budget for warmup, enable the right GC for your heap and latency goals, and measure steady-state throughput under realistic load.
+* If you optimize for native execution, audit reflection and resource usage, enable dead-code elimination-friendly patterns, and consider profile-guided optimizations where appropriate.
+* If you optimize for JVM execution, budget for warm up, enable the right GC for your heap and latency goals, and measure steady-state throughput under realistic load.
 
 Quarkus also includes structured health checks, metrics, and tracing, which align the runtime with production standards from day one.
 
-Taken together, these in production choices provide measurable wins, as the next examples illustrate.
+Taken together, these in production choices provide measurable wins:
 
 image::7-success-stories.png[alt="Real-world success stories using Quarkus", width=100%]
 
@@ -146,12 +147,12 @@ Because Quarkus modularity is declarative and unified across extensions, it supp
 
 === Building your stack with Quarkus
 
-We will explore this topic in depth in part three of this series.
+We will explore this topic in depth in part 3 of this series.
 For now, here is how Quarkus fits into the picture.
 
 Frameworks can serve as a foundation for creating higher-level abstractions.
 
-Quarkus fits naturally into this model—not by becoming a platform itself, but by enabling teams to build their customized stacks and frameworks on top of it.
+Quarkus fits naturally into this model — not by becoming a platform in itself, but by enabling teams to build their customized stacks and frameworks on top of it.
 
 Unlike many traditional frameworks, Quarkus provides a unified extension architecture that supports deep customization.
 Organizations can tailor Quarkus to fit specific domains, technologies, or compliance needs.
@@ -161,7 +162,7 @@ By encouraging consistency, offering buildtime integration, and exposing clean e
 
 By packaging Quarkus extensions, curated defaults, and service templates into an internal Quarkus stack, teams focus on business logic.
 At the same time, your framework layer standardizes infrastructure, security, and operational integrations across services.
-This has been exemplified by Logicdrop, which refactored its entire Spring Boot stack with Quarkus, reducing container size by ~75%, achieving sub-second startup times, and significantly improving developer productivity.
+This has been proven by Logicdrop, who refactored their entire Spring Boot stack with Quarkus, reducing container size by ~75%, achieving sub-second startup times, and significantly improving developer productivity.
 
 For more information, see the link:https://quarkus.io/blog/logicdrop-customer-story/[Logicdrop customer story] and their link:https://quarkus.io/blog/logicdrop-automating-quarkus-with-gitlab/?utm_source=chatgpt.com[GitLab automation write-up].
 
@@ -173,7 +174,7 @@ As a runtime, it delivers fast startup, low memory use, and operational consiste
 This dual role helps teams standardize practices, reduce costs, and ship resilient cloud-native services.
 
 Quarkus is built in the open under the Apache License 2.0, governed with the Commonhaus model, and developed end-to-end on GitHub.
-Beyond the core project, the ecosystem includes the link:https://hub.quarkiverse.io/[Quarkiverse Hub], a community-run collection of Quarkus link:https://quarkus.io/extensions/[extensions] and related projects.
+Beyond the core project, the ecosystem includes the link:https://hub.quarkiverse.io/[Quarkiverse Hub], a community-run collection of link:https://quarkus.io/extensions/[Quarkus extensions] and related projects.
 The Quarkiverse Hub provides repository hosting with build, CI, and release publishing, so features land as versioned, testable modules you can adopt, fork, or extend.
 
 image::8-expectations.png[alt="Setting expectations for performance and developer experience with Quarkus", width=100%]