From 02aaef2e514e6535d801f74ce21392cd4df7a9fe Mon Sep 17 00:00:00 2001
From: Paul W. Frields <stickster@gmail.com>
Date: Fri, 20 Feb 2009 16:30:22 -0500
Subject: [PATCH] Started editing standard chapter for free software

---
 en-US/Books/FreeSoftware/standard.xml |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/en-US/Books/FreeSoftware/standard.xml b/en-US/Books/FreeSoftware/standard.xml
index 560c08c..3abd0e7 100644
--- a/en-US/Books/FreeSoftware/standard.xml
+++ b/en-US/Books/FreeSoftware/standard.xml
@@ -17,21 +17,21 @@
 
     <title>Free Software Introduction</title>
     <para>
-        This chapter focuses on how to become a Free Software friendly professional.  As an engineer, developer, architect or administrator, using free software can greatly increase your efficiency for a minimum of cost.  By following the guidelines included in this document you can be sure to stay legally compliant when using free software as well has having the best possible chance if successful implementation.
+        This chapter focuses on how to become a Free Software friendly professional.  As an engineer, developer, architect or administrator, using free software can greatly increase your efficiency for a minimum of cost.  By following the guidelines included in this document you can stay legally compliant when using free software and have the best possible chance for a successful implementation.
     </para>
 
     <section id="FreeSoftware-Standard-Introduction-About">
         <title>Crash Course About Free Software</title>
         <para>
-            The <ulink url="http://www.fsf.org/about/what-is-free-software">Free Software Foundation</ulink> defines free software as: <quote>software that gives you the user the freedom to share, study and modify it. We call this free software because the user is free.</quote>  Having the code is only one part of being free.  Being allowed to do things with that code is the main difference between free software and open source software.  The free software ecosystem consists of three basic areas:
+            The <ulink url="http://www.fsf.org/about/what-is-free-software">Free Software Foundation</ulink> defines free software as <quote>software that gives you the user the freedom to share, study and modify it. We call this free software because the user is free.</quote>  Having the code is only one element of software freedom.  Being allowed to do useful things with that code is the main difference between free software and open source software.  The free software ecosystem consists of three basic layers:
             <itemizedlist>
-              <listitem><para>Upstream - Where individual applications are created. (Apache's httpd)</para></listitem>
-              <listitem><para>Distribution - Where the upstream applications are packaged and then distributed (Red Hat Enterprise Linux)</para></listitem>
-              <listitem><para>Free Software Users - Where people consume and give back to free software (You)</para></listitem>
+	      <listitem><para><firstterm>Upstream</firstterm>, where individual applications are created (e.g. Apache's httpd)</para></listitem>
+              <listitem><para><firstterm>Distribution</firstterm>, where the upstream applications are packaged and then distributed (e.g. Red Hat Enterprise Linux)</para></listitem>
+              <listitem><para>Free software users, people who consume and give back to free software (e.g. you)</para></listitem>
             </itemizedlist>
         </para>
         <para>
-            The rest of this section describes the roles each of these areas work, what is expected, and how to contribute.  One benefit of free software is that a free software user can contribute in any aspect of the ecosystem they wish.  The overall theme you'll be reading is that changes need to happen upstream.
+            The rest of this section describes how each of these layers work, what is expected from each, and how to contribute to each.  One benefit of free software is that a free software user can contribute in any aspect of the ecosystem they wish.  The overall theme you'll be reading is that changes need to happen upstream.
         </para>
         <section id="FreeSoftware-Standard-Introduction-Upstream">
           <title>Upstream</title>
-- 
1.6.0.6

