Grasscutters/mitmproxy
3
0
Fork 0
mirror of https://github.com/Grasscutters/mitmproxy.git synced 2024-11-25 18:03:50 +00:00
Code Issues Projects Releases Wiki Activity

docs: Fix typos

Browse Source
This commit is contained in:
Quentin Pradet 2016-11-14 08:43:32 +04:00
parent 2d0a65a3f4
commit eb7bcb37ec
No known key found for this signature in database
GPG Key ID: E328ACB1EC7E57C2
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/scripting/overview.rst
View File

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