From 5d9c86e340b40379d18ffeb7ce1739e07bdeb536 Mon Sep 17 00:00:00 2001
From: "Miss Islington (bot)"
 <31488909+miss-islington@users.noreply.github.com>
Date: Sat, 24 Jul 2021 03:30:25 -0700
Subject: [PATCH] bpo-44713: [doc fix]: typo in subprocess.rst (GH-27297)
 (#27327)

This fixes a small typo. The code fragment should not be quoted. Thank you
@merwok for the feedback.
(cherry picked from commit 7d25254cf0763b62f4c4a3019e56385cab597b9f)

Co-authored-by: Jack DeVries <58614260+jdevries3133@users.noreply.github.com>
---
 Doc/library/subprocess.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Doc/library/subprocess.rst b/Doc/library/subprocess.rst
index 67754a7299d..2e9540ec48c 100644
--- a/Doc/library/subprocess.rst
+++ b/Doc/library/subprocess.rst
@@ -662,7 +662,7 @@ execute, will be re-raised in the parent.
 
 The most common exception raised is :exc:`OSError`.  This occurs, for example,
 when trying to execute a non-existent file.  Applications should prepare for
-:exc:`OSError` exceptions. Note that, when ``"shell=True"``, :exc:`OSError`
+:exc:`OSError` exceptions. Note that, when ``shell=True``, :exc:`OSError`
 will be raised by the child only if the selected shell itself was not found.
 To determine if the shell failed to find the requested application, it is
 necessary to check the return code or output from the subprocess.