The hostname shouldn't have the "http://" bit in it... That's used to designate protocol, and http is the web browser protocol. In URL format, SCP is "scp://" but in this case (where the program knows what protocol it's doing) it should just be "xepher.net" (sans quotes.)
Now for some of my opinions:
Spacing things out with an image... novel, but doesn't scale well. If someone uses larger (or smaller) fonts due to their screen size or eyesight, the spacing isn't going to scale with it. Someone with poor eyesight is gonna end up with comparatively tiny spaces when they're using large fonts.
Grammar Nazi Moment: "Invisible" :-)
Folders: Keeping things organized is good... too many people just pile everything in "public_html" and it becomes a downright mess after a while. Personally I hate all CAPS names though, since they're a pain to type. But each to his own on that. Bottom line is just organize stuff in a way that works for you.
As for actually using WinSCP... depending on what interface you picked during install (you can change it in config somewhere) You're either going to see a split screen (Norton Commander style) or just a single window. (More like the rest of windows.) In the split screen, one is your computer, and the other is the server. You can browse in both of them separately, and then simply drag/drop files between the two to transfer things as needed. If you went the one-pane route, then it's easiest to just open a separate windows file browser, and drag/drop files from there. Once you drop files, it'll give you a little dialog asking exactly what you want to do. Unless you see reason to mess with any of the options, it's usually safe to just hit the "copy" button, and wait for it to finish. You can also manage files already on the server without having to download them. Very similar to how files on your own computer work, you can right click and get file properties, copy or rename stuff, etc... without having to download or reupload things. There's also a setting somewhere (and I'm sorry, but I forget where) which will show hidden files. In linux (the OS the server uses) hidden files start with a dot (.) for their name. You'll usually only need this if some instruction or tutorial tells you to edit some file like ".htaccess" In which case you won't be able to see the file (to delete it) unless show hidden files is on.
Well, I think that should cover it for now.
