ethdev: make device operations struct private

[dpdk.git] / doc / guides / prog_guide / rawdev.rst

diff --git a/doc/guides/prog_guide/rawdev.rst b/doc/guides/prog_guide/rawdev.rst
index 54bffc5..a712c7f 100644 (file)
--- a/doc/guides/prog_guide/rawdev.rst
+++ b/doc/guides/prog_guide/rawdev.rst
@@ -32,7 +32,7 @@ Key factors guiding design of the Rawdevice library:
 
 1. Following are some generic operations which can be treated as applicable
    to a large subset of device types. None of the operations are mandatory to
-   be implemented by a driver. Application should also be design for proper
+   be implemented by a driver. Application should also be designed for proper
    handling for unsupported APIs.
 
   * Device Start/Stop - In some cases, 'reset' might also be required which
@@ -43,7 +43,7 @@ Key factors guiding design of the Rawdevice library:
   * Firmware Management - Firmware load/unload/status
 
 2. Application API should be able to pass along arbitrary state information
-   to/fro device driver. This can be achieved by maintaining context
+   to/from device driver. This can be achieved by maintaining context
    information through opaque data or pointers.
 
 Figure below outlines the layout of the rawdevice library and device vis-a-vis
@@ -100,7 +100,7 @@ From the command line using the --vdev EAL option
 
    --vdev 'rawdev_dev1'
 
-Our using the rte_vdev_init API within the application code.
+Or using the rte_vdev_init API within the application code.
 
 .. code-block:: c