<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Digital.gov</title>
    <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/colleen-blessing/</link>
    <description>Recent content on Digital.gov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/colleen-blessing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Roadmap for Creating a Writing Style Guide: One Step at a Time</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/11/20/roadmap-for-creating-a-writing-style-guide-one-step-at-a-time/</link>
      <pubDate>Fri, 20 Nov 2015 10:00:37 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/11/20/roadmap-for-creating-a-writing-style-guide-one-step-at-a-time/</guid>
      <description>So, you’re tired of seeing little (or big!) errors on your agency’s website, and you flinch at the random writing styles. You feel like your agency’s content is good, but there are still too many inconsistencies. What you need is an agency Writing Style Guide. A good guide can set styles that improve your agency’s</description>
    </item>
    <item>
      <title>Technical Writing Need Not Be Abstruse—Use Plain Language for Maximum Impact</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/10/23/technical-writing-need-not-be-abstruse-use-plain-language-for-maximum-impact/</link>
      <pubDate>Fri, 23 Oct 2015 10:00:55 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/10/23/technical-writing-need-not-be-abstruse-use-plain-language-for-maximum-impact/</guid>
      <description>Author writes: Additionally, the method utilized a myriad of factors for the purpose of incentivizing production to hit record-high levels of magnitude in the equivalent time period. Author thinks: My work sounds serious, impressive and interesting. Reader thinks: Huh? Technical writers are great—some of my favorite colleagues are technical writers. But technical writers often need</description>
    </item>
  </channel>
</rss>
