Minor edits and remove `` in title

_posts/2024-04-15-heapdump-oome-native.adoc

@@ -1,6 +1,6 @@
 ---
 layout: post
-title: 'Obtaining heap dump on `OutOfMemoryError` in Quarkus native'
+title: 'Obtaining heap dump on OutOfMemoryError with Quarkus native'
 date: 2024-04-15
 tags: native heapdump oome epsilongc jol
 synopsis: 'Generating and inspecting heap dumps in Quarkus native when `OutOfMemoryError` errors occur'
@@ -18,10 +18,11 @@ Once the Quarkus application is running with Epsilon GC,
 apply some load and within a short space of time it will run out of memory and produce a heap dump.
 
 Let’s start by producing a heap dump with a Quarkus native executable.
-A good starting point would be a Quarkus application that simply responds to an HTTP endpoint request, e.g.
-https://github.com/quarkusio/quarkus-quickstarts/tree/main/getting-started-reactive[the getting-started-reactive Quarkus quickstart].
+A good starting point would be a Quarkus application that simply responds to an HTTP endpoint request, e.g. the
+https://github.com/quarkusio/quarkus-quickstarts/tree/main/getting-started-reactive[getting-started-reactive] Quarkus quickstart.
 Once checked out,
-build a Quarkus native executable GraalVM for JDK 21 for the application that uses Epsilon GC:
+build a Quarkus native executable with GraalVM for JDK 21 configuring Epsilon GC.
+For Quarkus native mode, selecting the GC needs to be done at build time:
 
 [source,bash]
 ----