<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Grammar Software &#187; writing tips</title>
	<atom:link href="http://www.grammarsoftware.com/blog/topics/writing-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.grammarsoftware.com</link>
	<description></description>
	<lastBuildDate>Thu, 09 Feb 2012 11:37:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Is There Such A Thing As Too Much Rewriting?</title>
		<link>http://www.grammarsoftware.com/blog/rewriting/</link>
		<comments>http://www.grammarsoftware.com/blog/rewriting/#comments</comments>
		<pubDate>Wed, 25 Jan 2012 05:52:52 +0000</pubDate>
		<dc:creator>grammar</dc:creator>
				<category><![CDATA[writing tips]]></category>
		<category><![CDATA[revision]]></category>
		<category><![CDATA[rewriting]]></category>

		<guid isPermaLink="false">http://www.grammarsoftware.com/?p=2412</guid>
		<description><![CDATA[We&#8217;ve often harped on about the benefits of rewriting.  Without it, you&#8217;ll be stuck with whatever came out of your [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve often harped on about the benefits of rewriting.  Without it, you&#8217;ll be stuck with whatever came out of your first draft, which, judging from experience, usually isn&#8217;t all that good.</p>
<p>However, there are some people who do take rewriting too far.  They go over their piece once, twice, thrice and more, yet never come away satisfied.  For some reason, they always feel like something else can be tweaked, changed and made better.</p>
<p>It&#8217;s easy to fall into that trap, too.  After all, we all want our writing to be the best we can produce and rewriting gives you the opportunity to create improvements.   However, make sure to define an end point &#8212; a time when you will stop adding changes.  Otherwise, you could be stuck obsessing on revisions, missing deadlines and losing other opportunities as a result.</p>
<p>That end point, of course, will depend on you, but you need to establish one.  You could do it after two full rewrites.  Or 24 hours after the original draft is finished.  Or if your paper receives an 80 or higher score using your readability software.   Whatever arbitrary rule you choose to signal the end point, stick to it &#8212; that should help you get rid of the nagging feeling that you might still need a little work done.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.grammarsoftware.com/blog/rewriting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Keeping A Writer&#8217;s Journal</title>
		<link>http://www.grammarsoftware.com/blog/keeping-writers-journal/</link>
		<comments>http://www.grammarsoftware.com/blog/keeping-writers-journal/#comments</comments>
		<pubDate>Wed, 04 Jan 2012 11:15:48 +0000</pubDate>
		<dc:creator>grammar</dc:creator>
				<category><![CDATA[writing tips]]></category>
		<category><![CDATA[journal]]></category>
		<category><![CDATA[journaling]]></category>
		<category><![CDATA[writer's journal]]></category>

		<guid isPermaLink="false">http://www.grammarsoftware.com/?p=2384</guid>
		<description><![CDATA[Many writers I know don&#8217;t keep a journal.  It&#8217;s understandable.  The process of keeping a diary can feel very adolescent, [...]]]></description>
			<content:encoded><![CDATA[<p>Many writers I know don&#8217;t keep a journal.  It&#8217;s understandable.  The process of keeping a diary can feel very adolescent, after all.  However, it&#8217;s also one of the most useful tools any writer can have to help in the overall development of their craft.</p>
<p>Why keep one?</p>
<ol>
<li>To keep a record of ideas for future work.  It&#8217;s not uncommon for writers to come up with clever ideas at the most inopportune time.  Keeping a journal is your best shot at making sure those ideas don&#8217;t just disappear right when you need them.</li>
<li>To write freely.  If you write for a living, then it&#8217;s likely that you rarely write solely for yourself.   A journal gives you the opportunity to do write that way &#8212; without judgment.</li>
<li>To get perspective.  Some writers use their journal to write down thoughts on their development as a writer.  If you do the same, you can accumulate quite a treasure trove of insightful material that you can later read to give you some perspective on your growth (or lack of it) in the craft.</li>
<li>To get the gears running.  Because a journal is a free space for you to write, it&#8217;s a highly-effective way to get the writing gears going when you&#8217;re stuck or struggling.   Try it the next time you&#8217;re sitting in front of the computer and the words just won&#8217;t come.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.grammarsoftware.com/blog/keeping-writers-journal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Finding A Writing Style</title>
		<link>http://www.grammarsoftware.com/blog/finding-writing-style/</link>
		<comments>http://www.grammarsoftware.com/blog/finding-writing-style/#comments</comments>
		<pubDate>Wed, 28 Dec 2011 12:46:31 +0000</pubDate>
		<dc:creator>grammar</dc:creator>
				<category><![CDATA[writing tips]]></category>
		<category><![CDATA[developing your writing style]]></category>
		<category><![CDATA[discovering your writing style]]></category>
		<category><![CDATA[writing style]]></category>

		<guid isPermaLink="false">http://www.grammarsoftware.com/?p=2376</guid>
		<description><![CDATA[What&#8217;s the best writing style in the world?  We&#8217;re not actually sure.  We do have a good idea of what&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>What&#8217;s the best writing style in the world?  We&#8217;re not actually sure.  We do have a good idea of what&#8217;s the best writing style for you: whatever comes most naturally.</p>
<p>Let me explain.  When you write in a natural style, your expression feels more authentic.  You don&#8217;t struggle with finding the words, since that is how you can most comfortably convey your thoughts.  Your writing feels loose and relaxed, as that is likely how you feel yourself while you were composing it.</p>
<p>Contrast that with attempting to sound like someone else.   Instead of focusing on your ideas, you split your attention between expressing your thoughts clearly and mimicking a style that&#8217;s unfamiliar to you.  Writing on a deadline is stressful enough &#8212; having to sound like someone else will just add to your woes.</p>
<p>What if you want your writing to resemble the kind of writing you admire?   If that&#8217;s the case, we still recommend doing the same.  Instead of just writing in that natural style, though, try to integrate one element from your target style into everything you write.  Just focus on one, all while doing the things that you normally do otherwise.   That way, your writing can retain the same relaxed and natural feel, all while gradually learning new things that can bring it closer towards your target style.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.grammarsoftware.com/blog/finding-writing-style/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Three Tips For New Nonfiction Writers</title>
		<link>http://www.grammarsoftware.com/blog/tips-nonfiction-writers/</link>
		<comments>http://www.grammarsoftware.com/blog/tips-nonfiction-writers/#comments</comments>
		<pubDate>Sun, 18 Dec 2011 01:45:24 +0000</pubDate>
		<dc:creator>grammar</dc:creator>
				<category><![CDATA[writing tips]]></category>
		<category><![CDATA[new writers]]></category>
		<category><![CDATA[nonfiction writing]]></category>

		<guid isPermaLink="false">http://www.grammarsoftware.com/?p=2363</guid>
		<description><![CDATA[Want to get on the road writing nonfiction?  As a novice to the field, there are certain things that can [...]]]></description>
			<content:encoded><![CDATA[<p>Want to get on the road writing nonfiction?  As a novice to the field, there are certain things that can help you grease your gears and get off to a good start.</p>
<ol type="1">
<li>Focus on what you know.     To get started right, you need to write a lot.  The best way to do that is to focus your efforts on the subjects that you already have a decent grasp on.  It&#8217;s going to be hard to be proficient on fields where you&#8217;re an absolute newbie, so write about what you know to get a firm start.</li>
<li>Write about subjects that interest you.  Think of your writing as a present and future career.   What do you want to be writing about in two or three years&#8217; time?  If you intend to be an authority on dating and relationships, then those are the topics you should focus on.  Same if you want to be a respected food critic, a fashion writer or a respected voice on the automotive industry.</li>
<li>Develop a system that works for you.  If you&#8217;re going to produce output with any regularity, you need to develop a dependable system that gives your work some structure.   You can&#8217;t depend on inspiration or a good mood to strike.  Instead, you need to be able to work regardless of what&#8217;s going on with other things in your life.  For that, a system will benefit you immensely.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.grammarsoftware.com/blog/tips-nonfiction-writers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Keep Your Editors Happy</title>
		<link>http://www.grammarsoftware.com/blog/editors-happy/</link>
		<comments>http://www.grammarsoftware.com/blog/editors-happy/#comments</comments>
		<pubDate>Tue, 13 Dec 2011 11:06:41 +0000</pubDate>
		<dc:creator>grammar</dc:creator>
				<category><![CDATA[writing tips]]></category>
		<category><![CDATA[editors]]></category>
		<category><![CDATA[keeping editors happy]]></category>
		<category><![CDATA[working with editors]]></category>

		<guid isPermaLink="false">http://www.grammarsoftware.com/?p=2355</guid>
		<description><![CDATA[Trying to establish yourself as a freelance writer?   Then it pays to get on your editors&#8217; good side.  You make [...]]]></description>
			<content:encoded><![CDATA[<p>Trying to establish yourself as a freelance writer?   Then it pays to get on your editors&#8217; good side.  You make them happy, you get more work.  Aside from writing good material, here are things you can do to get on your editors&#8217; good graces.</p>
<ol type="1">
<li>Make deadlines.  Failing to make deadlines is a cardinal sin for freelance writers.   Gaining a reputation as a regular tardy submitter can have you shunned, regardless of how clean and polished your copy is.</li>
<li>Make your word count.  Never submit copy that&#8217;s less than the required word count.  If you go over, never go higher than 10% of the target count.   In fact, 10% over can be ideal as it gives the editor room to trim parts they might not be big fans of.</li>
<li>Bring up problems early.  Don&#8217;t wait for the last minute to inform editors about problems with your assignment.   Whether you can&#8217;t locate a crucial source or you&#8217;re having personal problems that&#8217;s preventing you from working at a fast pace, let the editor know early.  Just make sure you can justify any problems (i.e. don&#8217;t make up stuff just to push a deadline) and suggest a solution.</li>
<li>Be respectful at all times.  Sometimes, you won&#8217;t see things eye to eye with your editor.   Some of those times, you&#8217;ll need to step back and give way.  Other times, you&#8217;ll need to stand up for what you believe.  In either case, be respectful .  You can still express a contrarian opinion while recognizing your editor&#8217;s position and authority.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.grammarsoftware.com/blog/editors-happy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Seven-Step Structure For Your Essay Writing Process</title>
		<link>http://www.grammarsoftware.com/blog/sevenstep-structure-essay-writing-process/</link>
		<comments>http://www.grammarsoftware.com/blog/sevenstep-structure-essay-writing-process/#comments</comments>
		<pubDate>Mon, 05 Dec 2011 11:05:41 +0000</pubDate>
		<dc:creator>grammar</dc:creator>
				<category><![CDATA[writing tips]]></category>
		<category><![CDATA[essay writing]]></category>
		<category><![CDATA[essay writing steps]]></category>

		<guid isPermaLink="false">http://www.grammarsoftware.com/?p=2341</guid>
		<description><![CDATA[Need to put more structure in your writing process?  If you have no clue where to start, you can follow [...]]]></description>
			<content:encoded><![CDATA[<p>Need to put more structure in your writing process?  If you have no clue where to start, you can follow this seven-step guideline that divides the work into focused and manageable chunks.</p>
<ol type="1">
<li>Plan.  Read the assignment brief and make a detailed list of things you&#8217;ll need to do.  Are you supposed to investigate, analyze, compare, review or perform some other action? Define your work clearly.  Then, make a list of possible sources you will se for your research.   This bit of planning will help you push through the rest of the steps without having to reconsider at every turn.</li>
<li>Schedule.  Create a timetable .  Assign more time to preparation (research, outlining) than the actual writing and revision stages.  Getting those crucial first steps right will make the actual writing part go much smoother.</li>
<li>Gather data.  When it comes to research data, you want to gather as much as you can.  That way, you won&#8217;t end up short on information right when you need it.  Make sure to highlight key data, so you can quickly find them later.</li>
<li>Outline.  Organize your data and write down a list of main points in the order you believe they should be presented in the essay.  Refer to your research to find pertinent information.</li>
<li>Draft.  Write your first draft, following the pattern and structure you defined in the outline.</li>
<li>Revise.  After the first draft, put it down for some time (ideally a day) before returning to it for review and revision.  Make a few passes, starting with big picture changes (e.g. overall structure) before drilling down to the nitty-gritty (e.g. word choice).</li>
<li>Put finishing touches.    Once you&#8217;re satisfied with the rewrites, time to put the essay through the final phases: run it through your grammar software, double-check facts and numbers, and tidy up the presentation.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.grammarsoftware.com/blog/sevenstep-structure-essay-writing-process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Formal English</title>
		<link>http://www.grammarsoftware.com/blog/formal-english/</link>
		<comments>http://www.grammarsoftware.com/blog/formal-english/#comments</comments>
		<pubDate>Fri, 02 Dec 2011 13:50:42 +0000</pubDate>
		<dc:creator>grammar</dc:creator>
				<category><![CDATA[writing tips]]></category>
		<category><![CDATA[formal English]]></category>
		<category><![CDATA[formal writing]]></category>

		<guid isPermaLink="false">http://www.grammarsoftware.com/?p=2338</guid>
		<description><![CDATA[Formal English is the language commonly used in business, government and academic settings.  When used, it conveys a dignified and [...]]]></description>
			<content:encoded><![CDATA[<p>Formal English is the language commonly used in business, government and academic settings.  When used, it conveys a dignified and distinguished tone that paints the author as a professional.</p>
<p>While most people will probably prefer a more conversational tone for everyday writing, there always comes a time when sounding more professional will serve you well.  Sure, emails to friends and letters to family always work better when written conversationally.  But how about when submitting a report to your board of directors, preparing a proposal to a group of bank executives or completing a paper for a science journal?</p>
<p>Do note that even &#8220;formal English&#8221; can vary in degrees.   While a job proposal may require strictly formal language, an expository essay for a History course will work with a slightly less strict tone.  In both cases, however, it is characterized with adherence to grammatical correctness, a neutral tone and more professional-oriented language choices.</p>
<p>Pretty much any situation where you need to make a good impression and paint yourself as a professional, you&#8217;ll probably need to write in a formal English.   Some of these include:</p>
<p>Business letters (regardless of whether you&#8217;re writing as a business or as an individual that&#8217;s part of an organization)</p>
<ul>
<li>Government correspondence</li>
<li>Legal documents</li>
<li>Office reports</li>
<li>Job applications</li>
<li>University papers</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.grammarsoftware.com/blog/formal-english/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Common Logical Fallacies Your Essay Could Be Falling Into</title>
		<link>http://www.grammarsoftware.com/blog/common-logical-fallacies-essay-falling/</link>
		<comments>http://www.grammarsoftware.com/blog/common-logical-fallacies-essay-falling/#comments</comments>
		<pubDate>Sun, 27 Nov 2011 02:03:22 +0000</pubDate>
		<dc:creator>grammar</dc:creator>
				<category><![CDATA[writing tips]]></category>
		<category><![CDATA[essay writing]]></category>
		<category><![CDATA[logical fallacy]]></category>
		<category><![CDATA[reasoning]]></category>

		<guid isPermaLink="false">http://www.grammarsoftware.com/?p=2330</guid>
		<description><![CDATA[When writing your papers, you need to make sure that your reasoning is sound. All the evidence in the world [...]]]></description>
			<content:encoded><![CDATA[<p>When writing your papers, you need to make sure that your reasoning is sound.  All the evidence in the world won&#8217;t help validate your case if your interpretation is off and your logic is faulty.</p>
<p>Reasoning errors may be intentional.  Some authors will engage in it as a way to trick readers when their argument can&#8217;t actually hold on its own.   Most of the time, though, these types of problems arise unintentionally, either as a result of carelessness or just faulty thinking.</p>
<p>Common logical fallacies you might end up writing include:</p>
<p>	1. Hasty generalizations.  This is when you come up with a generalization based on too little evidence.<br />
	2. False choice.  Here, you frame a situation as having only two choices when there are, in fact, a lot more possible options.<br />
	3. Non-sequitur.  This is when the conclusion isn&#8217;t directly in line with the premise.<br />
	4. False Analogy.  Here, you wrongly assume that similarities in two things make them similar in every other way, too.<br />
	5. Ad Hominem.  Instead of arguing against the issue, this faulty approach attacks the personalities that support the opposing view.<br />
	6. Red Herring. This is when you cite an unrelated issue instead of addressing the issue directly.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.grammarsoftware.com/blog/common-logical-fallacies-essay-falling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Technical Writing Sections: Part II</title>
		<link>http://www.grammarsoftware.com/blog/technical-writing-sections-part-ii/</link>
		<comments>http://www.grammarsoftware.com/blog/technical-writing-sections-part-ii/#comments</comments>
		<pubDate>Sat, 19 Nov 2011 02:30:50 +0000</pubDate>
		<dc:creator>grammar</dc:creator>
				<category><![CDATA[writing tips]]></category>
		<category><![CDATA[technical document]]></category>
		<category><![CDATA[technical document sections]]></category>
		<category><![CDATA[technical writing]]></category>

		<guid isPermaLink="false">http://www.grammarsoftware.com/?p=2311</guid>
		<description><![CDATA[We covered five of the elements you can use in standard technical documents in the last piece.  Here are the [...]]]></description>
			<content:encoded><![CDATA[<p>We covered five of the elements you can use in standard technical documents in the last piece.  Here are the rest:</p>
<ul>
<li>Procedures.  This explains the work that was carried out in order to come to the results, including a description of each task and the equipment used.  Any problems that needed to be overcome will also be covered here.</li>
<li>Results.  This part offers a brief explanation of the results you got off the procedures, often bearing tables and graphs that show them in detail.</li>
<li>Interpretation.  Results are often made up of exact numbers or hard facts.  For that data to carry any relevance, it has to be interpreted.  You do that here, giving your reasoning for each interpretation you offer.</li>
<li>Conclusion.  This section gives the reader the overall findings based on all the work previously done.</li>
<li>Recommendations.  Normally, readers will peruse a document to be enlightened about a matter that requires their decision.  This section allows you to recommend a course of action for them.</li>
<li>References.  This section lists the publications referred to, whether in general or particular, in both your technical document and in the work carried out for it.  You can also add a list of materials for further reading to those members of the audience who would like to follow up on the topic.</li>
<li>Appendix.  Here, you include any additional supporting materials, such as examples, a glossary of technical terms and the like.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.grammarsoftware.com/blog/technical-writing-sections-part-ii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Technical Writing Sections: Part I</title>
		<link>http://www.grammarsoftware.com/blog/technical-writing-sections-part/</link>
		<comments>http://www.grammarsoftware.com/blog/technical-writing-sections-part/#comments</comments>
		<pubDate>Wed, 16 Nov 2011 17:27:27 +0000</pubDate>
		<dc:creator>grammar</dc:creator>
				<category><![CDATA[writing tips]]></category>
		<category><![CDATA[technical writing]]></category>
		<category><![CDATA[technical writing components]]></category>

		<guid isPermaLink="false">http://www.grammarsoftware.com/?p=2308</guid>
		<description><![CDATA[Writing technical documents?  While each one will vary depending on its purpose and audience, most technical writing revolve around a [...]]]></description>
			<content:encoded><![CDATA[<p>Writing technical documents?  While each one will vary depending on its purpose and audience, most technical writing revolve around a similar format, based around the standard model for technical documentation.</p>
<p>The standard technical writing model uses multiple sections, one or more of which will appear in every technical paper.  In these series of articles, we&#8217;ll cover the different sections that comprise this model.  Here are the first five:</p>
<ul>
<li>Abstract.  This is a brief summary of the document, giving readers an overview of the its contents, including any conclusions or recommendations.   The recommended length for abstracts is 300 words, although this could vary depending on the requirements of the organization or publication you&#8217;re writing for.</li>
<li>Acknowledgment.  Here, you cite all the individuals that directly helped in the work described in the document.</li>
<li>Introduction.  This section explains the main subject of the document, its goals, and how it fits in with the other work done in that field.</li>
<li>Objectives.  What results are the document expected to accomplish?  You list those down in this section, elaborating on the reasons for these objectives and who each is aimed for.</li>
<li>Theory.  Here, you describe and explain any background theory that&#8217;s required for the reader to understand your document, ensuring that all your readers are adequately informed of the basic technical details they need.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.grammarsoftware.com/blog/technical-writing-sections-part/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

