Issue #28820: Fix spelling of “practice” as a noun

diff --git a/Doc/howto/urllib2.rst b/Doc/howto/urllib2.rst
index c5003809829e216c389b55742e2f6a0293b07018..f6cba755443bfa1ee786c4dc8ba5ab3a7582917c 100644 (file)
--- a/Doc/howto/urllib2.rst
+++ b/Doc/howto/urllib2.rst
@@ -567,7 +567,7 @@ This document was reviewed and revised by John Lee.
 .. [#] For an introduction to the CGI protocol see
        `Writing Web Applications in Python <http://www.pyzine.com/Issue008/Section_Articles/article_CGIOne.html>`_.
 .. [#] Google for example.
-.. [#] Browser sniffing is a very bad practise for website design - building
+.. [#] Browser sniffing is a very bad practice for website design - building
        sites using web standards is much more sensible. Unfortunately a lot of
        sites still send different versions to different browsers.
 .. [#] The user agent for MSIE 6 is

diff --git a/Doc/tutorial/modules.rst b/Doc/tutorial/modules.rst
index 0ef07a3c786a4ffe7350b27af8d71cdcda404e4f..6fb4ffda2b84e0081760f39322118db3b073b7b8 100644 (file)
--- a/Doc/tutorial/modules.rst
+++ b/Doc/tutorial/modules.rst
@@ -496,7 +496,7 @@ when the ``from...import`` statement is executed.  (This also works when
 ``__all__`` is defined.)
 
 Although certain modules are designed to export only names that follow certain
-patterns when you use ``import *``, it is still considered bad practise in
+patterns when you use ``import *``, it is still considered bad practice in
 production code.
 
 Remember, there is nothing wrong with using ``from Package import

diff --git a/Mac/Modules/cg/CFMLateImport.c b/Mac/Modules/cg/CFMLateImport.c
index 955acfb85bd7fcb1a6bc0d5442f29ad149f0a55a..4da153613f264dc148f253492821cea905b19f91 100644 (file)
--- a/Mac/Modules/cg/CFMLateImport.c
+++ b/Mac/Modules/cg/CFMLateImport.c
@@ -894,7 +894,7 @@ static OSStatus RunRelocationEngine(const FragToFixInfo *fragToFix,
     MoreAssertQ(fragToFix->sectionHeaders != nil);
     MoreAssertQ(fragToFix->loaderSection != nil);
     MoreAssertQ(fragToFix->section0Base != nil);        // Technically, having a nil for these two is not a problem, ...
-    MoreAssertQ(fragToFix->section1Base != nil);        // but in practise it a wildly deviant case and we should know about it.
+    MoreAssertQ(fragToFix->section1Base != nil);        // but in practice it a wildly deviant case and we should know about it.
     MoreAssertQ(importLibrary != nil);
     MoreAssertQ(lookup != nil);