From b9f10af5f10e2e042ce48d26841e54587c979a6e Mon Sep 17 00:00:00 2001
From: Erik Van Der Bij <Erik.van.der.Bij@cern.ch>
Date: Mon, 17 Sep 2012 18:33:15 +0200
Subject: [PATCH] doc: typo fixes
---
doc/fmc-bus.in | 2 +-
doc/spec-sw.in | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/fmc-bus.in b/doc/fmc-bus.in
index 8f4c052..69b1e00 100644
--- 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
diff --git a/doc/spec-sw.in b/doc/spec-sw.in
index d76ed7e..375ec5f 100644
--- 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.
--
GitLab