trents, at this stage, I like your approach, your clarifications.
Since we are not dealing with newspaper print, what I had in mind initially was an introduction which would easily link to the useful background info for the less experienced and easily link straight into the steps of the creation with not too much additional info so that way both kinds of audiences would be addressed.
Personally, I don't like to have a bunch of links I have to follow in order to get the info I need. I'd rather have it right there.
In other words, the less experienced can be frustrated with the lack of explanation. Given a choice I _always_ prefer your approach trents, making sure to hand-hold the less experienced, it's easy to forget how much they *don't know* and how easy it is for them to be confused.
Also in other words, the more experienced can be frustrated by not getting to the point, they have no desire to read any additional info and want to just have a quick short list of actual nitty-gritty, they know exactly what to do with quick instructions...
So right now, I thought I would give TechWizard time to see what he comes up with for the IT pros.
Then somehow incorporate both in a single article.
The typos do not concern me, they can easily be corrected, polishing the article would come after the big picture is clear. I am confident we can adjust things to address both inexperienced home users as well as IT Pros.
Unless the typos happen in a command string. I also like what I write to come across in a professional way and not like someone with no education. But I myself am a terrible proofreader. I'm constantly amazed at how much I miss when I proofread my own stuff. I miss things because I know what I wanted to say and I see it that way.