summaryrefslogtreecommitdiff
path: root/doc/ref/api-debug.texi
diff options
context:
space:
mode:
authorJan Synacek <jsynacek@redhat.com>2020-03-10 15:36:03 +0100
committerLudovic Courtès <ludo@gnu.org>2020-03-11 12:14:24 +0100
commit18c7637640c6365e1ce3251d60c78c0c93b45f84 (patch)
tree3343a3f84d19b16d674f4951d4e14f1c49b8b0bb /doc/ref/api-debug.texi
parent7c17655cd3d859bf0c5a86d9782a7788205fc05a (diff)
downloadguile-18c7637640c6365e1ce3251d60c78c0c93b45f84.tar.gz
doc: Fix typo in api-debug.texi.
* doc/ref/api-debug.texi (Debugging): Fix typo. Signed-off-by: Ludovic Courtès <ludo@gnu.org>
Diffstat (limited to 'doc/ref/api-debug.texi')
-rw-r--r--doc/ref/api-debug.texi2
1 files changed, 1 insertions, 1 deletions
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.