[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master 2b6f529: ; * doc/lispref/tips.texi: Fix typo.
From: |
Michael Albinus |
Subject: |
master 2b6f529: ; * doc/lispref/tips.texi: Fix typo. |
Date: |
Mon, 17 Aug 2020 05:41:56 -0400 (EDT) |
branch: master
commit 2b6f52950dbc52f776e065a3716b8bd480d1b922
Author: Michael Albinus <michael.albinus@gmx.de>
Commit: Michael Albinus <michael.albinus@gmx.de>
; * doc/lispref/tips.texi: Fix typo.
---
doc/lispref/tips.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi
index 6292054..1826e8f 100644
--- a/doc/lispref/tips.texi
+++ b/doc/lispref/tips.texi
@@ -956,7 +956,7 @@ multiple sub-sections. Even though that was the only
recommended
approach for a long time, many people have chosen to use multiple
top-level code sections instead. You may chose either style.
-Using multiple top-level code sections has the advanatage that it
+Using multiple top-level code sections has the advantage that it
avoids introducing an additional nesting level but it also means that
the section named @samp{Code} does not contain all the code, which is
awkward. To avoid that, you should put no code at all inside that
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- master 2b6f529: ; * doc/lispref/tips.texi: Fix typo.,
Michael Albinus <=