Spelling and grammar sweep.

svn path=/www/; revision=30911

en/projects/ideas/ideas.xml

@@ -15,7 +15,7 @@ Ideas//EN"
 <ideas>
   <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
     <cvs:keyword name="freebsd">
-      $FreeBSD: www/en/projects/ideas/ideas.xml,v 1.26 2007/10/14 15:48:12 netchild Exp $
+      $FreeBSD: www/en/projects/ideas/ideas.xml,v 1.27 2007/10/14 17:44:18 hrs Exp $
     </cvs:keyword>
   </cvs:keywords>
 
@@ -70,7 +70,7 @@ Ideas//EN"
       <title>Extend UFS2 with on-disk indexing</title>
 
       <desc><p>The section <emph>8.3 Naming</emph> of the book
-        <emph>Design and Implementation of FreeBSD operation system</emph>
+        <emph>Design and Implementation of the FreeBSD Operating System</emph>
         describes the current approach of name lookups in UFS2 and a possible
         extension/improvement by utilizing on-disk indexing in a backward
         compatible way. While the current approach (an in-memory directory cache)
@@ -80,7 +80,7 @@ Ideas//EN"
 <ul>
   <li>Knowledge of C programming.</li>
   <li>Basic understanding of filesystems.</li>
-  <li>The book <emph>Design and Implementation of FreeBSD operation system</emph>.</li>
+  <li>The book <emph>Design and Implementation of the FreeBSD Operating System</emph>.</li>
 </ul>
       </desc>
     </idea>
@@ -99,7 +99,7 @@ Ideas//EN"
         towards ext3fs, which supports the same on-disk format as ext2fs and
         adds journalling. Porting NetBSD's ext2fs and adding support for in
         gjournal (if possible) would make an excellent combination. Other
-        desirables possibilities would be to implement EA/ACLs and to use
+        desirable possibilities would be to implement EA/ACLs and to use
         it as root filesystem.</p>
 <p><strong>Requirements</strong>:</p>
 <ul>
@@ -115,14 +115,14 @@ Ideas//EN"
       <desc><p>While FreeBSD's FFS implementation is pretty much
         state-of-the-art, in addition to softupdates, Greg Granger <a
         href="http://www.ece.cmu.edu/~ganger/papers/cffs.html">proposed</a>
-        other stategies that would be useful, especially when working
+        other strategies that would be useful, especially when working
         with small files. Quoting Greg Ganger: "The key insight for why
         current file systems perform poorly is that locality is insufficient
         - exploiting disk bandwidth for small data objects requires that
-        they be placed adjacently". Explict grouping, in particular, seems
+        they be placed adjacently". Explicit grouping, in particular, seems
         to provide important performance improvements without less
         implementation complexity than embedded inodes. As this changes
-        the on-disk structure, care needs to be taken, that the
+        the on-disk structure, care needs to be taken that the
         implementation is backwards compatible.</p>
 <p><strong>Requirements</strong>:</p>
 <ul>
@@ -656,7 +656,7 @@ they all need to be locked.</p>
 	<title>Add support for the sensors framework to more drivers</title>
 
 	<desc>
-<p>Not much drivers make use of the sensors framework yet. Possible targets
+<p>Not many drivers make use of the sensors framework yet. Possible targets
   which should be enhanced to use the sensors framework are ATA/SCSI (temperature,
   write cache status, ...), GEOM (RAID status, ...), ACPI (temperature,
   voltage, ...) and more.</p>
@@ -793,9 +793,9 @@ they all need to be locked.</p>
   things like FreeBSD 5.x compatibility are present on the system (just
   installing the compat5x port is not enough, you need a kernel built
   with COMPAT_FREEBSD5).  All such optional kernel features should
-  registered themselves in a common location (e.g. sysctl MIB) so that
+  register themselves in a common location (e.g. sysctl MIB) so that
   the userland can easily query whether a given feature is present. There
-  needs also be a way to spoof those values, e.g., when the ports build
+  needs also to be a way to spoof those values, e.g., when the ports build
   cluster is building for older FreeBSD versions in a jail.</p>
 <p><strong>Requirements</strong>:</p>
 <ul>
@@ -929,7 +929,7 @@ they all need to be locked.</p>
   href="mailto:mharvan@inf.ethz.ch">Matus Harvan</a><br />
   <strong>WIP</strong>: <a
   href="http://wiki.freebsd.org/mtund">http://wiki.freebsd.org/mtund</a></p>
-<p>IP can be tunneled over IP, UDP, TCP, SSH, DNS, HTTP and many other
+<p>IP can be tunnelled over IP, UDP, TCP, SSH, DNS, HTTP and many other
   protocols, and this means that it is often possible to get a
   connection out through a firewall, but each of these encapsulations
   require prior setup of a specific program for each encapsulation, and
@@ -1513,9 +1513,9 @@ New tests must be created; existing tests must be completed and updated.
   href="mailto:cperciva@FreeBSD.org">Colin Percival</a></p>
 <p>The freebsd-update(8) utility is used to fetch, install, and rollback
   binary updates to the FreeBSD base system.  A nice project would be to
-  develop at graphical front-end for freebsd-update(8), using the QT toolkit.
+  develop a graphical front-end for freebsd-update(8), using the QT toolkit.
   A GTK frontend was developed as part of GSoC 2007 and exists at <a
-  href="http://developer.berlios.de/projects/facund">berlios</a>, the QT
+  href="http://developer.berlios.de/projects/facund">berlios</a>; the QT
   frontend could maybe share common functions/classes and design ideas.</p>
 <p><strong>Requirements</strong>:</p>
 <ul>
@@ -1769,7 +1769,7 @@ clean.</p>
         <desc>
 <p><strong>Technical contact</strong>: <a href="mailto:jeff@FreeBSD.org">Jeff Roberson</a></p>
 
-<p>Schedgraph is a tool for analyzing scheduling events and visualy
+<p>Schedgraph is a tool for analyzing scheduling events and visually
 displaying them in such a way that they reveal interesting kernel
 and application performance problems.  It is written in python/tkinter
 and interfaces with the kernel via the generic KTR kernel tracing
@@ -1847,7 +1847,7 @@ SMP features.</p>
     <a href="mailto:yar@FreeBSD.org">Yar Tikhiy</a></p>
     
   <p>Currently, cron(8) and atrun(8) are outdated in their implementation.
-    Here are some directions for impovement:</p>
+    Here are some directions for improvement:</p>
   <ul>
     <li>Convert atrun(8) to using setusercontext(3) instead of creating  
       the job context through a sequence of basic syscalls.</li>