Rename the "Configuration" and "Usage" top-level menu items

[inteon]

Based on what was proposed in #1260

[inteon]

/approve

[netlify]

✅ Deploy Preview for cert-manager-website ready!

Name	Link
🔨 Latest commit	10c7a76
🔍 Latest deploy log	https://app.netlify.com/sites/cert-manager-website/deploys/64f88eaaaf45b700080dfa3f
😎 Deploy Preview	https://deploy-preview-1282--cert-manager-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[wallrj]

I personally still prefer "Issuing Certificates",
but if you're going to use "Requesting Certificates", then that should also be the title of the Overview / Introduction page for that section:

• https://deploy-preview-1282--cert-manager-website.netlify.app/docs/usage/

And ideally, the URL path segment should also change.

[inteon]

I personally still prefer "Issuing Certificates", but if you're going to use "Requesting Certificates", then that should also be the title of the Overview / Introduction page for that section:

• https://deploy-preview-1282--cert-manager-website.netlify.app/docs/usage/

And ideally, the URL path segment should also change.

I did not change the URL, because I think it this is the easiest way to not break any links.

[inteon]

@wallrj I updated the content of those pages (see https://deploy-preview-1282--cert-manager-website.netlify.app/docs/usage/)

[wallrj]

Ok. As we discussed this morning, merging this will leave the website in an inconsistent state where the section called "Requesting Certificates" contains documents about prometheus metrics.
How about we merge this and the followup PR into a feature branch.
Then the feature branch preview can be presented in #cert-manager-dev for feedback before we make it live.

/lgtm
/hold in case you want to merge this into a feature branch

[jetstack-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: inteon, wallrj

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [inteon,wallrj]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[inteon]

I think it's not too disruptive, I fear that having a feature branch will just complicate things a lot (given that we might want to make more additional changes on master too).
/unhold