Peer Reviewing

Description

Once you have reviewed the peer review sample document in your reading as noted above, check out this crazy sample of a confusing piece of technical writing:  http://www.impactonthenet.com/rg-m1.html  (Links to an external site.)    This is the document you’ll be offering peer feedback on (the warhead storage instructions).   Use the format of the peer review sample (making up any information that you don’t have, such as names and emails). You’ll notice that the document you’ll be offering suggestions about is short–don’t let that stop you! Remember that you can not only point out areas for improvement, but also note why those areas are problematic and how they can be improved.  Your document should:  Be 12 pt, Times New Roman font, 1-inch margins, double spaced.  Include 3-4 suggestions, each a paragraph in length (with a minimum of 3 sentences per paragraph).  Reference:  Impact Technical Publications. (n.d.). Who’s on top? The Rogues’ Gallery of Bad Technical Publications. Retrieved from http://www.impactonthenet.com/gallery.html  (Links to an external site.)   This is a sample of how it should look. From hcexres36:05 1999 -0600 Date: Sun, 5 Dec 1999 15:36:04 -0600 (EST) From: “David A. McMurrey” <hcexres@io.com> To: julie@colltech.com Cc: xgraphic_team Subject: Review of your section of xgraphics HTML project Content-Type: TEXT/PLAIN; charset=US-ASCII   Julie, your section of the guide is super! You’ve done several things the rest of the team ought to incorporate in their sections.   1. But I do find places where it feels like there is too much text — for example, in “Using Gravity and Snap.” It’s not a major problem but I’d be looking to see if I could cut a few lines from the longer paragraphs without sacrificing detail.   2. Your labels for the screen captures are really nice. You’ll have to show the rest of the team how you do it.   3. You leave out generic buttons on several pages — I think the group was in agreement that *all* pages would have them at the bottom.   4. I notice in some areas you use italics for some interface elements, bold for others. Our style guide states that we wanted bold for any screen button or similar element that makes something happen when you click it. Maybe we need to discuss the distinction you are thinking about here at our next meeting.