=== modified file 'doc/gnufi.texi'
--- doc/gnufi.texi	2006-10-24 20:13:52 +0000
+++ doc/gnufi.texi	2006-12-12 14:48:13 +0000
@@ -135,7 +135,7 @@
 address@hidden/build$
 @end smallexample
 
-The above example configures and build a kernel suitable to be loaded
+The above example configures and builds a firmware kernel suitable to be loaded
 by a multiboot compliant boot loader, such as @sc{gnu} GRUB.  It also
 builds a set of runtime modules and a few utilities.
 
@@ -189,13 +189,13 @@
 
 @c -----------------------------------------------------------------
 @node Loaders
address@hidden Firmware loaders
address@hidden Firmware Loaders
 
 @sc{gnufi} is designed so that the firmware can be loaded in several
 different ways, suiting the desired environment.  A @samp{loader} is
-responsible for loading the firmware kernel into memory and collect
+responsible for loading the firmware kernel into memory and collecting
 information about the environment before passing control to the
-kernel.
+firmware kernel.
 
 @menu
 * i386-multiboot::              i386 Multiboot loader
@@ -214,7 +214,7 @@
 Board specific configuration scripts, called kernel scripts or simply
 kscripts, are used to enable the user to select what services to
 include, and how to connect those services to devices.  The scripts
-contains a sequence of operations to perform while starting the
+contain a sequence of operations to perform while starting the
 firmware.  An operation is specified by a single operation command
 word and a set of arguments.  All lines that start with a @samp{#} are
 treated as comments. The following operations are available:
@@ -222,7 +222,7 @@
 @table @code
 @item load @var{MODULE}
 Load and start module specified by @var{MODULE}.  The module can
-either be an driver or an application.
+either be a driver or an application.
 
 @item connect @var{PATH}
 Connect device path specified by @var{PATH} to a (or several) suitable