diff --git a/docs/src/main/asciidoc/command-mode-reference.adoc b/docs/src/main/asciidoc/command-mode-reference.adoc
index dc07d4a7454bb..008f52916c069 100644
--- a/docs/src/main/asciidoc/command-mode-reference.adoc
+++ b/docs/src/main/asciidoc/command-mode-reference.adoc
@@ -25,9 +25,10 @@ First, we need to create a new Quarkus project with the following command:
 :create-app-artifact-id: command-mode-quickstart
 include::{includes}/devtools/create-app.adoc[]
 
-NOTE: By default, our tooling will include the RESTEasy extension. As it is not desired for a command mode application,
-you need to add `-no-code` for the CLI or `-DnoCode` for Maven. In the same way, if you use code.quarkus.io to generate a
-project, you need to go to *MORE OPTIONS -> Starter Code* and select *No* to avoid adding the RESTEasy extension.
+NOTE: The suggested project creation command lines disable the codestarts to avoid including a REST server. Similarly, if you use code.quarkus.io to generate a
+project, you need to go to *MORE OPTIONS -> Starter Code* and select *No* to avoid adding the RESTEasy Reactive extension.
+
+The RESTEasy Reactive extension is added automatically only if you ask for codestarts and you didn't specify any extensions.
 
 
 == Writing Command Mode Applications
@@ -213,7 +214,7 @@ public class HelloTest {
 
 ----
 
-Each test method must be annotated by `@Launch` to automatically start the application of have a `QuarkusMainLauncher`
+Each test method must be annotated with `@Launch` to automatically start the application of have a `QuarkusMainLauncher`
 parameter and manually launch the application.
 
 We can then extend this with an integration test that can be used to test the native executable or runnable jar: