aboutsummaryrefslogtreecommitdiff
path: root/Doc/Manual
diff options
context:
space:
mode:
authorSylvestre Ledru <sylvestre.ledru@scilab-enterprises.com>2012-08-08 09:30:08 +0000
committerSylvestre Ledru <sylvestre.ledru@scilab-enterprises.com>2012-08-08 09:30:08 +0000
commitff2df5b288d2cff0953f3836d46106741f3e7bd1 (patch)
tree390c2f5344ce21608dd7af37f88346d5cb50e60d /Doc/Manual
parent7dac1bc5242424d8c9c5610f782aa19a6e07a934 (diff)
downloadswig-ff2df5b288d2cff0953f3836d46106741f3e7bd1.tar.gz
Fix some minor typos in the doc
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@13560 626c5289-ae23-0410-ae9c-e8d60b6d4f22
Diffstat (limited to 'Doc/Manual')
-rw-r--r--Doc/Manual/Go.html2
-rw-r--r--Doc/Manual/Ocaml.html2
2 files changed, 2 insertions, 2 deletions
diff --git a/Doc/Manual/Go.html b/Doc/Manual/Go.html
index cd39d1fa1..78a58df28 100644
--- a/Doc/Manual/Go.html
+++ b/Doc/Manual/Go.html
@@ -498,7 +498,7 @@ into Go types.
<p>Because of limitations in the way output arguments are processed in swig,
a function with output arguments will not have multiple return values.
Instead, you must pass a pointer into the C++ function to tell it where to
-store the ouput value. In go, you supply a slice in the place of the output
+store the output value. In go, you supply a slice in the place of the output
argument.</p>
<p>For example, suppose you were trying to wrap the modf() function in the
diff --git a/Doc/Manual/Ocaml.html b/Doc/Manual/Ocaml.html
index ba8aa5fa9..127be904d 100644
--- a/Doc/Manual/Ocaml.html
+++ b/Doc/Manual/Ocaml.html
@@ -126,7 +126,7 @@ the resulting .ml and .mli files as well, and do the final link with -custom
<p>
-The O'Caml SWIG module now requires you to compile a module (<tt>Swig</tt>)
+The OCaml SWIG module now requires you to compile a module (<tt>Swig</tt>)
separately. In addition to aggregating common SWIG functionality, the Swig
module contains the data structure that represents C/C++ values. This allows
easier data sharing between modules if two or more are combined, because