summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike DePalatis <mike@depalatis.net>2017-08-03 10:20:42 -0400
committerMariatta <Mariatta@users.noreply.github.com>2017-08-04 00:20:42 +1000
commit87c3c5de731af18a271f4559cd69ccb8d050208f (patch)
treeac4a2e0f18070adb78590c236663036a22e82f00
parent5075416b8fedc5526b643dabc915f7945fa0d969 (diff)
downloadcpython-git-87c3c5de731af18a271f4559cd69ccb8d050208f.tar.gz
Improve grammar in asyncio documentation (GH-2993)
"not only is it .." is the correct form, as opposed to: "not only it is ..."
-rw-r--r--Doc/library/asyncio-dev.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/asyncio-dev.rst b/Doc/library/asyncio-dev.rst
index cc4a14b201..1838eb95a7 100644
--- a/Doc/library/asyncio-dev.rst
+++ b/Doc/library/asyncio-dev.rst
@@ -52,7 +52,7 @@ Cancellation
------------
Cancellation of tasks is not common in classic programming. In asynchronous
-programming, not only it is something common, but you have to prepare your
+programming, not only is it something common, but you have to prepare your
code to handle it.
Futures and tasks can be cancelled explicitly with their :meth:`Future.cancel`