aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPierre Neidhardt <mail@ambrevar.xyz>2020-05-06 21:35:35 +0200
committerPierre Neidhardt <mail@ambrevar.xyz>2020-05-07 09:23:06 +0200
commitd35a0f14528166cd0d76abab409e3d74c79dadd8 (patch)
tree1e1c1993ed1adae82049d1309a3f31120b029883
parent1339a03b6d28c0b1726b501bde27a807f960edff (diff)
downloadpatches-d35a0f14528166cd0d76abab409e3d74c79dadd8.tar
patches-d35a0f14528166cd0d76abab409e3d74c79dadd8.tar.gz
gnu: sbcl-trivial-backtrace: Fix typo in description.
* gnu/packages/lisp-xyz.scm (sbcl-trivial-backtrace)[description]: Replace "On" with "One".
-rw-r--r--gnu/packages/lisp-xyz.scm2
1 files changed, 1 insertions, 1 deletions
diff --git a/gnu/packages/lisp-xyz.scm b/gnu/packages/lisp-xyz.scm
index 3d2cff2834..fc15bf40a9 100644
--- a/gnu/packages/lisp-xyz.scm
+++ b/gnu/packages/lisp-xyz.scm
@@ -3548,7 +3548,7 @@ client and server.")
(home-page "https://common-lisp.net/project/trivial-backtrace/")
(synopsis "Portable simple API to work with backtraces in Common Lisp")
(description
- "On of the many things that didn't quite get into the Common Lisp
+ "One of the many things that didn't quite get into the Common Lisp
standard was how to get a Lisp to output its call stack when something has
gone wrong. As such, each Lisp has developed its own notion of what to
display, how to display it, and what sort of arguments can be used to