docs: fix broken WAF link in the scheduler page#57
Merged
Conversation
scheduler.md linked the WAF zone as /networking/firewall/, which 404s — the page is at /networking/waf/ (content/networking/waf.md; its linkTitle is 'Firewall (WAF)', which is likely where the wrong slug came from). Repoint the link to the canonical URL. Verified against the content tree that /networking/firewall/ has no backing page and /networking/waf/ exists.
|
Preview deleted (PR closed). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
content/automation/scheduler.mdlinked the WAF zone as/networking/firewall/, which 404s — there is no such page. The firewall/WAF page lives at/networking/waf/(content/networking/waf.md; itslinkTitleis "Firewall (WAF)", which is likely where the wrongfirewallslug came from). Repointed the link to the canonical URL.Verification
content/networking/has nofirewall.md/firewall/_index.md, and thatwaf.md(→/networking/waf/) exists and is already a working link target used elsewhere.](/…));/networking/firewall/was the only broken one, and none remain after the fix.Docs only; link text and context unchanged.