Calm down.
Everyone makes mistakes.
I never!
j/k
And then again, I'm getting back to my QA questions I put a while ago.
I understand this application is in an incipient stage, and you are trying to make it dynamic, make changes on the fly and such.
However, it is much better, and definitely recommended to go through a regular development cycle, set up a 1-2 week iteration, followed up by a QA stage (of course you will need a dev platform, then a QA platform, and only after that is the production one). As it stands, seeing how quick some things manage to get fixed, it looks like there process is not organized enough, and it's very dangerous to make changes without a proper QA approach. I am under the impression that the changes are being directly made in production environment, which can backfire...
I say this because in several cases I saw changes done in few hours after being reported. While that seems good, it is rather dangerous. Those bugs were indeed bugs, but they were not critical, nor blockers. Putting them in a regular life cycle would protect the application's health much better than having a display issue fixed right away.
Enough ranting, but hope you understand my point.
Feel free to contact me if you want further professional expertise ;)