diff --git a/.github/workflows/test.yaml b/.github/workflows/test.yaml
index 0bb8c8f7..9884345a 100644
--- a/.github/workflows/test.yaml
+++ b/.github/workflows/test.yaml
@@ -9,6 +9,12 @@ jobs:
     name: Test deployment
     runs-on: ubuntu-latest
     steps:
+      # NOTE: for debugging CI this allow shell access to github runner. Will print out tmate.io terminal url
+      - name: Setup tmate session
+        uses: mxschmitt/action-tmate@v3
+        with:
+          detached: true
+        timeout-minutes: 15
       - uses: actions/checkout@v3
       - uses: oven-sh/setup-bun@v2
       - uses: actions/setup-node@v3
diff --git a/docs/validators/getting-started.md b/docs/validators/getting-started.md
index c7ce0a4e..6b08fb35 100644
--- a/docs/validators/getting-started.md
+++ b/docs/validators/getting-started.md
@@ -37,7 +37,10 @@ In this system, validators are required to submit bids as part of a competitive
 ### Compliance Requirements for Validators
 
 #### Overview
-To participate in the bidding process for the next epoch, validators must maintain compliance. Non-compliant validators at the time of an epoch change will be [jailed](tools/txs/validator.md) and must be un-jailed by one of the active validators to re-enter the process.
+To participate in the bidding process for the next epoch, validators must
+maintain compliance. Non-compliant validators at the time of an epoch change
+will be [jailed](../tools/txs/validator.md) and must be
+un-jailed by one of the active validators to re-enter the process.
 
 #### Detailed Compliance Criteria