<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Personal pronouns: It’s okay to own your web copy</title>
	<atom:link href="http://blog.braintraffic.com/2010/03/personal-pronouns-it%e2%80%99s-okay-to-own-your-web-copy/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.braintraffic.com/2010/03/personal-pronouns-it%e2%80%99s-okay-to-own-your-web-copy/</link>
	<description></description>
	<lastBuildDate>Thu, 02 Feb 2012 22:49:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Kevin Rapley</title>
		<link>http://blog.braintraffic.com/2010/03/personal-pronouns-it%e2%80%99s-okay-to-own-your-web-copy/comment-page-1/#comment-1032</link>
		<dc:creator>Kevin Rapley</dc:creator>
		<pubDate>Mon, 05 Apr 2010 02:28:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1067#comment-1032</guid>
		<description>I am really pleased that you have written this Angie. This is a great article. I use personal pronouns in my web copy which I am happy with. However, sometimes I catch myself starting too many sentences with &#039;We&#039;. This feels somewhat awkward so with a second draft I try to restructure the sentences to avoid too much of this. Am I worrying over nothing? I still keep to personal pronouns when I restructure and I think the copy reads better after. Do you have any tips for avoiding this pitfall—if it is one?</description>
		<content:encoded><![CDATA[<p>I am really pleased that you have written this Angie. This is a great article. I use personal pronouns in my web copy which I am happy with. However, sometimes I catch myself starting too many sentences with &#39;We&#39;. This feels somewhat awkward so with a second draft I try to restructure the sentences to avoid too much of this. Am I worrying over nothing? I still keep to personal pronouns when I restructure and I think the copy reads better after. Do you have any tips for avoiding this pitfall—if it is one?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dey Alexander</title>
		<link>http://blog.braintraffic.com/2010/03/personal-pronouns-it%e2%80%99s-okay-to-own-your-web-copy/comment-page-1/#comment-1010</link>
		<dc:creator>Dey Alexander</dc:creator>
		<pubDate>Thu, 25 Mar 2010 04:44:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1067#comment-1010</guid>
		<description>I agree with all you&#039;ve said, except the legal restriction.   I&#039;d be challenging that too, especially if the product is co-branded. &lt;br&gt;&lt;br&gt;It may be necessary (and important for users) to say once that Company X and Company Y have created the product/are sponsoring the event/have funded the program or whatever it may be. From then on &#039;we&#039; should be just fine.</description>
		<content:encoded><![CDATA[<p>I agree with all you&#39;ve said, except the legal restriction.   I&#39;d be challenging that too, especially if the product is co-branded. </p>
<p>It may be necessary (and important for users) to say once that Company X and Company Y have created the product/are sponsoring the event/have funded the program or whatever it may be. From then on &#39;we&#39; should be just fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kozakewich</title>
		<link>http://blog.braintraffic.com/2010/03/personal-pronouns-it%e2%80%99s-okay-to-own-your-web-copy/comment-page-1/#comment-1004</link>
		<dc:creator>Michael Kozakewich</dc:creator>
		<pubDate>Fri, 19 Mar 2010 14:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1067#comment-1004</guid>
		<description>I decided to challenge myself and use only second-person pronouns (because it&#039;s all about you?) in my main body copy. I think it worked reasonably well. I don&#039;t think I referred to the company once in the entire thing -- not even to say &#039;we&#039; or &#039;us&#039;.</description>
		<content:encoded><![CDATA[<p>I decided to challenge myself and use only second-person pronouns (because it&#39;s all about you?) in my main body copy. I think it worked reasonably well. I don&#39;t think I referred to the company once in the entire thing &#8212; not even to say &#39;we&#39; or &#39;us&#39;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Melanie S.</title>
		<link>http://blog.braintraffic.com/2010/03/personal-pronouns-it%e2%80%99s-okay-to-own-your-web-copy/comment-page-1/#comment-986</link>
		<dc:creator>Melanie S.</dc:creator>
		<pubDate>Wed, 17 Mar 2010 19:28:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1067#comment-986</guid>
		<description>I had a difficult time convincing my co-workers of this, but our copy and documentation is so much better when we use personal pronouns. And the legal caveats, I&#039;d never thought of. Thanks!</description>
		<content:encoded><![CDATA[<p>I had a difficult time convincing my co-workers of this, but our copy and documentation is so much better when we use personal pronouns. And the legal caveats, I&#39;d never thought of. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlueFerret</title>
		<link>http://blog.braintraffic.com/2010/03/personal-pronouns-it%e2%80%99s-okay-to-own-your-web-copy/comment-page-1/#comment-980</link>
		<dc:creator>BlueFerret</dc:creator>
		<pubDate>Sat, 13 Mar 2010 06:35:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1067#comment-980</guid>
		<description>Thanks for writing this Angie.  The &quot;old fashioned&quot; is what I run into the most with potential clients.  Even smaller businesses tell me, &quot;We need to sound formal!&quot;&lt;br&gt;&lt;br&gt;...Why?  You&#039;re not legally required.&lt;br&gt;&lt;br&gt;Some do it because they want to sound as professional as possible.  Not realizing that on the Web, their &quot;professional&quot; comes across as &quot;snooty&quot; a lot of the time.&lt;br&gt;&lt;br&gt;Something else they miss is that by doing this, they&#039;re talking AT their audience.  Not ABOUT them.  Which is what the audience wants to read.&lt;br&gt;&lt;br&gt;When I remind them that the copy draws more people in if it&#039;s personal - and then mention the SEO hit if they&#039;re too formal - they sometimes change gears.  It&#039;s (slowly) changing out there!</description>
		<content:encoded><![CDATA[<p>Thanks for writing this Angie.  The &#8220;old fashioned&#8221; is what I run into the most with potential clients.  Even smaller businesses tell me, &#8220;We need to sound formal!&#8221;</p>
<p>&#8230;Why?  You&#39;re not legally required.</p>
<p>Some do it because they want to sound as professional as possible.  Not realizing that on the Web, their &#8220;professional&#8221; comes across as &#8220;snooty&#8221; a lot of the time.</p>
<p>Something else they miss is that by doing this, they&#39;re talking AT their audience.  Not ABOUT them.  Which is what the audience wants to read.</p>
<p>When I remind them that the copy draws more people in if it&#39;s personal &#8211; and then mention the SEO hit if they&#39;re too formal &#8211; they sometimes change gears.  It&#39;s (slowly) changing out there!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabriel Smy</title>
		<link>http://blog.braintraffic.com/2010/03/personal-pronouns-it%e2%80%99s-okay-to-own-your-web-copy/comment-page-1/#comment-978</link>
		<dc:creator>Gabriel Smy</dc:creator>
		<pubDate>Fri, 12 Mar 2010 14:34:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1067#comment-978</guid>
		<description>They say that talking to yourself is the first sign of madness but talking about yourself in the third person must be getting close.&lt;br&gt;&lt;br&gt;One of the biggest problems I find with web copy is inconsistency in the voice – people switching between third and first person or between singular and plural. I just wrote about this at SmyWord.&lt;br&gt;&lt;br&gt;Thanks for flagging up the legal issues. I haven&#039;t come across the cobranded issue before but we do have clients whose copy is legally monitored (e.g. in finance) so there must be no ambiguity around who the &#039;we&#039; is.</description>
		<content:encoded><![CDATA[<p>They say that talking to yourself is the first sign of madness but talking about yourself in the third person must be getting close.</p>
<p>One of the biggest problems I find with web copy is inconsistency in the voice – people switching between third and first person or between singular and plural. I just wrote about this at SmyWord.</p>
<p>Thanks for flagging up the legal issues. I haven&#39;t come across the cobranded issue before but we do have clients whose copy is legally monitored (e.g. in finance) so there must be no ambiguity around who the &#39;we&#39; is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://blog.braintraffic.com/2010/03/personal-pronouns-it%e2%80%99s-okay-to-own-your-web-copy/comment-page-1/#comment-974</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Thu, 11 Mar 2010 23:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1067#comment-974</guid>
		<description>Great advice, Angie. &quot;We&quot; is the way to go. Sometimes you just have to make it really clear who you mean, as we discovered when writing for Nokia’s environmental campaign. Its name? &quot;&lt;a href=&quot;http://www.polon.co.uk/our-work/detail/web-copywriting-for-nokia/&quot; rel=&quot;nofollow&quot;&gt;we:&lt;/a&gt;&quot;</description>
		<content:encoded><![CDATA[<p>Great advice, Angie. &#8220;We&#8221; is the way to go. Sometimes you just have to make it really clear who you mean, as we discovered when writing for Nokia’s environmental campaign. Its name? &#8220;<a href="http://www.polon.co.uk/our-work/detail/web-copywriting-for-nokia/" rel="nofollow">we:</a>&#8220;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

