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

This commit is contained in:
Martin Panter 2016-11-30 10:18:45 +00:00
parent 13cc67946b
commit a52b567a3f
3 changed files with 3 additions and 3 deletions

View File

@ -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

View File

@ -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

View File

@ -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);