@@ -1096,7 +1096,7 @@ Python 3.2 or later.
10961096
10971097.. _custom-logrecord :
10981098
1099- Customising ``LogRecord ``
1099+ Customizing ``LogRecord ``
11001100-------------------------
11011101
11021102Every logging event is represented by a :class: `LogRecord ` instance.
@@ -1313,7 +1313,7 @@ of the Django documentation.
13131313
13141314.. _cookbook-rotator-namer :
13151315
1316- Using a rotator and namer to customise log rotation processing
1316+ Using a rotator and namer to customize log rotation processing
13171317--------------------------------------------------------------
13181318
13191319An example of how you can define a namer and rotator is given in the following
@@ -1694,14 +1694,14 @@ Python used.
16941694
16951695.. currentmodule :: logging.config
16961696
1697- Customising handlers with :func: `dictConfig `
1697+ Customizing handlers with :func: `dictConfig `
16981698--------------------------------------------
16991699
1700- There are times when you want to customise logging handlers in particular ways,
1700+ There are times when you want to customize logging handlers in particular ways,
17011701and if you use :func: `dictConfig ` you may be able to do this without
17021702subclassing. As an example, consider that you may want to set the ownership of a
17031703log file. On POSIX, this is easily done using :func: `shutil.chown `, but the file
1704- handlers in the stdlib don't offer built-in support. You can customise handler
1704+ handlers in the stdlib don't offer built-in support. You can customize handler
17051705creation using a plain function such as::
17061706
17071707 def owned_file_handler(filename, mode='a', encoding=None, owner=None):
0 commit comments