feat: Update Security Monitoring section, fix NAP link #49
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.
Proposed changes
This pull request updates the Security Monitoring section to fit contemporary style standards: sentence case for titles, no gerunds, horizontal line breaks at the end of sections.
It also fixes the frontmatter for the section's pages to be uniform in order and parameters with newer pages, and adds explicit weights for page numbering.
The final change is to add a reference link to the right NAP V4 page: prior to the release of NAP V5 the link was valid, but was not automatically detected due to being a production URL.
Checklist
Before creating a PR, run through this checklist and mark each as complete.
I have read the contributing guidelines
I have signed the F5 Contributor License Agreement (CLA)
If applicable, I have added tests that prove my fix is effective or that my feature works
If applicable, I have checked that any relevant tests pass after adding my changes
I have updated any relevant documentation (
README.md
andCHANGELOG.md
)I have rebased my branch onto main
I will ensure my PR is targeting the main branch and pulling from my branch from my own fork
If the change involves:
<username>
in place of PIIIn these cases, the change will require at least two (2) approvals before merging