aboutsummaryrefslogtreecommitdiffstats
path: root/docs/scripting/inlinescripts.rst
diff options
context:
space:
mode:
authorMaximilian Hils <git@maximilianhils.com>2016-04-30 15:25:02 -0700
committerMaximilian Hils <git@maximilianhils.com>2016-04-30 15:25:02 -0700
commitd84fc645a711c5e420c78dd1b49148c8973e9a5a (patch)
tree634b7772ac8218db6b5c1d0f35cffb25987461fd /docs/scripting/inlinescripts.rst
parentf456591db0e3e9d11768cd146b4d446e36415003 (diff)
downloadmitmproxy-d84fc645a711c5e420c78dd1b49148c8973e9a5a.tar.gz
mitmproxy-d84fc645a711c5e420c78dd1b49148c8973e9a5a.tar.bz2
mitmproxy-d84fc645a711c5e420c78dd1b49148c8973e9a5a.zip
docs: minor fixes
Diffstat (limited to 'docs/scripting/inlinescripts.rst')
-rw-r--r--docs/scripting/inlinescripts.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/scripting/inlinescripts.rst b/docs/scripting/inlinescripts.rst
index 89bff2c1..d282dfa6 100644
--- a/docs/scripting/inlinescripts.rst
+++ b/docs/scripting/inlinescripts.rst
@@ -212,7 +212,7 @@ Running scripts on saved flows
Sometimes, we want to run a script on :py:class:`~mitmproxy.models.Flow` objects that are already
complete. This happens when you start a script, and then load a saved set of flows from a file
-(see the "scripted data transformation" example `here <https://mitmproxy.org/doc/mitmdump.html>`_).
+(see the "scripted data transformation" example :ref:`here <mitmdump>`).
It also happens when you run a one-shot script on a single flow through the ``|`` (pipe) shortcut
in mitmproxy.