Minor documentation typos.
Peace
--Devon
diff -Bbdur dist/bigloo4.1a/manuals/eval.texi hack/bigloo4.1a/manuals/eval.texi
--- dist/bigloo4.1a/manuals/eval.texi 2013-09-18 17:10:15.000000000 +0800
+++ hack/bigloo4.1a/manuals/eval.texi 2013-10-30 09:47:31.000000000 +0800
@@ -53,7 +53,7 @@
By default the evaluator assumes that operators from the standard
library (e.g., @code{+}, @code{car}) are immutable. Hence, it optimizes
-these operators calls. This optimization can be disables using
+these operators' calls. This optimization can be disabled using
the @code{bigloo-eval-strict-module} parameter described in
the chapter describing the parameters (see @pxref{Parameters}).
diff -Bbdur dist/bigloo4.1a/manuals/fthread.texi
hack/bigloo4.1a/manuals/fthread.texi
--- dist/bigloo4.1a/manuals/fthread.texi 2013-09-18 17:10:15.000000000
+0800
+++ hack/bigloo4.1a/manuals/fthread.texi 2013-10-26 20:57:26.000000000
+0800
@@ -76,7 +76,7 @@
concurrently competing to gain access to the processor, in order to
execute.
-Threads are a basic mean for concurrent programming, and are widely
+Threads are a basic means for concurrent programming, and are widely
used in operating systems. At language level, threads offer a way to
structure programs by decomposing systems in several concurrent
components; in this respect, threads are useful for modularity.
@@ -141,18 +141,18 @@
@deffn {SRFI-18 function} thread-start! @var{thread} [@var{scheduler}]
Runs a thread created with @code{make-thread}. If @var{scheduler} is
-provided, the @var{thread} is started this particular scheduler. Otherwise,
+provided, the @var{thread} is started in this particular scheduler. Otherwise,
it is started in the current scheduler (see Section @ref{Scheduler}).
Threads are started at the beginning of @emph{reactions}
(see Section @ref{Scheduler}).
@end deffn
@deffn {SRFI-18 function} thread-yield!
-The current thread @emph{cooperates}. That is, it is suspend for the
+The current thread @emph{cooperates}. That is, it is suspended for the
@emph{reaction} and the scheduler selects a new thread to be resumed. The
scheduler resumes the next avaliable thread. If there is only one
thread started in the scheduler, the same thread is resumed.
-A @emph{reaction} correspond to the invocation of a @code{scheduler-react!}
+A @emph{reaction} corresponds to the invocation of a @code{scheduler-react!}
call (see Section @ref{Scheduler}).
@end deffn
@@ -182,8 +182,8 @@
@end deffn
@deffn {SRFI-18 function} thread-join! @var{thread} [@var{timeout}
[@var{timeout-val}]]
-The current thread waits until the @var{thread} terminates or until
-the @var{timeout} is reached (when supplied). If the @var{timeout} is
+The current thread waits until @var{thread} terminates or until
+@var{timeout} is reached (when supplied). If the @var{timeout} is
reached, @code{thread-join!} returns @var{timeout-val}. If @var{thread}
terminates, @code{thread-join!} returns the end-result of the @var{thread}
or the end-exception if that thread terminates abnormally.
@@ -228,7 +228,7 @@
@deffn {Bigloo function} thread-await! @var{signal} [@var{timeout}]
Blocks the thread until @var{signal} has been broadcast or until
-@var{timeout} is elapsed. The function @code{thread-await!} returns
+@var{timeout} has elapsed. The function @code{thread-await!} returns
the value associated with the previous emissions of the signal that
took place during the reaction.
@@ -253,13 +253,13 @@
@end smalllisp
The function @code{thread-await!} cannot be used to intercept all the signals
-broadcasted during a reaction. This is illustrated by the following example
-were obviously @code{thread-await!} cannot intercept the emission of the
+broadcast during a reaction. This is illustrated by the following example
+where obviously @code{thread-await!} cannot intercept the emission of the
signal:
@smalllisp
(thread-start! (instantiate::fthread (body (lambda ()
- (tread-await! 'foo)
+ (thread-await! 'foo)
(broadcast! 'foo 1)))))
(thread-start! (instantiate::fthread (body (lambda ()
(broadcast! 'foo 2)))))
diff -Bbdur dist/bigloo4.1a/manuals/hash.texi hack/bigloo4.1a/manuals/hash.texi
--- dist/bigloo4.1a/manuals/hash.texi 2013-09-18 17:10:15.000000000 +0800
+++ hack/bigloo4.1a/manuals/hash.texi 2013-10-30 09:54:45.000000000 +0800
@@ -55,7 +55,7 @@
incorrect hashtable uses because excessive expansion is generally the
signs of an incorrect behavior. Excessive expansions, cause the
garbage collector to crash at some point. This debugging feature can
-be disable by specifies a negative max length, in which case, no check
+be disabled by specifying a negative max length, in which case, no check
is performed at runtime.
The argument @var{bucket-expansion} controls how @var{max-bucket-len} is
diff -Bbdur dist/bigloo4.1a/manuals/io.texi hack/bigloo4.1a/manuals/io.texi
--- dist/bigloo4.1a/manuals/io.texi 2013-09-18 17:10:15.000000000 +0800
+++ hack/bigloo4.1a/manuals/io.texi 2013-10-30 09:41:19.000000000 +0800
@@ -789,7 +789,7 @@
@item @code{~r} A return (@code{#\Return}) is inserted.
@item @code{~v} The corresponding value is inserted into the string
as if printed with display followed by a newline. This tag is hence
-equivalent to the sequence @code{~v~n}.
+equivalent to the sequence @code{~a~n}.
@item @code{~c} The corresponding value must be a character and is
inserted into the string as if printed with write-char.
@item @code{~x}, @code{~o}, @code{~b} The corresponding value must
