Update NGINX Agent and NGINX One console in Docs

[lucYang55]

Proposed changes

Problem: I addressed issue 228 where the documentation needed updating to adhere to new style guidelines. This involved phrases like NGINX Agent (not "the NGINX Agent") and "NGINX One Console" v "NGINX One console".

Solution: I updated the documents according to the format that was requested for the issue. I updated several instances with the new style convention.

Testing: This was just documentation, so I made sure the documentation format stayed the same.

If this PR addresses an issue on GitHub, ensure that you link to it here:

#228

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

• [ x] I have read the contributing guidelines
• [ x] I have signed the F5 Contributor License Agreement (CLA)
• [x ] I have rebased my branch onto main
• [ x] I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
• [ x] I have ensured that the commit messages adhere to Conventional Commits
• [ x] I have ensured that documentation content adheres to the style guide
• If the change involves potentially sensitive changes[^1], I have assessed the possible impact
• If applicable, I have added tests that prove my fix is effective or that my feature works
• I have ensured that existing tests pass after adding my changes
• If applicable, I have updated README.md and CHANGELOG.md

[github-actions]

✅ All required contributors have signed the F5 CLA for this PR. Thank you!
_{Posted by the CLA Assistant Lite bot.}

[lucYang55]

I have hereby read the F5 CLA and agree to its terms

[JTorreG]

'the' should only be removed when referring to a product. Product components should keep the determiner:

Correct: NGINX Agent; the NGINX Agent service
Incorrect: The NGINX Agent; NGINX Agent service

[mjang]

Hi @lucYang55

• Thanks so much for your work on this!
• Tip: If you want to accept a group of these suggestions,
  • Scroll to the top of the page
  • Select the Files changed tab
  • With the "Suggested changes" that you agree with, select Add suggestion to batch
  • When you're done, select Commit suggestions. This process can commit dozens of changes, simultaneously!
• We're not perfect. If you think our style guide did not give clear instructions, you're welcome to suggest changes in a separate pull request

[mjang]

@lucYang55 thank you for your contribution and work on this!

May I ask -- what prompted your interest? if I understand your GitHub profile, you're also from Oregon State. You're welcome to respond here, to mi.jang@f5.com, or to DM my LinkedIn at https://www.linkedin.com/in/mijang/