From 6acc8ca43a82f56f4b61ef04dd42e84afa06b207 Mon Sep 17 00:00:00 2001
From: O1LER <44237025+O1LER@users.noreply.github.com>
Date: Wed, 5 Feb 2025 21:17:44 +0100
Subject: [PATCH] Fix no-launch argument

---
 docs/en/game/getting-started.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/game/getting-started.md b/docs/en/game/getting-started.md
index c95db2a2..2d3fc403 100644
--- a/docs/en/game/getting-started.md
+++ b/docs/en/game/getting-started.md
@@ -56,7 +56,7 @@ The native linux BeamMP-Launcher will start and use native linux BeamNG.drive
 
 Should you want to use the native linux BeamMP-Launcher together with BeamNG.drive running through Proton, you can do so:
 
-Run the BeamMP-Launcher using the argument ` -no-launch` (This will prevent the Launcher from starting native linux BeamNG.drive). Further information about launcher arguments can be found in the [Development Environment Setup](../guides/beammp-dev/beammp-dev.md)
+Run the BeamMP-Launcher using the argument ` --no-launch` (This will prevent the Launcher from starting native linux BeamNG.drive). Further information about launcher arguments can be found in the [Development Environment Setup](../guides/beammp-dev/beammp-dev.md)
 
 Change the userfolder location of Proton-BeamNG.drive to the location of Linux-BeamNG.drive (since the native linux BeamMP-Launcher currently only writes into the Linux-BeamNG.drive userfolder)