diff --git a/README.md b/README.md
index 804f869..c3f392c 100644
--- a/README.md
+++ b/README.md
@@ -31,7 +31,7 @@ exports those metrics in Prometheus format.
Here's an overview of the checks performed by kubenurse, which are exposed as
labels for the various duration/error prometheus metrics.
-![kubenurse request types](./doc/kubenurse.svg)
+![kubenurse request types](./doc/kubenurse.png)
## Deployment
@@ -250,7 +250,7 @@ To combat this, a node filtering feature was implemented, which works as follows
Here's an example with 6 nodes, where each node queries the next 3 nodes:
-![node filtering drawing](./doc/kubenurse_node_filtering.svg)
+![node filtering drawing](./doc/kubenurse-node-filtering.png)
Thanks to this, every node is making queries to the same 10 nodes, unless one
of those nodes disappears, in which case kubenurse will pick the next node in
diff --git a/doc/kubenurse-node-filtering.png b/doc/kubenurse-node-filtering.png
new file mode 100644
index 0000000..f782972
Binary files /dev/null and b/doc/kubenurse-node-filtering.png differ
diff --git a/doc/kubenurse.png b/doc/kubenurse.png
new file mode 100644
index 0000000..8dbce22
Binary files /dev/null and b/doc/kubenurse.png differ
diff --git a/doc/kubenurse.svg b/doc/kubenurse.svg
deleted file mode 100644
index 92b646a..0000000
--- a/doc/kubenurse.svg
+++ /dev/null
@@ -1,24 +0,0 @@
-
\ No newline at end of file
diff --git a/doc/kubenurse_node_filtering.svg b/doc/kubenurse_node_filtering.svg
deleted file mode 100644
index eb2289a..0000000
--- a/doc/kubenurse_node_filtering.svg
+++ /dev/null
@@ -1,24 +0,0 @@
-
\ No newline at end of file