Syntax and readme changes

Author: Ariouz

README.md

@@ -14,16 +14,13 @@ with an explicit and predictable workflow.
 ## Why GKit?
 
 Building native images with GraalVM is powerful but often painful:
-complex plugins, duplicated configuration, CI inconsistencies.
+complex plugins, duplicated configuration, CI inconsistencies, tons of build args.
 
 GKit focuses on:
-- **Developer Experience** – clear commands, no magic
+- **Developer Experience** – clear commands, detailed feedback
 - **Portable configuration** – one `gkit.yml`, reusable everywhere
 - **CI-friendly workflows** – explicit commands, dry-run support
 
-GKit does **not** replace Maven or Gradle.
-It orchestrates them.
-
 
 ## Features
 
@@ -60,6 +57,8 @@ build:
 
 nativeImage:
       output: target/my-app
+      buildArgs:
+        fallbackImage: false
 
 profiles:
   dev:
@@ -175,13 +174,6 @@ nativeImage:
 
 #### Notes:
 
-- **Boolean flags** (`fallbackImage: false`) will be converted to `--no-fallback` automatically.
-- **List arguments** (`initializeAtBuildTime: [foo, bar]`) will generate repeated flags:
-
-```bash
-  --initialize-at-build-time=foo --initialize-at-build-time=bar
-```
-
 - **Raw args** are passed **as-is** to native-image.
 
 - If a [profile](#Profiles) overrides a flag:

src/main/java/fr/ariouz/gkit/doctor/ConfigDoctorCheck.java

@@ -31,7 +31,7 @@ protected String getStatusMessage(DoctorStatus status) {
 		return switch (status) {
 			case ERROR -> "Failed to load config. Consider using gkit check-config [-p PROFILE] for details";
 			case WARNING -> "One or more native build args are invalid. Consider using gkit check-config [-p PROFILE] for details";
-			case SUCCESS -> "No error on base profile found. Consider using gkit check-config -p PROFILE for profile validation";
+			case SUCCESS -> "No error on base profile found. Consider using gkit check-config [-p PROFILE] for profile validation";
 		};
 	}
 }