summaryrefslogtreecommitdiff
path: root/doc/contributing.texi
diff options
context:
space:
mode:
authorEfraim Flashner <[email protected]>2025-02-19 11:12:45 +0200
committerEfraim Flashner <[email protected]>2025-02-19 11:28:40 +0200
commita641396502603458c492cc8d4c804930816e4424 (patch)
tree0cc848394866610a4104540c43eeb1afc83964e1 /doc/contributing.texi
parente5829034814bfb789b4fa94ab3a6c4bdd27bb56e (diff)
doc: Fix some misspellings.
Change-Id: I567aec7b1fac91234f46886c35affa6bd6e582d9
Diffstat (limited to 'doc/contributing.texi')
-rw-r--r--doc/contributing.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/contributing.texi b/doc/contributing.texi
index c94ae940fa..ab4f30d54b 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -3465,9 +3465,9 @@ Guile does not know in which order you intended the string to be read, so it
will substitute the symbols in the same order as the English sentence.
As an example, you cannot translate @samp{package '~a' has been superseded by
-'~a'} by @samp{'~a' superseeds package '~a'}, because the meaning would be
+'~a'} by @samp{'~a' supersedes package '~a'}, because the meaning would be
reversed. If @var{foo} is superseded by @var{bar}, the translation would read
-@samp{'foo' superseeds package 'bar'}. To work around this problem, it
+@samp{'foo' supersedes package 'bar'}. To work around this problem, it
is possible to use more advanced formatting to select a given piece of data,
instead of following the default English order. @xref{Formatted Output,,,
guile, GNU Guile Reference Manual}, for more information on formatting in Guile.