diff options
| author | Michael Albinus <michael.albinus@gmx.de> | 2020-08-17 11:41:46 +0200 |
|---|---|---|
| committer | Michael Albinus <michael.albinus@gmx.de> | 2020-08-17 11:41:46 +0200 |
| commit | 2b6f52950dbc52f776e065a3716b8bd480d1b922 (patch) | |
| tree | 032f4dcb3bb9351b9098452b46d30638ed55ce7f /doc/lispref/tips.texi | |
| parent | 0c86f5592e79100c9f307e878cb41b3c02f1f85a (diff) | |
| download | emacs-2b6f52950dbc52f776e065a3716b8bd480d1b922.tar.gz | |
; * doc/lispref/tips.texi: Fix typo.
Diffstat (limited to 'doc/lispref/tips.texi')
| -rw-r--r-- | doc/lispref/tips.texi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi index 6292054d306..1826e8f7b42 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 |