From 67165be9dc38d8514c0da419a670d40640f09ae7 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Sun, 6 Jan 2002 07:50:01 +0000 Subject: [PATCH] Spell check. --- doc/ref/intro.texi | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/doc/ref/intro.texi b/doc/ref/intro.texi index bcd5342a3..867b982e2 100644 --- a/doc/ref/intro.texi +++ b/doc/ref/intro.texi @@ -1,4 +1,4 @@ -@c $Id: intro.texi,v 1.1.2.1 2001-08-24 11:58:36 ossau Exp $ +@c $Id: intro.texi,v 1.1.2.2 2002-01-06 07:50:01 ttn Exp $ @page @node What is Guile? @@ -432,7 +432,7 @@ of Guile. If you can, you should use @code{scm_boot_guile} instead. Note that @code{scm_init_guile} does not inform Guile about the command line arguments that should be returned by the Scheme function -@code{comamnd-line}. You can use @code{scm_set_program_arguments} to do +@code{command-line}. You can use @code{scm_set_program_arguments} to do this. @end deftypefun @@ -592,7 +592,7 @@ Scheme programmer. Writing a new version of @code{guile} is inconvenient in this case and it would in fact make the life of the users of your new features needlessly hard. -@c [[ the following is probably a bit longwinded ]] +@c [[ the following is probably a bit long-winded ]] For example, suppose that there is a program @code{guile-db} that is a version of Guile with additional features for accessing a database. @@ -602,7 +602,7 @@ Now suppose that there is also a program @code{guile-gtk} that extends Guile with access to the popular Gtk+ toolkit for graphical user interfaces. People who want to write GUIs in Scheme would have to use @code{guile-gtk}. Now, what happens when you want to write a Scheme -application that uses a GUI to let the user accessa a database? You +application that uses a GUI to let the user access a database? You would have to write a @emph{third} program that incorporates both the database stuff and the GUI stuff. This might not be easy (because @code{guile-gtk} might be a quite obscure program, say) and taking this @@ -617,7 +617,7 @@ possible. You write the new primitive procedures and data types in the normal fashion, and link them into a shared library instead of into a -standalone program. The shared library can then be loaded dynamically +stand-alone program. The shared library can then be loaded dynamically by Guile. @menu @@ -696,7 +696,7 @@ modules, you can group related code together and manage the composition of complete programs from largely independent parts. (Although the module system implementation is in flux, feel free to use it -anyway. Guile will provide reasonable backwards compatability.) +anyway. Guile will provide reasonable backwards compatibility.) Details on the module system beyond this introductory material can be found in @xref{Modules}. @@ -760,7 +760,7 @@ distribute them more easily. Also, explicitly defining the procedures and variables which are exported from a module adds documentation to the source and specifies the interface a module provides. -In Guile, you can create new modules and switch to exisiting modules in +In Guile, you can create new modules and switch to existing modules in order to add bindings to them using the syntactic form @code{define-module}. @@ -857,7 +857,7 @@ Any problems with the installation should be reported to Whenever you have found a bug in Guile you are encouraged to report it to the Guile developers, so they can fix it. They may also be able to -suggest workarounds when it is not possible for you to apply the bugfix +suggest workarounds when it is not possible for you to apply the bug-fix or install a new version of Guile yourself. Before sending in bug reports, please check with the following list that @@ -865,7 +865,7 @@ you really have found a bug. @itemize @bullet @item -Whenever documentation and actual behaviour differ, you have certainly +Whenever documentation and actual behavior differ, you have certainly found a bug, either in the documentation or in the program. @item @@ -905,7 +905,7 @@ You can get the version number by invoking the command $ guile --version Guile 1.4.1 Copyright (c) 1995, 1996, 1997, 2000 Free Software Foundation -Guile may be distributed under the terms of the GNU General Public Licence; +Guile may be distributed under the terms of the GNU General Public License; certain other uses are permitted as well. For details, see the file `COPYING', which is included in the Guile distribution. There is no warranty, to the extent permitted by law.