From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Fri, 12 Jan 2024 22:48:32 +0000 (+0100)
Subject: [3.11] Tutorial: Clarify 'nonzero exit status' in the appendix (GH-112039) (#114000)
X-Git-Tag: v3.11.8~165
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=e276743682d52f3e4b6b9ff5332821473f3de0fc;p=thirdparty%2FPython%2Fcpython.git

[3.11] Tutorial: Clarify 'nonzero exit status' in the appendix (GH-112039) (#114000)

Tutorial: Clarify 'nonzero exit status' in the appendix (GH-112039)
(cherry picked from commit 32f3684b8f18d757945eee67a697cb4a95c697db)

Co-authored-by: Andrew Zipperer <47086307+zipperer@users.noreply.github.com>
---

diff --git a/Doc/tutorial/appendix.rst b/Doc/tutorial/appendix.rst
index 588591fcdb72..4bea0d8a49ce 100644
--- a/Doc/tutorial/appendix.rst
+++ b/Doc/tutorial/appendix.rst
@@ -20,7 +20,7 @@ In interactive mode, it then returns to the primary prompt; when input came from
 a file, it exits with a nonzero exit status after printing the stack trace.
 (Exceptions handled by an :keyword:`except` clause in a :keyword:`try` statement
 are not errors in this context.)  Some errors are unconditionally fatal and
-cause an exit with a nonzero exit; this applies to internal inconsistencies and
+cause an exit with a nonzero exit status; this applies to internal inconsistencies and
 some cases of running out of memory.  All error messages are written to the
 standard error stream; normal output from executed commands is written to
 standard output.