From 6dd97e8634439eaa664f458701f639e5ca7d4ebf Mon Sep 17 00:00:00 2001
From: terrywhitney <100789884+terrywhitney@users.noreply.github.com>
Date: Wed, 26 Feb 2025 15:18:52 -0500
Subject: [PATCH] Update page.md

corrected format settings for "config values, added consistent header structure, removed redundant blank lines
---
 .../page.md                                   | 110 +++++++++---------
 1 file changed, 52 insertions(+), 58 deletions(-)

diff --git a/docs/04.guides/13.Various/51.lucee-step-debugger-installation-guide/page.md b/docs/04.guides/13.Various/51.lucee-step-debugger-installation-guide/page.md
index cabc4d585..18c500e56 100644
--- a/docs/04.guides/13.Various/51.lucee-step-debugger-installation-guide/page.md
+++ b/docs/04.guides/13.Various/51.lucee-step-debugger-installation-guide/page.md
@@ -122,72 +122,66 @@ Get the `Luceedebug Visual Studio Code Extension` by installing the extension fr
 
 At this moment, Lucee is already running providing your CFML generated content at `http://localhost:8888`, and the **Luceedebug.jar** is listening at localhost:9999, but the Visual Studio Code Editor doesn't know about it yet. The last step is to link the code base at `D:\luceedebug_example\lucee-express-5.4.6.9/webapps/ROOT` to the Visual Studio Code Luceedebug Extension and configure it to use the remote endpoint at localhost:9999 (Luceedebug.jar). This can typically be done within the workspace setting file. To achieve that, create a file named `lucee_debug_example.code-workspace` at `D:\luceedebug_example\lucee_debug_example.code-workspace` with the following content:
 
-On Windows:
-
-```json
-{
-	"folders": [
-		{
-			"path": "D:\\luceedebug_example\\lucee-express-5.4.6.9\\webapps\\ROOT"
-		}
-	],
-	"launch": {
-		"version": "0.2.0",
-		"configurations": [
+## Configuration for Lucee Debugging
 
+### On Windows:
 
-			{
-				"type": "cfml",
-				"request": "attach",
-				"name": "Attach to Luceedebug Backend",
-				"hostName": "localhost",
-				"port": 10000,
-				 "pathTransforms": []
-				
-			}
-		]
-	},
-	"settings": {
-		"files.exclude": {
-			"**/WEB-INF": true
-		}
-	}
+```
+{
+  "folders": [
+    {
+      "path": "D:\\luceedebug_example\\lucee-express-5.4.6.9\\webapps\\ROOT"
+    }
+  ],
+  "launch": {
+    "version": "0.2.0",
+    "configurations": [
+      {
+        "type": "cfml",
+        "request": "attach",
+        "name": "Attach to Lucee Debug Backend",
+        "hostName": "localhost",
+        "port": 10000,
+        "pathTransforms": []
+      }
+    ]
+  },
+  "settings": {
+    "files.exclude": {
+      "**/WEB-INF": true
+    }
+  }
 }
 ```
 
-On Linux/MacOs:
-
-```json
+### On Linux/MacOs:
+```
 {
-	"folders": [
-		{
-			"path": "/opt/luceedebug_example/lucee-express-5.4.6.9/webapps/ROOT"
-		}
-	],
-	"launch": {
-		"version": "0.2.0",
-		"configurations": [
-
-
-			{
-				"type": "cfml",
-				"request": "attach",
-				"name": "Attach to Luceedebug Backend",
-				"hostName": "localhost",
-				"port": 10000,
-				 "pathTransforms": []
-				
-			}
-		]
-	},
-	"settings": {
-		"files.exclude": {
-			"**/WEB-INF": true
-		}
-	}
+  "folders": [
+    {
+      "path": "/opt/luceedebug_example/lucee-express-5.4.6.9/webapps/ROOT"
+    }
+  ],
+  "launch": {
+    "version": "0.2.0",
+    "configurations": [
+      {
+        "type": "cfml",
+        "request": "attach",
+        "name": "Attach to Lucee Debug Backend",
+        "hostName": "localhost",
+        "port": 10000,
+        "pathTransforms": []
+      }
+    ]
+  },
+  "settings": {
+    "files.exclude": {
+      "**/WEB-INF": true
+    }
+  }
 }
 ```
-
 #### Step 7: Running everything all together
 
 While the Tomcat Lucee instance is already running at `http://localhost:8888` (test it by browsing to it) and the Java Agent with luceedebug.jar is listening on localhost:9999, you can open the workspace by double-clicking the file at `D:\luceedebug_example\lucee_debug_example.code-workspace`. This should open your Visual Studio Code with Lucee's default application at `D:\luceedebug_example\lucee-express-5.4.6.9\webapps\ROOT\index.cfm`.