To me, it looks better once changed as it matches the download list, however, I guess this is all personal preference - are bugs reviewed once people submit them?
Please could I have permissions added for the repo if you want me to commit this fix/preference?
When new coders volunteer, they post their changes for review via a patch file. We look through the patch file and see if it looks okay, then apply the patch for them.
After they have a few bug fixes under their belt, and it looks like they're getting the hang of it, w/o needing a lot of fixes to their patches, then we'll open the door and let them have write access to the source repo.
So hang in there, fix a few problems, and we'll see about getting you write access.
For future reference, I prefer that you mark your code changes so they can be tied to specific problems that you're fixing. For example, search for "grayman" in the source to see how I've done it for my changes. I find this invaluable if we later have a problem in a bit of code and need to talk to the person who made the change. (Also, in my case, it makes it easier for me to find all the scattered bits of changes I made a few years back to fix a particular problem.)