summaryrefslogtreecommitdiffstats
path: root/sysdep
diff options
context:
space:
mode:
authorMartin Mares <mj@ucw.cz>2000-06-07 15:25:53 +0200
committerMartin Mares <mj@ucw.cz>2000-06-07 15:25:53 +0200
commit58f7d004fddd2cccdb019be59b6cc7a8abe50510 (patch)
tree97d14f24e68ec6d32d114af62dab293a9abeb10c /sysdep
parent38203d789a872077ec174a63a448568725e4715f (diff)
downloadbird-58f7d004fddd2cccdb019be59b6cc7a8abe50510.tar
bird-58f7d004fddd2cccdb019be59b6cc7a8abe50510.zip
Fixes to the progdoc.
Diffstat (limited to 'sysdep')
-rw-r--r--sysdep/unix/io.c4
-rw-r--r--sysdep/unix/krt.c10
2 files changed, 7 insertions, 7 deletions
diff --git a/sysdep/unix/io.c b/sysdep/unix/io.c
index f503bb9..445bc7c 100644
--- a/sysdep/unix/io.c
+++ b/sysdep/unix/io.c
@@ -78,11 +78,11 @@ tracked_fopen(pool *p, char *name, char *mode)
*
* Timers are resources which represent a wish of a module to call
* a function at the specified time. The platform dependent code
- * doesn't guarantee the exact timing, only that a timer function
+ * doesn't guarantee exact timing, only that a timer function
* won't be called before the requested time.
*
* In BIRD, real time is represented by values of the &bird_clock_t type
- * which are integral numbers corresponding to a number of seconds since
+ * which are integral numbers interpreted as a number of seconds since
* a fixed (but platform dependent) epoch. The current time can be read
* from a variable @now with reasonable accuracy.
*
diff --git a/sysdep/unix/krt.c b/sysdep/unix/krt.c
index 2b4117c..317d3f5 100644
--- a/sysdep/unix/krt.c
+++ b/sysdep/unix/krt.c
@@ -26,14 +26,14 @@
* 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
- * attach temporary &rte's to the routing tables, but it cannot harm the rest of
- * BIRD since table synchronization is an atomic process.
+ * We use FIB node flags in the routing table to keep track of route
+ * synchronization status. We also attach temporary &rte's to the routing table,
+ * but it cannot do any harm to the rest of BIRD since table synchronization is
+ * an atomic process.
*
* When starting up, we cheat by looking if there is another
* KRT instance to be initialized later and performing table scan
- * only once for all the instances.
- */
+ * only once for all the instances. */
/*
* If you are brave enough, continue now. You cannot say you haven't been warned.