Testing Maven guide

Author: olyagpl

docs/src/docs/asciidoc/end-to-end-maven-guide.adoc

@@ -261,6 +261,13 @@ For example:
 </configuration>
 ----
 
+Run the build command:
+
+[source,bash, role="multi-language-sample"]
+----
+./mvnw -Pnative package
+----
+
 Step 2: **Gather profiles** by running the instrumented executable.
 By default, the _default.iprof_ file, if not specified otherwise, is generated alongside the native executable.
 
@@ -282,10 +289,17 @@ You may want to provide a different name for the native image or create another
 </configuration>
 ----
 
+Run the build command:
+ 
+[source,bash, role="multi-language-sample"]
+----
+./mvnw -Pnative package
+----
+
 If the profile file has the default name and location, it will be automatically picked up.
 Alternatively, you can specify the file path as following: `--pgo=myprofile.iprof`.
 
-Once the optimized image is built, run it.
+Once the optimized image is built, run it: `./target/optimizedApp`.
 The application's performance when running from this native executable should be comparable to, or even faster than, running on the JVM.
 Learn more about PGO https://www.graalvm.org/reference-manual/native-image/optimizations-and-performance/PGO/basic-usage[on the website].
 
@@ -324,7 +338,7 @@ Alternatively, you can **identify missing configuration manually** using the fol
 
 [NOTE]
 ====
-The `--exact-reachability-metadata` option was introduced in GraalVM for JDK 23. With older versions, use `-H:ThrowMissingRegistrationErrors=` instead.
+The `--exact-reachability-metadata` option was introduced in GraalVM for JDK 23. With older versions, use `-H:ThrowMissingRegistrationErrors=` instead. 
 ====
 
 - Rebuild the application:
@@ -338,10 +352,15 @@ The `--exact-reachability-metadata` option was introduced in GraalVM for JDK 23.
 
 [source,bash, role="multi-language-sample"]
 ----
-./target/yourApp -XX:MissingRegistrationReportingMode=Warn
+./target/myApp -XX:MissingRegistrationReportingMode=Warn
 ----
 
-- If there is any missing metadata printed to the console, **add it to the configuration file manually**, as described https://www.graalvm.org/reference-manual/native-image/metadata/#specifying-metadata-with-json[here], or **collect it automatically using the Tracing agent**.
+[NOTE]
+====
+With GraalVM versions older than JDK 23, pass `-H:MissingRegistrationReportingMode=Warn` at build time instead.
+====
+
+- If there is any missing metadata printed to the console, **add it to the configuration file manually**, as described https://www.graalvm.org/latest/reference-manual/native-image/metadata/#specifying-metadata-with-json[here], or **collect it automatically using the Tracing agent**.
 (See next.) 
 
 - Rebuild your native image and test again.
@@ -390,7 +409,6 @@ Step 1: **Enable the agent** by setting `<agent>` to `true` in the `native` prof
 </configuration>
 ----
 From that point on, commands you execute will run with the agent attached.
-By default, the agent creates the metadata in the _target/native/agent-output_ directory.
 
 Step 2: **Copy the generated metadata** from the default location, _target/native/agent-output_, to the resources directory, for example, _resources/META-INF/native-image_.
 Native Image automatically uses the metadata from this location.
@@ -424,7 +442,7 @@ Step 3: Now that the `metadataCopy` task is configured, **run the agent to colle
 
 [source,bash,subs="verbatim,attributes", role="multi-language-sample"]
 ----
-./mvnw -Pnative -Dagent=true test native:metadata-copy
+./mvnw -Pnative test native:metadata-copy
 ----
 
 Step 4: Finally, proceed without the agent and **build the native image with the metadata**.