docs: fix Tip typo and broken sample-scenario link in service-hijacking

[StrikerEureka34]

Documentation Update

Related Feature:

N/A - this is a standalone documentation fix on the existing service-hijacking
scenario page (a typo and a broken internal link).

Changes:

Two small fixes on the service-hijacking scenario docs:

• Krkn-hub "Tip" callout typo: ecause → Because.
• Broken "sample scenario file" link in the Krkn-hub and Krknctl tabs. It originally pointed to a non-existent service-hijacking-scenarios-krkn.md and rendered as a dead .md link.

What changed after the recent commit:-

• That was first patched to an on-page #sample-scenario anchor, but each tab renders as a separate hidden pane (Docsy tabpane), so the anchor still couldn't activate the Krkn tab from the Krkn-hub or Krknctl tab, and the target content stayed hidden.
• The link now just points readers to the Krkn tab by name, where the "Sample Scenario" section actually lives.

[netlify]

✅ Deploy Preview for krkn-chaos ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	e8bd381
🔍 Latest deploy log	https://app.netlify.com/projects/krkn-chaos/deploys/6a54aa220c1c710008f68171
😎 Deploy Preview	https://deploy-preview-536--krkn-chaos.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[qodo-code-review]

PR Summary by Qodo

Docs: fix typo and sample-scenario link in service-hijacking docs
📝 Documentation 🕐 Less than 5 minutes

Description

• Fix typo in krkn-hub “Tip” callout for service-hijacking scenario.
• Repair broken “sample scenario file” link in krkn-hub and krknctl tabs.

High-Level Assessment

The following are alternative approaches to this PR:

1. Use Hugo/MkDocs ref-style link helpers (e.g., relref/ref)

• ➕ Avoids fragile hardcoded paths/filenames when docs are moved/renamed
• ➕ Typically validated by the docs build pipeline (depending on tooling)
• ➖ May require adopting/standardizing link helper usage across docs
• ➖ Still needs correct anchor/heading targeting to avoid drift

2. Restore/create the previously linked file path

• ➕ Keeps the original link structure intact
• ➕ Can be useful if multiple pages were intended to share that sample
• ➖ Adds/maintains an extra doc artifact solely to satisfy a link
• ➖ Higher ongoing maintenance than linking to the canonical section

Recommendation: The PR’s approach (linking directly to the on-page #sample-scenario anchor) is the most maintainable for a single canonical example. If the docs toolchain supports it, consider using ref/relref-style helpers for cross-page links to reduce future breakage when pages move.

Files changed (2) +3 / -3

Documentation (2) +3 / -3

_tab-krkn-hub.mdFix Tip callout typo and point sample link to on-page anchor +2/-2

Fix Tip callout typo and point sample link to on-page anchor

• Corrects a typo in the “Tip” alert text ("ecause" → "Because"). Updates the sample scenario link to target the local “Sample Scenario” section via #sample-scenario instead of a non-existent markdown file.

content/en/docs/scenarios/service-hijacking-scenario/_tab-krkn-hub.md

_tab-krknctl.mdFix broken sample scenario link to use #sample-scenario +1/-1

Fix broken sample scenario link to use #sample-scenario

• Updates the “sample scenario file” link to point to the on-page #sample-scenario anchor rather than a missing service-hijacking-scenarios-krkn.md file.

content/en/docs/scenarios/service-hijacking-scenario/_tab-krknctl.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 24 rules

1. Hub sample link hidden ✓ Resolved 🐞 Bug ≡ Correctness

Description

_tab-krkn-hub.md and _tab-krknctl.md now link to #sample-scenario, but the only `Sample
Scenario` heading is inside the Krkn tab pane, so clicking those links from the Krkn-hub or Krknctl
tabs won’t activate the Krkn tab and the target content may remain hidden.

Code

content/en/docs/scenarios/service-hijacking-scenario/_tab-krkn-hub.md[67]

+A sample scenario file can be found [here](#sample-scenario), you'll need to customize it based on your wanted response codes for API calls

Evidence

Both the Krkn-hub and Krknctl tab content include links to #sample-scenario, but the `Sample
Scenario heading (### Sample Scenario) is defined only in the Krkn tab file (_tab-krkn.md`) and
is rendered inside the Krkn tab pane via _index.md. Because the site’s tab activation JavaScript
only switches tabs when the URL hash matches #tab-*/#tabpane-*, navigating to #sample-scenario
does not trigger a tab change, leaving the referenced section potentially unreachable/hidden when
clicked from non-Krkn tabs.

content/en/docs/scenarios/service-hijacking-scenario/_tab-krkn-hub.md[62-69]
content/en/docs/scenarios/service-hijacking-scenario/_tab-krkn.md[1-6]
content/en/docs/scenarios/service-hijacking-scenario/_index.md[44-58]
layouts/partials/hooks/body-end.html[4-46]
content/en/docs/scenarios/service-hijacking-scenario/_tab-krknctl.md[9-17]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The Krkn-hub and Krknctl tabs link to `#sample-scenario`, but the `Sample Scenario` section exists under the Krkn tab content; since tab switching is hash-driven only for `#tab-*`/`#tabpane-*` patterns, clicking these links from other tabs won’t activate the Krkn tab and users may not be taken to visible content.

## Issue Context
The service-hijacking scenario page is rendered as a tabpane with three tabs (Krkn / Krkn-hub / Krknctl). The `Sample Scenario` heading lives in `_tab-krkn.md` (rendered within the Krkn tab pane via `_index.md`), while the links to `#sample-scenario` are present in `_tab-krkn-hub.md` and `_tab-krknctl.md`.

## Fix Focus Areas
- content/en/docs/scenarios/service-hijacking-scenario/_tab-krkn-hub.md[67-67]
- content/en/docs/scenarios/service-hijacking-scenario/_tab-krknctl.md[15-15]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[StrikerEureka34]

Addressed the bug, can this be reviewed whenever you have a moment.
Thanks! @paigerube14 @ddjain

Note:- Please check the updated issue description for more details.

[github-actions]

Hi @StrikerEureka34! 👋 One or more commits in this PR are missing a Signed-off-by line, which is required by our DCO policy.

Unsigned commits:

• e8bd381: Merge branch 'main' into fix/service-hijacking-docs

To fix, rebase and sign off all commits:

git rebase HEAD~1 --signoff
git push --force-with-lease

Or, to sign off every commit in this PR at once:

git rebase origin/main --signoff
git push --force-with-lease

Tip: Add -s to future git commit commands (e.g. git commit -s -m "...") to sign off automatically.

Note: Please make sure your PR contains only 1 commit before signing off. If you have multiple commits, squash them first:

git checkout <my-working-branch>
git rebase -i HEAD~<num_of_commits_to_merge>
   -OR-
git rebase -i <commit_id_of_first_change_commit>

In the interactive rebase screen, set the first commit to pick and all others to squash. Then push your rebased commits:

git push origin <my-working-branch> --force-with-lease

See the Squash Commits guide for more details.

The needs-dco label and this comment will be removed automatically once all commits are signed off.

[ddjain]

/LGTM

[ddjain]

can you fix the CI ?

[StrikerEureka34]

can you fix the CI ?

I didn't get which one are you referring to.
CI for the DCO?

[ddjain]

Yes, CI for the DCO. I think you need to squash all commit and push forcefully.

[paigerube14]

instead of taking out this link would be good to fix the link to point to here or say see krkn page