Is it acceptable to mix how you address the reader in an instructional Wiki?
I'm working on a Wiki article that explains to new developers how our product life-cycle works.
Originally, my goal was to completely avoid the word "you" and use a more general description like "the developer".
The more I write though, the more useful I find the word "you."
And now I'm doing a mixture of both.
For instance, I may start a description of a new topic by saying the following:
This phase requires the developer to obtain a firm grasp on blah blah blah
Then, the first sentence of the next paragraph looks like this:
By the time you receive a Change Request, the A & D department will have a Functional Specification ready for review.
My general questions is this: Is it acceptable to jump between "the developer" and "you"?
When I read it, it seems to flow fine, but I would love some feedback on this approach.
This post was sourced from https://writers.stackexchange.com/q/3463. It is licensed under CC BY-SA 3.0.
2 answers
I think it's fine, because you as a company are creating an instruction manual which is going to be used by specific people. It's not literally a public Wikipedia.
To make it as clear as possible, start with the kind of disclaimer you sometimes see in plain-English contracts: "You, Your, Yourself, etc. refers to the developer."
When you're done writing, go back and search for any instance of "the developer" and see if changing it to "you" makes it read more smoothly or makes it clearer.
0 comment threads
It would be bad style to publish documentation that did that, but since a wiki is designed to be edited by many people who will each have their own quirks and don't usually consult house style guides, doing this on a wiki probably won't raise eyebrows.
That said, you should go back and change those "the developer"s to "you"s as you can, to improve the readability.
The tech-writing circles I have contact with overwhelmingly prefer "you" to "the (user, developer, etc)" when speaking to the reader. This also allows you to more easily write to the developer about his users without ending up with constructs like "the developer should (do something) to allow the users to (do something else)".
0 comment threads
0 comment threads