I would also be interested in re-writing text (Unless, of course, Whiteknight gets the position) I am a native English speaker, and used to do something similar for Japanese speakers in a language exchange (I help fix their English, they fix my Japanese).
I suppose for an example of my work you could see the amazon gift codes I'm selling in my signature.
NOTE: Some of these are probably not exactly worth a bounty, but still a good idea to change, I may post more after my account is verified.
Something I notice quite a bit recently, is the lack of liquid layouts, my screen isn't that small, but I get some cut off for some reason:
[...]
Whiteknight already agreed to help, but I will keep you in mind in case I need advice from multiple people.I suppose for an example of my work you could see the amazon gift codes I'm selling in my signature.
NOTE: Some of these are probably not exactly worth a bounty, but still a good idea to change, I may post more after my account is verified.
Something I notice quite a bit recently, is the lack of liquid layouts, my screen isn't that small, but I get some cut off for some reason:
[...]
Concerning the cut offs: Can you tell me what your screen resolution is?
Thanks for the problems reported. These things will be fixed with the next update.
Sent 0.025 BTC to 1AKtor49AFFHF8kVH4SAgd23eTPVy91iDB
Not sure how serious this is, but it looks like your bitcoind is listening on port 8333 (default) for incoming Bitcoin-esque connections. It's said that it's much easier to double spend when someone connects directly to your node and another at the same time.
On my DNS tunnel service, I have the daemon setup like this, to only connect out: bitcoind -noupnp -par=1 -daemon -nolisten. Granted, I'm not quite sure how relevant this for your environment. Not sure why you have portmapper open or port 41689, either.
Let me know what you think. Best of luck with the service!
Since, we do not accept 0-conf transactions there should be no big problems with double spending.On my DNS tunnel service, I have the daemon setup like this, to only connect out: bitcoind -noupnp -par=1 -daemon -nolisten. Granted, I'm not quite sure how relevant this for your environment. Not sure why you have portmapper open or port 41689, either.
Let me know what you think. Best of luck with the service!
The open portmapper port is indeed strange and I've contacted the support who told me that this was part of their default configuration upon server setup.
Nevertheless, the port is now closed.
There is Mater Key at the registration form. Looking at the JavaScript code I can see that validation will fail if key is exactly equal to 10000 or to 99999. But these values can be generated by the random generator. So the code should be changed to the following:
Will be fixed in the next update. Since this statistically only causes a small bug in every 4500th registration I hope you are okay if I don't pay a reward for this. 
At OP,
Not really a big deal, but when I entered some invalid characters I got greeted by a blank page with a red box with an error message, but when done to this URL, the error message appears ontop of the normal page, with no footer.
http://i.imgur.com/OFnkrKN.png
Not really a big deal, but when I entered some invalid characters I got greeted by a blank page with a red box with an error message, but when done to this URL, the error message appears ontop of the normal page, with no footer.
http://i.imgur.com/OFnkrKN.png
This is known and a result of our code structure and error handling. Since a "normal" user won't see such things there is no need to fix this, imho.
Thank you all!