From: Martin Panter <vadmium+py@gmail.com>
Date: Wed, 30 Nov 2016 10:18:45 +0000 (+0000)
Subject: Issue #28820: Fix spelling of “practice” as a noun
X-Git-Tag: v2.7.13rc1~20
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a52b567a3f36004cc48f91feeb708548c20e57d5;p=thirdparty%2FPython%2Fcpython.git

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

diff --git a/Doc/howto/urllib2.rst b/Doc/howto/urllib2.rst
index c5003809829e..f6cba755443b 100644
--- 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 0ef07a3c786a..6fb4ffda2b84 100644
--- 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 955acfb85bd7..4da153613f26 100644
--- 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);