summaryrefslogtreecommitdiff
path: root/doc/emacs
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2023-07-25 16:49:18 +0300
committerEli Zaretskii <eliz@gnu.org>2023-07-30 10:22:42 +0300
commitcb1f7db249096bf58e28fb586d7ef926536dcb09 (patch)
tree7ae262d98360c09aee856e5c89383f3175692a05 /doc/emacs
parent4a687bcc20d4d5a3297bfaecd6bd9d400ba39195 (diff)
downloademacs-cb1f7db249096bf58e28fb586d7ef926536dcb09.tar.gz
emacs-cb1f7db249096bf58e28fb586d7ef926536dcb09.tar.bz2
emacs-cb1f7db249096bf58e28fb586d7ef926536dcb09.zip
; Minor documentation fixes
* src/character.c (Fstring_width): Doc fix. * doc/emacs/trouble.texi (Understanding Bug Reporting): Fix typo (bug#64854). (cherry picked from commit f6e4e77d23d0be79be83ef41c3ea9acd5c983af2)
Diffstat (limited to 'doc/emacs')
-rw-r--r--doc/emacs/trouble.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi
index bccdea72b19..d2e8ac3452a 100644
--- a/doc/emacs/trouble.texi
+++ b/doc/emacs/trouble.texi
@@ -706,7 +706,7 @@ produced by typing those commands.
for the detailed raw data. Reporting the facts is straightforward,
but many people strain to posit explanations and report them instead
of the facts. If the explanations are based on guesses about how
-Emacs is implemented, they night not be useful; meanwhile, lacking the
+Emacs is implemented, they might not be useful; meanwhile, lacking the
facts, we will have no real information about the bug. If you want to
actually @emph{debug} the problem, and report explanations that are
more than guesses, that is useful---but please include the raw facts