SHA1 Hash:	d0e8e88d546eda1fcc18f9401a3f3bc8f4e80777
Date:	2008-10-09 18:09:37
User:	aku
Comment:	Fixed a number of small typos.
Timelines:	ancestors | descendants | both | trunk
Other Links:	files | ZIP archive | manifest

• branch=trunk inherited from [a28c83647d]
• sym-trunk inherited from [a28c83647d]

Modified www/qandc.wiki from [75989d6590] to [1cfcbbb4e1].

@@ -11,19 +11,19 @@
   <p>I wrote fossil because none of the
   other available DVCSes met my needs.  If the other DVCSes do
   meet your needs, then you might not need fossil.  But they
   don't meet mine, and so fossil is necessary for me.</p>
 
-  <p>Feature provided by fossil that one does not get with other
+  <p>Features provided by fossil that one does not get with other
   DVCSes include:</p>
 
   <ol>
   <li> Integrated <a href="wikitheory.wiki">wiki</a>. </li>
   <li> Integrated <a href="bugtheory.wiki">bug tracking</a> </li>
   <li> Immutable artifacts </li>
-  <li> self-contained, stand-alone executable </li>
-  <li> simple, well-defined,
+  <li> Self-contained, stand-alone executable </li>
+  <li> Simple, well-defined,
        <a href="fileformat.wiki">enduring file format</a> </li>
   </ol>
 </blockquote>
 
 <b>Why should I use this rather than Trac?</b>
@@ -55,11 +55,11 @@
 The documentation files for
 <a href="http://www.sqlite.org/">SQLite</a> are hosted in a
 fossil repository <a href="http://www.sqlite.org/docsrc/">here</a>,
 for example.
 Other projects are also adopting fossil.  But fossil does not yet have
-the massive user base of git or mecurial.
+the massive user base of git or mercurial.
 </blockquote>
 
 <b>Fossil looks like the bug tracker that would be in your
 Linksys Router's administration screen.</p>
 
@@ -74,25 +74,25 @@
 self-hosting.  Send me email to request a password that will let
 you push to the main fossil repository.</p>
 </blockquote>
 
 <b>It would be useful to have a separate application that
-keeps the bug-tracking database in a versioned filed. That file can
+keeps the bug-tracking database in a versioned file. That file can
 then be pushed and pulled along with the rest repository.</b>
 
 <blockquote>
-<p>This addressed in the opening paragraphs of
+<p>This is addressed in the opening paragraphs of
 the <a href="bugtheory.wiki">Bug-Tracking In Fossil</a> document.
 </blockquote>
 
 <b>Fossil is already the name of a plan9 versioned
 append-only filesystem.</b>
 
 <blockquote>
 I did not know that.  Perhaps they selected the name for the same reason that
 I did: because a repository with immutable artifacts preserves
-and excellent fossil record of a long-running project.
+an excellent fossil record of a long-running project.
 </blockquote>
 
 <b>The idea of storing a repository in a binary blob like an
 SQLite database terrifies me.</b>
 
@@ -99,11 +99,11 @@
 <blockquote>
 The use of SQLite to store the database is likely more stable and secure
 than any other approach, due to the fact that SQLite is transactional.
 Fossil also implements several internal
 <a href="selfcheck.wiki">self-checks</a> to insure that no information
-is every lost.  And, indeed, in over a year of operation, there have been
+is ever lost.  And, indeed, in over a year of operation, there have been
 no reports of data loss due to a Fossil malfunction.
 </blockquote>
 
 
 <b>I am dubious of the benefits of including wikis and bug trackers