From 191d3ac1c585f9fb53473e8687c719c47f198ac0 Mon Sep 17 00:00:00 2001
From: Protogen187 <162638343+Protogen187@users.noreply.github.com>
Date: Mon, 27 Jan 2025 19:01:09 +0100
Subject: [PATCH] Update docs/en/FAQ/How-to-check-for-CGNAT.md

Co-authored-by: O1LER <44237025+O1LER@users.noreply.github.com>
---
 docs/en/FAQ/How-to-check-for-CGNAT.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/FAQ/How-to-check-for-CGNAT.md b/docs/en/FAQ/How-to-check-for-CGNAT.md
index ed7ccdfc..ac728e91 100644
--- a/docs/en/FAQ/How-to-check-for-CGNAT.md
+++ b/docs/en/FAQ/How-to-check-for-CGNAT.md
@@ -9,7 +9,7 @@ If you have connection problems and you are using a Hosting-Service, contact the
 # How to check for CGNAT?
 
 ## Method 1:
-Open a cmd, run ``tracert -4 beammp.com``. This will output a series of network hops. Wait for the operation to finish (may take up to 30 hops). Check the first few IP addresses after the IP of your Router/Modem/Gateway.
+Open a command prompt, run ``tracert -4 beammp.com``. This will output a series of network hops. Wait for the operation to finish (may take up to 30 hops). Check the first few IP addresses after the IP of your Router/Modem/Gateway.
 If multiple IP addresses within the range of 100.64.x.x-100.127.x.x appear after the Gateway/Modem/Router IP (top IP), you are most likely behind a CGNAT.
 
 If multiple IP addresses within the range of ``100.64.x.x``-``100.127.x.x`` or ``10.xx.xx.xx`` appear after the first hop, you are most likely behind a CGNAT.