aboutsummaryrefslogtreecommitdiffstats
path: root/docs/scripting
diff options
context:
space:
mode:
authorAldo Cortesi <aldo@corte.si>2016-10-30 17:21:12 +1300
committerGitHub <noreply@github.com>2016-10-30 17:21:12 +1300
commit897d5ddc87c2a30a6740b32217959e8bbce690cc (patch)
tree33503b29d0d075f46e2230090367d9362db79ec4 /docs/scripting
parentb229d470c444a84e20c630bd73096b6f5b4e2cdc (diff)
parent7a6bae336b35175b26494bf86fe740e61a34723f (diff)
downloadmitmproxy-897d5ddc87c2a30a6740b32217959e8bbce690cc.tar.gz
mitmproxy-897d5ddc87c2a30a6740b32217959e8bbce690cc.tar.bz2
mitmproxy-897d5ddc87c2a30a6740b32217959e8bbce690cc.zip
Merge pull request #1691 from cortesi/consoleclean1
console: various cleanups
Diffstat (limited to 'docs/scripting')
-rw-r--r--docs/scripting/overview.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/scripting/overview.rst b/docs/scripting/overview.rst
index b820538e..dfee23a5 100644
--- a/docs/scripting/overview.rst
+++ b/docs/scripting/overview.rst
@@ -80,13 +80,13 @@ 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
should be used, so that the mitmproxy host program can handle output
-appropriately. So, mitmdump can print colorised sript output to the terminal,
+appropriately. So, mitmdump can print colorised script output to the terminal,
and mitmproxy console can place script output in the event buffer.
Here's how this looks:
-.. literalinclude:: ../../examples/logging.py
- :caption: :src:`examples/logging.py`
+.. literalinclude:: ../../examples/context_logging.py
+ :caption: :src:`examples/context_logging.py`
:language: python
The ``ctx`` module also exposes the mitmproxy master object at ``ctx.master``