local/local-workflow.md

@@ -66,7 +66,7 @@ No local Lambda service needs to be running first, in our case:
      ~/Source/purpleteam-lambda `echo '<same-JSON-payload-as-above>' | sam local invoke -d 5858 --docker-network compose_pt-net provisionAppSlaves`
    * For `provisionSeleniumStandalones`:  
      ~/Source/purpleteam-lambda `echo '<same-JSON-payload-as-above>' | sam local invoke -d 5858 --docker-network compose_pt-net provisionSeleniumStandalones`
-3. [Debug](#debugging-1) in VSCode
+3. [Debug](#debugging) in VSCode
 4. Then check that conatiners are running as already discussed
 5. Bring them down again as already discussed
 
@@ -137,7 +137,7 @@ In Chromium, open `chrome://inspect` and click "inspect", which will drop you in
    * Debug (orchestrator or app-scanner. For this example we demo orchestrator, for app-scanner just swap the "orchestrator" with "app"):
      1. ~/Source/purpleteam-orchestrator `npm run dc-build-debug-orchestrator` (builds/rebuilds images after code changes)  
      2. ~/Source/purpleteam-orchestrator `npm run dc-up-debug-orchestrator`  
-        * Now you can attach to `purpleteam-orchestrator`, or `purpleteam-app-scanner` as discussed in the [Debugging](#debugging-1) section
+        * Now you can attach to `purpleteam-orchestrator`, or `purpleteam-app-scanner` as discussed in the [Debugging](#debugging) section
 <!---->
 5. Start cli: