summaryrefslogtreecommitdiff
path: root/sysdep/unix/krt.c
diff options
context:
space:
mode:
authorMartin Mares <mj@ucw.cz>2000-06-07 12:29:08 +0000
committerMartin Mares <mj@ucw.cz>2000-06-07 12:29:08 +0000
commit2e9b24211a523c754b9437d6b742d6df304d8aeb (patch)
tree8df91a3bdd2a704006dcb2ed97c49c6e4f36158c /sysdep/unix/krt.c
parente403aa89e50471eb6f2838117887b1207627ae3a (diff)
Spelling fixes to progdoc.
Diffstat (limited to 'sysdep/unix/krt.c')
-rw-r--r--sysdep/unix/krt.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/sysdep/unix/krt.c b/sysdep/unix/krt.c
index 7aee1f6b..2b4117c7 100644
--- a/sysdep/unix/krt.c
+++ b/sysdep/unix/krt.c
@@ -16,14 +16,14 @@
* The whole kernel synchronization is a bit messy and touches some internals
* of the routing table engine, because routing table maintenance is a typical
* example of the proverbial compatibility between different Unices and we want
- * to keep the overhead of our krt business as low as possible and avoid maintaining
+ * to keep the overhead of our KRT business as low as possible and avoid maintaining
* a local routing table copy.
*
* The kernel syncer can work in three different modes (according to system config header):
* Either with a single routing table and single KRT protocol [traditional Unix]
- * or with many routing tables and separate krt protocols for all of them
+ * or with many routing tables and separate KRT protocols for all of them
* or with many routing tables, but every scan including all tables, so we start
- * separate krt protocols which cooperate with each other [Linux 2.2].
+ * separate KRT protocols which cooperate with each other [Linux 2.2].
* In this case, we keep only a single scan timer.
*
* We use FIB node flags to keep track of route synchronization status. We also