<?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: Two ways to improve your Blogger.com blog</title>
	<atom:link href="http://www.bloggingforpeoplewhoshould.com/2010/01/two-ways-to-improve-your-blogger-com-blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bloggingforpeoplewhoshould.com/2010/01/two-ways-to-improve-your-blogger-com-blog/</link>
	<description>An introduction to telling important stories online</description>
	<lastBuildDate>Wed, 04 Jan 2012 06:21:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Two ways to deal with those pesky &#8216;Posted in&#8217; links on WordPress.com blogs &#124; Blogging for People Who Should</title>
		<link>http://www.bloggingforpeoplewhoshould.com/2010/01/two-ways-to-improve-your-blogger-com-blog/comment-page-1/#comment-6581</link>
		<dc:creator>Two ways to deal with those pesky &#8216;Posted in&#8217; links on WordPress.com blogs &#124; Blogging for People Who Should</dc:creator>
		<pubDate>Fri, 20 May 2011 01:50:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingforpeoplewhoshould.com/?p=94#comment-6581</guid>
		<description>[...] does a similar trick with their Next Blog &#8216;feature&#8217; &#8211; I explained how to deal with that glitch here. Here are two ways to avoid this problem on [...]</description>
		<content:encoded><![CDATA[<p>[...] does a similar trick with their Next Blog &#8216;feature&#8217; &#8211; I explained how to deal with that glitch here. Here are two ways to avoid this problem on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Two ways to deal with those pesky &#8216;Posted in&#8217; links on WordPress.com blogs &#124; Blogging for People Who Should</title>
		<link>http://www.bloggingforpeoplewhoshould.com/2010/01/two-ways-to-improve-your-blogger-com-blog/comment-page-1/#comment-6582</link>
		<dc:creator>Two ways to deal with those pesky &#8216;Posted in&#8217; links on WordPress.com blogs &#124; Blogging for People Who Should</dc:creator>
		<pubDate>Fri, 20 May 2011 01:50:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingforpeoplewhoshould.com/?p=94#comment-6582</guid>
		<description>[...] does a similar trick with their Next Blog &#8216;feature&#8217; &#8211; I explained how to deal with that glitch here. Here are two ways to avoid this problem on [...]</description>
		<content:encoded><![CDATA[<p>[...] does a similar trick with their Next Blog &#8216;feature&#8217; &#8211; I explained how to deal with that glitch here. Here are two ways to avoid this problem on [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

