Corrected typo in DIONFO acronym.

[ortcan-www.git] / vca / index.mdwn

diff --git a/vca/index.mdwn b/vca/index.mdwn
index 0f992128ea47d8a078dca2e9e57a23c9a3148aa1..eaef1c4b564d689e8d5df25a98417801a3694815 100644 (file)
--- a/vca/index.mdwn
+++ b/vca/index.mdwn
@@ -18,7 +18,7 @@ sources
 
 The build components selection and configuration is controlled by "config.omk"
 file which overrides "config.omk-default". The default sources configuration
-builds VCA support for LinCAN and LinCAN driver is build as well.
+builds VCA support for [[LinCAN|lincan]] and [[LinCAN|lincan]] driver is build as well.
 The option for building library sources relinkable into shared objects (DLLs)
 is required for example modules building on x86_64 and PowerPC targets
 
@@ -55,7 +55,7 @@ without need of recompilation to connect OD data
 with real or simulated hardware data sources. The connection
 is realized by specifying interconnection between
 OD index and subindex entries and named data access
-information structures (DIONFO) provided by loadable
+information structures (DINFO) provided by loadable
 modules. Example of simple example of such module which
 provides two mutually interconnected data items is provided
 in "app/candev/nascanhw/nascanhw.c" source file which is
@@ -120,7 +120,7 @@ You can test most of build components by script
 
     ./test-can-in-konsole
 
-The script  test native build of LinCAN in the KDE konsole window.
+The script  test native build of [[LinCAN|lincan]] in the KDE konsole window.
 This script uses command DCOP scripting capabilities of konsole
 and if it is started from already running console, scripting has
 to be enabled.