More typos corrected

diff --git a/vca/index.mdwn b/vca/index.mdwn
index eaef1c4b564d689e8d5df25a98417801a3694815..2cd9d53756f70227619aca655ce888ceb2e9ae23 100644 (file)
--- a/vca/index.mdwn
+++ b/vca/index.mdwn
@@ -64,7 +64,7 @@ module is controlled by next "config.omk" line
 
     CONFIG_OC_CANSLAVE_NASCANHW=y
 
-The actual build of the libVCA is specified GNu make program
+The actual build of the libVCA is specified GNU make program
 invocation
 
     make
@@ -78,9 +78,10 @@ by underlaying [OMK make system][omk] can be found on its [home page][omk].
 ### Standard EDS and VCA Hardware Connection Configuration HDS Files
 
 The most comprehensive OCERA RT CAN/CANopen components documentation
-is part of WP7.4 deliverable. But it is quite dated and not fully
-complete, same for some code features. The basic CAN part and river
-has been in production use and is tested and documented in separate file.
+is part of [WP7.4 Communication Components V2 deliverable][oceraD74].
+But it is quite dated and not fully complete, same for some code features.
+The basic CAN part and river has been in production use and is tested
+and documented in separate file.
 Because OCERA project code base is not maintained as whole for
 some time, we are in process of separation of the parts which
 have been maintained and has potential for future.
@@ -96,7 +97,7 @@ On the device side, the capability to mimic device dictionary according
 to EDS file is implemented. The HDS is additional description,
 which allows to load shared libraries (DLLs) and map object dictionary
 objects into generic CANopen device binary. This way it is possible
-add new I/O capability without need to rebuild base binary.
+to add new I/O capability without need to rebuild base binary.
 The HDS file maps object dictionary index and subindex to named
 data I/O descriptor DINFOs which are exported by shared library
 object. You can find example of implementation of such module
@@ -108,13 +109,14 @@ The "nascanhw.so" implements two integer I/O variables (DINFOs)
 "input01" and "output01" which are connected together to copy
 "input01" to "output01" variable. The copy action is then notified
 back into "canslave" generic code. This allow to even map these object
-into PDOs and request to sent PDO on its values changes. The "hardware"
-provided variables are mapped into object dictionary by device
+into PDOs and request to sent PDO when the mapped object values changes.
+The "hardware" provided variables are mapped into object dictionary by device
 (Hardware Description File) HDS. The "nascan.hds" is simple example,
 which interconnects the first digital outputs group with with
 the first digital inputs group for DS401 profile device.
 
-    6000:01 /nascanhw/input01 6200:01 /nascanhw/output01
+    6000:01 /nascanhw/input01
+    6200:01 /nascanhw/output01
 
 You can test most of build components by script
 
@@ -158,7 +160,7 @@ students diploma thesis work or contributors.
 
 The PDO can be sent as response to the source value change notification
 over event connectors. This is tested, works and is probably most
-complicated mode if should be done without polling.
+complicated mode if that should be done without polling.
 The SYNC driven and time driven modes needs to be implemented.
 The function \_pdo_hub_event() should be divided into part processed
 at variable change notification, which only marks fields requiring
@@ -181,3 +183,4 @@ of list for PDOs with pending requests.
 
 [omk]:http://rtime.felk.cvut.cz/omk/
 [socketcan]:http://developer.berlios.de/projects/socketcan/
+[oceraD74]:http://www.ocera.org/download/documents/deliverables/ms4-month24.html