More justification for verify key status codes

[WilfredAlmeida]

Type of documentation issue

Other

Describe the problem and the proposed solution

For verify key, it's clear that these are key statuses & the http status will be 200, however, given similar names, its easy to get confused. Maybe a note at the bottom saying "These are key statuses, HTTP status will be 200" can be added. Just incase someone gets confused.

[linear]

ENG-446 More justification for verify key status codes

[Pranavtej]

/assign

[oss-gg]

Assigned to @Pranavtej! Please open a draft PR linking this issue within 48h ⚠️ If we can't detect a PR from you linking this issue in 48h, you'll be unassigned automatically 🕹️ Excited to have you ship this 🚀

[Pranavtej]

@WilfredAlmeida @chronark
can you please review this issue and validate?

[nilaygit-10721]

/assign

[oss-gg]

This issue is already assigned to another person. Please find more issues here.

[oss-gg]

This issue is already assigned to another person. Please find more issues here.

[parthmodi152]

/assign

[oss-gg]

This issue is already assigned to another person. Please find more issues here.

[WilfredAlmeida]

This isssue is a no-brainer fix that has already been implemented. I'm closing this now because I'm annoyed with the emails of people trying to get assigned an obviously assigned and fixed issue for the sake of point farming

Please create a new issue if the context if this issue needs to be revisited. Thank You!