@@ -272,7 +272,7 @@ The instance's values will be different for separate threads.
272272 A class that represents thread-local data.
273273
274274 For more details and extensive examples, see the documentation string of the
275- :mod: `_threading_local ` module::source: `Lib/_threading_local.py `.
275+ :mod: `! _threading_local:source: `Lib/_threading_local.py `.
276276
277277
278278.. _thread-objects :
@@ -285,7 +285,7 @@ thread of control. There are two ways to specify the activity: by passing a
285285callable object to the constructor, or by overriding the:meth: `~Thread.run `
286286method in a subclass. No other methods (except for the constructor) should be
287287overridden in a subclass. In other words, *only * override the
288- :meth: ` ~Thread. __init__:meth: `~Thread.run ` methods of this class.
288+ `` __init__() ` ` and:meth: `~Thread.run ` methods of this class.
289289
290290Once a thread object is created, its activity must be started by calling the
291291thread's:meth: `~Thread.start ` method. This invokes the:meth: `~Thread.run `
@@ -337,7 +337,7 @@ since it is impossible to detect the termination of alien threads.
337337 are:
338338
339339 *group * should be ``None ``; reserved for future extension when a
340- :class: `ThreadGroup ` class is implemented.
340+ :class: `! ThreadGroup
341341
342342 *target * is the callable object to be invoked by the:meth: `run ` method.
343343 Defaults to ``None ``, meaning nothing is called.
@@ -1009,7 +1009,7 @@ This class represents an action that should be run only after a certain amount
10091009of time has passed --- a timer.:class: `Timer ` is a subclass of:class: `Thread `
10101010and as such also functions as an example of creating custom threads.
10111011
1012- Timers are started, as with threads, by calling their:meth: `~ Timer.start
1012+ Timers are started, as with threads, by calling their:meth: `Timer.start <Thread.start> `
10131013method. The timer can be stopped (before its action has begun) by calling the
10141014:meth: `~Timer.cancel ` method. The interval the timer will wait before
10151015executing its action may not be exactly the same as the interval specified by
@@ -1147,10 +1147,10 @@ As an example, here is a simple way to synchronize a client and server thread::
11471147Using locks, conditions, and semaphores in the:keyword: `!with ` statement
11481148-------------------------------------------------------------------------
11491149
1150- All of the objects provided by this module that have:meth: ` acquire ` and
1151- :meth: ` release ` methods can be used as context managers for a:keyword: `with `
1152- statement. The:meth: ` acquire ` method will be called when the block is
1153- entered, and:meth: ` release ` will be called when the block is exited. Hence,
1150+ All of the objects provided by this module that have`` acquire ` ` and
1151+ `` release ` ` methods can be used as context managers for a:keyword: `with `
1152+ statement. The`` acquire ` ` method will be called when the block is
1153+ entered, and`` release ` ` will be called when the block is exited. Hence,
11541154the following snippet::
11551155
11561156 with some_lock: