Update product titles in one.json

[Kkresge]

#228

Proposed changes

Problem: Inconsistent case used for the product titled "NGINX One Console"

Solution: Changed all instances of "NGINX One console" to "NGINX One Console"

Testing: None

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

Closes #228

Checklist

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

• I have read the contributing guidelines
• I have signed the F5 Contributor License Agreement (CLA)
• I have rebased my branch onto main
• I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
• I have ensured that the commit messages adhere to Conventional Commits
• I have ensured that documentation content adheres to the style guide
• If the change involves potentially sensitive changes¹, 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

Footnotes

1. Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩

[github-actions]

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

[Kkresge]

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

[mjang]

Hi @Kkresge

Thank you for your contribution!

You've found an interesting file, a key to API documentation. There are a few things I should explain about it. Short version, to fix these titles, I'm going to have to change some "YAML" files from a different repository that's not open to the public. (I'm moving this to "draft" to prevent accidental merge.)

If you have some time while we're at the conference, I'd love to show you how we "build" this one.json file from other content -- and how that builds API docs. But you might already know that, as it takes quite the detective to find this file!

If you don't see me, DM me -- I'm @mikejang on the Write the Docs Slack

Note: as you can see, I've created issue #523 from your contribution. We will address it!