nano

commit d19915ea44bb3ad03d9262245ac3ac2acda4bb0f
parent 549e37d218ad1d0e52b77c1e61a42b9ef94aa756
Author: Jordi Mallach <jordi@debian.org>
Date:   Wed, 18 Jan 2023 15:58:34 +0100

docs: fix "availabilty" typo in the manual and the nanorc manpage

Diffstat:
M
doc/nano.texi
 | 
2
+-
M
doc/nanorc.5
 | 
2
+-

2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/nano.texi b/doc/nano.texi
@@ -1365,7 +1365,7 @@ Unbinds @code{key} from @code{menu}
 
 Note that @code{bind key "@{function@}" menu} is equivalent to
 @code{bind key function menu}, except that for the latter form
-@command{nano} will check the availabilty of the @code{function}
+@command{nano} will check the availability of the @code{function}
 in the given @code{menu} at startup time (and report an error if
 it does not exist there), whereas for the first form @command{nano}
 will check at execution time that the @code{function} exists but not
diff --git a/doc/nanorc.5 b/doc/nanorc.5
@@ -570,7 +570,7 @@ menus where the key exists when \fBall\fP is used).
 .sp
 Note that \fBbind \fIkey\fR \fB"{\fIfunction\fB}"\fR \fImenu\fR is equivalent
 to \fBbind \fIkey\fR \fIfunction\fR \fImenu\fR, except that for the latter form
-\fBnano\fR will check the availabilty of the \fIfunction\fR in the given \fImenu\fR
+\fBnano\fR will check the availability of the \fIfunction\fR in the given \fImenu\fR
 at startup time (and report an error if it does not exist there), whereas for the
 first form \fBnano\fR will check at execution time that the \fIfunction\fR exists
 but not whether it makes any sense in the current menu.  The user has to take care