summaryrefslogtreecommitdiff
path: root/gnu
diff options
context:
space:
mode:
authorVagrant Cascadian <vagrant@debian.org>2019-09-23 12:46:15 -0700
committerVagrant Cascadian <vagrant@debian.org>2019-09-23 13:01:36 -0700
commit0def6a488cb70840f3bba6bd319be2af6f910582 (patch)
tree453bb0da62fa0a68928748f0257b9fda0b684278 /gnu
parent3defa90ddf949328a87645612956d991b9725fa4 (diff)
gnu: sbcl-cl-hooks: Fix typo.
* gnu/packages/lisp (sbcl-cl-hooks)[description]: Fix spelling of "possibilities".
Diffstat (limited to 'gnu')
-rw-r--r--gnu/packages/lisp.scm2
1 files changed, 1 insertions, 1 deletions
diff --git a/gnu/packages/lisp.scm b/gnu/packages/lisp.scm
index ee2d28e579..985ed45465 100644
--- a/gnu/packages/lisp.scm
+++ b/gnu/packages/lisp.scm
@@ -6833,7 +6833,7 @@ Emacs.
In the Common LISP Object System (CLOS), a similar kind of extensibility is
possible using the flexible multi-method dispatch mechanism. It may even seem
-that the concept of hooks does not provide any benefits over the possibilites
+that the concept of hooks does not provide any benefits over the possibilities
of CLOS. However, there are some differences:
@itemize