<?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: How to Write a How-To</title>
	<atom:link href="http://diyubook.com/2011/01/how-to-write-a-how-to/feed/" rel="self" type="application/rss+xml" />
	<link>http://diyubook.com/2011/01/how-to-write-a-how-to/</link>
	<description>Edupunks, Edupreneurs, and the coming transformation of higher education</description>
	<lastBuildDate>Thu, 18 Jul 2013 18:44:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Kasal Payo</title>
		<link>http://diyubook.com/2011/01/how-to-write-a-how-to/comment-page-1/#comment-4942</link>
		<dc:creator>Kasal Payo</dc:creator>
		<pubDate>Sun, 05 Jun 2011 22:18:46 +0000</pubDate>
		<guid isPermaLink="false">http://diyubook.com/?p=393#comment-4942</guid>
		<description>Pick up your sword and fight!!</description>
		<content:encoded><![CDATA[<p>Pick up your sword and fight!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janet Swisher</title>
		<link>http://diyubook.com/2011/01/how-to-write-a-how-to/comment-page-1/#comment-4099</link>
		<dc:creator>Janet Swisher</dc:creator>
		<pubDate>Mon, 31 Jan 2011 21:19:49 +0000</pubDate>
		<guid isPermaLink="false">http://diyubook.com/?p=393#comment-4099</guid>
		<description>I agree with Josh&#039;s suggestions.

Steps should be just one action each, and should describe the outcome or state when you complete the step correctly (unless it&#039;s trivial, obvious, or already covered by the action description).

Keep all steps together, and don&#039;t interleave them with conceptual explanations. Put concepts before, after, or elsewhere. 

Put warnings and cautions &lt;em&gt;before&lt;/em&gt; the step they apply to.</description>
		<content:encoded><![CDATA[<p>I agree with Josh&#8217;s suggestions.</p>
<p>Steps should be just one action each, and should describe the outcome or state when you complete the step correctly (unless it&#8217;s trivial, obvious, or already covered by the action description).</p>
<p>Keep all steps together, and don&#8217;t interleave them with conceptual explanations. Put concepts before, after, or elsewhere. </p>
<p>Put warnings and cautions <em>before</em> the step they apply to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Baron</title>
		<link>http://diyubook.com/2011/01/how-to-write-a-how-to/comment-page-1/#comment-4031</link>
		<dc:creator>Josh Baron</dc:creator>
		<pubDate>Wed, 26 Jan 2011 23:32:26 +0000</pubDate>
		<guid isPermaLink="false">http://diyubook.com/?p=393#comment-4031</guid>
		<description>Maybe tips/tricks or pitfalls to avoid?  I&#039;m thinking of assembling things like a bike or kids toy...the people will often point on out blogs, etc. where the common confusion points are or common mistakes to avoid.

Might also want to suggest desired outcomes/goals...something like, you&#039;ll know that you&#039;ve successfully adopted an open textbook when your students tell other instructors they should be using open textbooks also...</description>
		<content:encoded><![CDATA[<p>Maybe tips/tricks or pitfalls to avoid?  I&#8217;m thinking of assembling things like a bike or kids toy&#8230;the people will often point on out blogs, etc. where the common confusion points are or common mistakes to avoid.</p>
<p>Might also want to suggest desired outcomes/goals&#8230;something like, you&#8217;ll know that you&#8217;ve successfully adopted an open textbook when your students tell other instructors they should be using open textbooks also&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
