<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: 3 Copywriting Pitfalls You Must Avoid</title>
	<link>http://www.writingwhitepapers.com/blog/2009/12/03/3-copywriting-pitfalls-you-must-avoid/</link>
	<description>Everything about writing and marketing white papers</description>
	<pubDate>Wed, 08 Feb 2012 21:35:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Peggy Jo</title>
		<link>http://www.writingwhitepapers.com/blog/2009/12/03/3-copywriting-pitfalls-you-must-avoid/#comment-63199</link>
		<dc:creator>Peggy Jo</dc:creator>
		<pubDate>Thu, 31 Dec 2009 10:54:58 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2009/12/03/3-copywriting-pitfalls-you-must-avoid/#comment-63199</guid>
		<description>Thank you Mike for 3 concise points.  I try to stick to the code in my blogging.  I am working on refinement in 2010.</description>
		<content:encoded><![CDATA[<p>Thank you Mike for 3 concise points.  I try to stick to the code in my blogging.  I am working on refinement in 2010.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peggy Jo</title>
		<link>http://www.writingwhitepapers.com/blog/2009/12/03/3-copywriting-pitfalls-you-must-avoid/#comment-63053</link>
		<dc:creator>Peggy Jo</dc:creator>
		<pubDate>Thu, 31 Dec 2009 09:54:58 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2009/12/03/3-copywriting-pitfalls-you-must-avoid/#comment-63053</guid>
		<description>Thank you Mike for 3 concise points.  I try to stick to the code in my blogging.  I am working on refinement in 2010.</description>
		<content:encoded><![CDATA[<p>Thank you Mike for 3 concise points.  I try to stick to the code in my blogging.  I am working on refinement in 2010.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ntarugera</title>
		<link>http://www.writingwhitepapers.com/blog/2009/12/03/3-copywriting-pitfalls-you-must-avoid/#comment-63020</link>
		<dc:creator>Ntarugera</dc:creator>
		<pubDate>Thu, 10 Dec 2009 14:41:06 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2009/12/03/3-copywriting-pitfalls-you-must-avoid/#comment-63020</guid>
		<description>Mike: It is been so long from the time that we started communicating business matters. As for your pitfalls that we should avoid while writing our stories; I&#39;m for the 3 rd option which says : Don’t assume they’re just like you:&lt;br&gt; Too often writers assume that readers understand the terms and “inside the beltway” talk that goes around.  However, there’s no bigger turn off to readers than terms and phrases that are are foreign.  Always ask yourself, “is this phrase something the reader will understand?”  If not, kill it.&lt;br&gt;&lt;br&gt;  Ntraugera François(Journalist&#038;information analyist)</description>
		<content:encoded><![CDATA[<p>Mike: It is been so long from the time that we started communicating business matters. As for your pitfalls that we should avoid while writing our stories; I&#39;m for the 3 rd option which says : Don’t assume they’re just like you:<br /> Too often writers assume that readers understand the terms and “inside the beltway” talk that goes around.  However, there’s no bigger turn off to readers than terms and phrases that are are foreign.  Always ask yourself, “is this phrase something the reader will understand?”  If not, kill it.</p>
<p>  Ntraugera François(Journalist&#038;information analyist)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RiverwoodWriter</title>
		<link>http://www.writingwhitepapers.com/blog/2009/12/03/3-copywriting-pitfalls-you-must-avoid/#comment-63015</link>
		<dc:creator>RiverwoodWriter</dc:creator>
		<pubDate>Sun, 06 Dec 2009 18:51:12 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2009/12/03/3-copywriting-pitfalls-you-must-avoid/#comment-63015</guid>
		<description>You&#39;re right on, Mike. The underlying thread here is to always think from the reader&#39;s standpoint. What would they want? What would hold their interest? What might annoy them? &lt;br&gt;&lt;br&gt;I, too, have a pet peeve with industry acronyms. I preach this as a board member when management gives me reports that I&#39;m supposed to understand in order to do my job as a board member. If acronyms--or special terminology-- have to be used, always include a legend or sidebar with the terms in alphabetical order followed by their explanation or definition.</description>
		<content:encoded><![CDATA[<p>You&#39;re right on, Mike. The underlying thread here is to always think from the reader&#39;s standpoint. What would they want? What would hold their interest? What might annoy them? </p>
<p>I, too, have a pet peeve with industry acronyms. I preach this as a board member when management gives me reports that I&#39;m supposed to understand in order to do my job as a board member. If acronyms&#8211;or special terminology&#8211; have to be used, always include a legend or sidebar with the terms in alphabetical order followed by their explanation or definition.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristi Daniels</title>
		<link>http://www.writingwhitepapers.com/blog/2009/12/03/3-copywriting-pitfalls-you-must-avoid/#comment-63013</link>
		<dc:creator>Kristi Daniels</dc:creator>
		<pubDate>Fri, 04 Dec 2009 16:15:11 +0000</pubDate>
		<guid>http://www.writingwhitepapers.com/blog/2009/12/03/3-copywriting-pitfalls-you-must-avoid/#comment-63013</guid>
		<description>Things are changing.  Advice use to be to always assume the sale.&lt;br&gt;&lt;br&gt;I agree though.  People don&#39;t like to be sold now.  They like to be informed and then asked if they would like to place an order.</description>
		<content:encoded><![CDATA[<p>Things are changing.  Advice use to be to always assume the sale.</p>
<p>I agree though.  People don&#39;t like to be sold now.  They like to be informed and then asked if they would like to place an order.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

