And anyway, this isn't actually a wiki page. So it can have all kinds of story.
Yaaaaaaay! All done with the guide. Pretty much covered everything, I think. If there is anything I am missing, tell me!
Oh, Jaded, if you ever see this thread, this is an application to become part of the Wiki Team. Thanks for considering!
o_oOn final note: If you really want to be a wiki guide author (which I wouldn't recommend yet), you have to change your style. The wiki is supposed to be formal and informative, without useless information (sludge anyone?). Have a look here: Upcoming Community Wiki Involvement, especially "This is a technical wiki not a story-line guide. No anecdotal novels please."
If you want to be on the wiki team but don't want to stick with the guidelines, I suggest not asking to be part of the wiki team. Even without the story theme of your guides, they still lack content. For a bit of effort, anyone can just go around and find information on each machine, function, etc. You can always try out writing novels, but don't expect your guide to be a success just because you slap "official" or "guide" on it or try to make it look official. You're going to have to make a guide that's to the point, helpful, and worth-using. Sure you can always change your guides and improve them after the fact, but they're going to have to be good when they're on the wiki. If you add story and leave out content, somebody else is going to have to review every guide for you, and what's the point if said person could just write the guide instead? Sure I'm going to be "the bad guy" here, but I'm just saying that it's going to have to be better than this.