merge https-status-code-500 and 500-error and rename

[Jimmy_Carter]

Hi,

500 and 500-error, which are both very unclear names.

Is there any reason not to merge both tags into a new http-status-code-500 tag?

Thank you in advance.

[Rachel S]

Merging 500 and 500-error into http-status-code-500 makes sense for clarity and consistency. The 403 tag follows the http-status-code-[code] naming convention, so applying the same to 500 ensures uniformity.

Since both 500 and 500-error refer to HTTP status code 500 (Internal Server Error), consolidating them into http-status-code-500 would help avoid confusion and make tag usage clearer.

There’s no strong reason not to merge them, unless:

1. 500 or 500-error are being used for something unrelated (unlikely).
2. There’s an existing convention that allows shorter tags (but the 403 tag suggests otherwise).