aboutsummaryrefslogtreecommitdiffstats
path: root/docs/src/content/addons-overview.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/src/content/addons-overview.md')
-rw-r--r--docs/src/content/addons-overview.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/src/content/addons-overview.md b/docs/src/content/addons-overview.md
index 6aa1207e..bfde7f27 100644
--- a/docs/src/content/addons-overview.md
+++ b/docs/src/content/addons-overview.md
@@ -35,7 +35,7 @@ Here, for example, is a command that shows the API documentation for the
mitmproxy's HTTP flow classes:
{{< highlight bash >}}
-pydoc mimtproxy.http
+pydoc mitmproxy.http
{{< /highlight >}}
You will be referring to the mitmproxy API documentation frequently, so keep
@@ -64,11 +64,11 @@ Here are a few things to note about the code above:
finds into the addons mechanism.
- Addons are just objects - in this case our addon is an instance of `Counter`.
- The `request` method is an example of an **event**. Addons simply implement a
- method for each event they wan to handle. Each event has a signature
+ method for each event they want to handle. Each event has a signature
consisting of arguments that are passed to the method. For `request`, this is
an instance of `mitmproxy.http.HTTPFlow`.
- Finally, the `ctx` module is a holdall module that exposes a set of standard
objects that are commonly used in addons. We could pass a `ctx` object as the
first parameter to every event, but we've found it neater to just expose it as
an importable global. In this case, we're using the `ctx.log` object to do our
- logging. \ No newline at end of file
+ logging.