Proofreading what you write is not easy. Proofreading is not editing. Proofreading is not reading for meaning. Proofreading is focusing on the mechanics, not the content. The goal of proofreading is to find and correct blatant errors…
Sourced through Scoop.it from: www.linkedin.com
If you have access to LinkedIn, I highly encourage you to read Yvonne Kucher’s essay about how to proofread your technical writing. I’ve met Yvonne at STC Summits, and she is a sharp-thinker. Yvonne offers fantastic guidelines on how to sharpen your proofreading skills, something that I think we all can learn to do better. What do you think? Do you have anything to add to Yvonne’s recommendations? Include your suggestions below. –TechCommGeekMom
See on Scoop.it – M-learning, E-Learning, and Technical Communications
Like this:
Like Loading...
Related
About TechCommGeekMom
Danielle M. Villegas is a technical communicator who has recently started her own technical communications consultancy, Dair Communications. She has worked at the International Refugee Committee, MetLife, Novo Nordisk, BASF North America, Merck, and Deloitte, with a background in content strategy, web content management, social media, project management, e-learning, and client services. Danielle is best known in the technical communications world for her blog, TechCommGeekMom.com, which has continued to flourish since it was launched during her graduate studies at NJIT in 2012. She has presented webinars and seminars for Adobe, the Society for Technical Communication (STC), the IEEE ProComm, TCUK (ISTC) and at Drexel University’s eLearning Conference. She has written articles for the STC Intercom, STC Notebook, the Content Rules blog, and The Content Wrangler as well. You can learn more about Danielle on LinkedIn at www.linkedin.com/in/daniellemvillegas, on Twitter @techcommgeekmom, or through her blog.
