X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=README.hwtables;h=2b005539a945533cc67bdd471a2d29cc1b32c4d2;hb=refs%2Fheads%2Ffor-nox%2F0.4;hp=e0b2a038ff97f0d56b68dbcb91d4ddd55db2158c;hpb=a0fd7dde11703233dd3e5a542fc674dd83bafcfb;p=sliver-openvswitch.git

diff --git a/README.hwtables b/README.hwtables
index e0b2a038f..2b005539a 100644
--- a/README.hwtables
+++ b/README.hwtables
@@ -17,7 +17,7 @@ hardware table module is loaded (and before it is unloaded) will take
 advantage of hardware switching features.
 
 Creating a hardware table module is straightforward.  Create a
-directory in the openflow source tree named datapath/hwtable-NAME,
+directory in the openflow source tree named datapath/hwtable_NAME,
 where NAME identifies the hardware that the module supports.  Populate
 that directory with the C source files that comprise the module, plus
 a file named Modules.mk that specifies how to build the module.  This
@@ -33,6 +33,6 @@ the OpenFlow configure script command as the argument to
 
 Each hardware table module's code is encapsulated in a directory, so
 it is easy to separate a hardware table implementation from OpenFlow.
-Simply package up the contents of the hwtable-NAME directory and
+Simply package up the contents of the hwtable_NAME directory and
 distribute it for builders to extract into their distribution
 directory.