doc: typo fixes

b9f10af5 · Erik van der Bij · Alessandro Rubini · bbff24dc · b9f10af5 · b9f10af5
Commit b9f10af5 authored Sep 17, 2012 by Erik van der Bij Committed by Alessandro Rubini Sep 17, 2012
Hide whitespace changes
Inline Side-by-side

Showing with 2 additions and 2 deletions

fmc-bus.in doc/fmc-bus.in +1 -1

spec-sw.in doc/spec-sw.in +1 -1

No files found.
--- a/doc/fmc-bus.in
+++ b/doc/fmc-bus.in
@@ -99,7 +99,7 @@ may want to force the choice).

 Within this framework, the FMC device is created and registered by the
 carrier driver. For example, the PCI driver for the SPEC card fills a
-data structure for each SPEC that it drivers, and registers an
+data structure for each SPEC that it drives, and registers an
 associated FMC device.  The SVEC driver can do exactly the same for
 the VME carrier (actually, it should do it twice, because the SVEC
 carries two FMC mezzanines.  Similarly, an Etherbone driver will be

--- a/doc/spec-sw.in
+++ b/doc/spec-sw.in
@@ -151,7 +151,7 @@ following steps:
      a minimal @i{sdb}-based verification).
 @item It reads the whole I2C EEPROM found on the mezzanine.
 @item It allocates an @i{fmc_device} structure and registers as
-      a nee device in the @i{fmc} bus.
+      a new device in the @i{fmc} bus.
 @end itemize

 Failure of any of the above steps is fatal.