From fd7e6081c19ec6fd17b6dc3611de0605d54dc613 Mon Sep 17 00:00:00 2001 From: Sajad Torkamani Date: Thu, 26 Jun 2025 18:36:59 +0100 Subject: [PATCH] docs: improve wording Signed-off-by: Sajad Torkamani --- apps/site/pages/en/learn/getting-started/debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/site/pages/en/learn/getting-started/debugging.md b/apps/site/pages/en/learn/getting-started/debugging.md index e4603e03606be..6b9504dca8945 100644 --- a/apps/site/pages/en/learn/getting-started/debugging.md +++ b/apps/site/pages/en/learn/getting-started/debugging.md @@ -38,7 +38,7 @@ restriction and will be able to run arbitrary code. By default `node --inspect` binds to 127.0.0.1. You explicitly need to provide a public IP address or 0.0.0.0, etc., if you intend to allow external connections to the debugger. Doing so may expose you to a potentially significant security -threat. We suggest you ensure appropriate firewalls and access controls in place +threat. We suggest you ensure appropriate firewalls and access controls are in place to prevent a security exposure. See the section on '[Enabling remote debugging scenarios](#enabling-remote-debugging-scenarios)' on some advice on how