diff options
| author | Quentin Pradet <quentin.pradet@gmail.com> | 2016-11-14 08:43:32 +0400 |
|---|---|---|
| committer | Quentin Pradet <quentin.pradet@gmail.com> | 2016-11-14 08:43:32 +0400 |
| commit | eb7bcb37ec074233e5684fbf4594478b2041170d (patch) | |
| tree | 60a1d0afb63c49218721512f37a51741afdbcea8 /docs | |
| parent | 2d0a65a3f4fe5482cf6502d5dbbeba8b5125604c (diff) | |
| download | mitmproxy-eb7bcb37ec074233e5684fbf4594478b2041170d.tar.gz mitmproxy-eb7bcb37ec074233e5684fbf4594478b2041170d.tar.bz2 mitmproxy-eb7bcb37ec074233e5684fbf4594478b2041170d.zip | |
docs: Fix typos
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/scripting/overview.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/scripting/overview.rst b/docs/scripting/overview.rst index dfee23a5..7e399c9c 100644 --- a/docs/scripting/overview.rst +++ b/docs/scripting/overview.rst @@ -78,7 +78,7 @@ Logging and the context ----------------------- Scripts should not output straight to stderr or stdout. Instead, the `log -<api.html#mitmproxy.controller.Log>`_ object on the ``ctx`` contexzt module +<api.html#mitmproxy.controller.Log>`_ object on the ``ctx`` context module should be used, so that the mitmproxy host program can handle output appropriately. So, mitmdump can print colorised script output to the terminal, and mitmproxy console can place script output in the event buffer. @@ -134,7 +134,7 @@ purposes. You can use it as follows: Developing scripts ------------------ -Mitmprxoy monitors scripts for modifications, and reloads them on change. When +Mitmproxy monitors scripts for modifications, and reloads them on change. When this happens, the script is shut down (the `done <events.html#done>`_ event is called), and the new instance is started up as if the script had just been loaded (the `start <events.html#start>`_ and `configure |