diff --git a/website/assets/images/2023-04-28-getpid-ptrace-vs-systrap-unopt.svg b/website/assets/images/2023-04-28-getpid-ptrace-vs-systrap-unopt.svg
deleted file mode 100644
index 84d8fbc3c..000000000
--- a/website/assets/images/2023-04-28-getpid-ptrace-vs-systrap-unopt.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/website/assets/images/2023-04-28-getpid-ptrace-vs-systrap-unoptimized.svg b/website/assets/images/2023-04-28-getpid-ptrace-vs-systrap-unoptimized.svg
new file mode 100644
index 000000000..671e0e696
--- /dev/null
+++ b/website/assets/images/2023-04-28-getpid-ptrace-vs-systrap-unoptimized.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/website/blog/2023-04-28-systrap-release.md b/website/blog/2023-04-28-systrap-release.md
index 801f80a4a..b62bda9a7 100644
--- a/website/blog/2023-04-28-systrap-release.md
+++ b/website/blog/2023-04-28-systrap-release.md
@@ -77,7 +77,7 @@ populates shared memory regions, and requests the sentry to handle the requested
system call. This alone proved to be faster than using `PTRACE_SYSEMU`, as
demonstrated by the `getpid` benchmark:
-{:width="100%"}
+{:width="100%"}
Can we make it even faster? Recall what the main purpose of our signal handler
is: to send a request to the sentry via shared memory. To do that, the sandboxed