bug#40014: [PATCH] typo in api-debug.texi
Jan Synacek <[email protected]>
| Newsgroups | gmane.lisp.guile.bugs |
|---|---|
| Message-ID | <CAPsXM8XUaXJMntAEvatOyx8+bG3NDfxuYQztYQ0OHYg0yaj-pg@mail.gmail.com> |
See attached patch. -- Jan Synacek Software Engineer, Red Hat
0001-texinfo-Fix-typo-in-api-debug.texi.patch
(application/x-patch, 895 B)
From 8617b6a94054aafc4a58cd1e5581154e1e9ea353 Mon Sep 17 00:00:00 2001 From: Jan Synacek <[email protected]> Date: Tue, 10 Mar 2020 15:36:03 +0100 Subject: [PATCH] texinfo: Fix typo in api-debug.texi --- doc/ref/api-debug.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/ref/api-debug.texi b/doc/ref/api-debug.texi index d7d0412f7..6718752fa 100644 --- a/doc/ref/api-debug.texi +++ b/doc/ref/api-debug.texi @@ -9,7 +9,7 @@ @cindex Debugging In order to understand Guile's debugging facilities, you first need to -understand a little about how Guile represent the Scheme control stack. +understand a little about how Guile represents the Scheme control stack. With that in place we explain the low level trap calls that the virtual machine can be configured to make, and the trap and breakpoint infrastructure that builds on top of those calls. -- 2.21.1