diff --git a/README.md b/README.md
index 9890a83..6493c06 100644
--- a/README.md
+++ b/README.md
@@ -178,7 +178,7 @@ the launcher could be named `fizzbuzz.exe`.
 
 The configurator (2) is named `jaunch-<os>-<arch>.exe`, and placed in the `jaunch`
 subdirectory of your application. Examples: for ARM64 Linux it would be named
-`jaunch/jaunch-linux-aarch64`, whereas for x86-64 Windows it would be named
+`jaunch/jaunch-linux-arm64`, whereas for x86-64 Windows it would be named
 `jaunch/jaunch-windows-x64.exe`. The reason for the `<os>-<arch>` suffix is so that
 portable applications can ship with all needed jaunch configurator executables in
 the same `jaunch` folder, without any name clashes.
diff --git a/src/c/jaunch.c b/src/c/jaunch.c
index e3979c7..172eb6d 100644
--- a/src/c/jaunch.c
+++ b/src/c/jaunch.c
@@ -55,7 +55,7 @@ static int launch_jvm(
 #endif
 
 #ifdef __aarch64__
-#define OS_ARCH "aarch64"
+#define OS_ARCH "arm64"
 #endif
 
 // List of places to search for the jaunch configurator executable.