docs: update subrequest section

[dkleinF5]

Proposed changes

Checklist

Before sharing this pull request, I completed the following checklist:

• I read the Contributing guidelines
• My branch adheres to the Git conventions
• My content changes adhere to the F5 NGINX Documentation style guide
• If my changes involve potentially sensitive information¹, I have assessed the possible impact
• I have waited to ensure my changes pass tests, and addressed any discovered issues

Footnotes

1. Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

[ADubhlaoich]

Generally LGTM: please ensure your commit messages (in-branch or merge) adhere to our Git conventions as outlined in the checklist part of every PR, which expect Conventional Commits formatting.

[github-actions]

✅ Deploy Preview will be available once build job completes!

Name	Link
😎 Deploy Preview	https://frontdoor-test-docs.nginx.com/previews/docs/1510/

---

[ADubhlaoich]

LGTM still, but you should reconsider how you have changed the headings.

Heading level 4 does not generate in the table of contents, meaning that they require the user to scroll to find them.

I suggest removing the "Additional..." third level subheadings, and renaming the subrequest "Example" heading into a "General example" to ensure that the headings are uniformly consistent from that point on.

[y82]

Perhaps it's worth adding the slice module here as well.
It'd be also good to align the values in config examples

[ADubhlaoich]

LGTM: I can merge this.

[ADubhlaoich]

I just noticed you added more commits since yesterday.

It is very unclear to me when to review this PR because commits keep being added: I do not understand what the definition of done is meant to look like.