I have found minor misspells in the manual.
--8<-----------------------------cut here---------------start------------->8---
commit 8793b0ce3c9ace917abad3a4644172a4c6d2ac89
Author: Tino Calancha <ccalan...@suse.com>
Date: Wed Mar 24 16:36:35 2021 +0100
Doc fixes
* doc/gst.texi (@node Namespaces): Misspell fix.
* doc/tutorial.texi (@node What happened): Drop 'ing'.
diff --git a/doc/gst.texi b/doc/gst.texi
index a04cd243..a73f9943 100644
--- a/doc/gst.texi
+++ b/doc/gst.texi
@@ -1069,7 +1069,7 @@ already in your image with the ``Bank'' meaning above
(e.g.@: in the
live bank support systems we all run in our images) and you might decide
to start developing @acronym{YAC} [Yet Another C]. Upon starting to
write parse nodes for the compiler, you would find that
-@code{#Statement} is boundk in the banking package. You could replace
+@code{#Statement} is bound in the banking package. You could replace
it with your parse node class, and the bank's @code{Statement} could
remain in the system as an unbound class with full functionality;
however, it could not be accessed anymore at the symbolic level in the
diff --git a/doc/tutorial.texi b/doc/tutorial.texi
index 458f9767..f0a93703 100644
--- a/doc/tutorial.texi
+++ b/doc/tutorial.texi
@@ -100,9 +100,8 @@ Second, it sends the message named @code{printNl} to the
object.
When the object is done processing the message, the code is
done and we get our prompt back.
You'll notice that we didn't say anything about printing
-ing the string, even though that's in fact what happened.
+the string, even though that's in fact what happened.
This was very much on purpose: the code we typed in doesn't
know anything about printing strings. It knew how to get a
string object, and it knew how to send a message to that
--8<-----------------------------cut here---------------start------------->8---
On top of commit: dfe4b5660037c4d178853ee00458a75e51a88563
