IP30 – April 26 (pm): Proofreading, and Confirmation for tomorrow




Good afternoon,

If you have time to check this out before or after class, visit http://bertc.com/recipes.htm for some unusual recipes. if you see one you like, you may save a copy or print one out, but don’t spend class time on it since tomorrow I’ve planned for a different activity.

NEWS: I have confirmed with YouthBuild that they will be working with us tomorrow morning on disassembling and reassembling computers.

Please continue the profreading this afternoon. I have received 2 grade folders that have been checked through, and found only one missed error in one, and two in the other. At last check, Tauren was the champion proofreader for accuracy, with zero errors slipping past him.

Final Note: If your folder of recipes is done and all proofreaders have signed their names on the back, return it to Mr. Stinson and find more recipes that you can help proofread as the second, third or fourth proofreader.

Keep up the good work! Hmm. I wonder which most people feel is more difficult; proofreading your own work or proofreading someone else’s?

Create a free edublog to get your own comment avatar (and more!)

3 Responses to “IP30 – April 26 (pm): Proofreading, and Confirmation for tomorrow”

  1. proofreading your own work is much harder than proofreading someone elses work because you are more likely to miss your own mistakes. You know what you mean so you dont really scrutinize your work.

  2. I think it is easier to edit my own work. I know that is kind of weird, but I get frustrated when what I am reading could have been done better. When I go through my own work, I pick it apart again and again. I get frustrated and want to just redo it!!

  3. I think that proofreading your own work is alot harder because your most likley to miss your own mistake. I really don’t like proofreading anyways so i am likely to miss alot of mistakes.

Leave a Reply

*
To prove you're a person (not a spam script), type the security word shown in the picture.
Anti-Spam Image