So just a bit of whining, pay no mind.

So 3 years ago, June 2012, I opened a ticket to let FA know "Hey, you've got a spelling mistake. It's spelled rhinoceros, not rhinocerus. Can you fix the species pull-down?" It was closed with a comment of "forwarding this to the development team" but was not fixed.

In January of this year, I re-opened the same ticket. Was told "Typos such as this should be fixed with the Phoenix UI update." "When is the scheduled Phoenix UI update?" "There is no date set". And then the ticket was closed again.

So I waited 3 months instead of three years to try again this time.
Can this just be fixed with an SQL update query? "UPDATE sometable SET somecolumn='rhinoceros' WHERE somecolumn='rhinocerus';"? with sometable and somecolumn being the appropriate table & column names?
Apparently, that bit in January was "addressed" with a "ruling" and "escalation" per FA Code of Conduct 1.14
1.14 - Do not abuse the Trouble Ticket system. This includes opening multiple tickets for the same issue and re-opening tickets after a ruling was made by an Administrator after escalation
Why? Because I was told
It will be fixed with the phoenix update as mentioned before. Please don't reopen tickets that have been addressed as it violates Fur Affinity's Code of Conduct.
Of course, this post at all probably counts as violation, per Code of Conduct 1.5:
1.5 - Do not abuse site staff. ... Please be respectful to staff ... If you have an issue with a member of site staff or a decision someone made, please escalate the issue
Further, I think that previous message may count as a "warning notice", so this one might trigger a "strike notice". It would certainly be amusing if it were.