From 7d03bd42ff88ddd26c68aa9508316f8b23a205ad Mon Sep 17 00:00:00 2001
From: himazawa <73994521+himazawa@users.noreply.github.com>
Date: Sun, 31 Mar 2024 16:07:14 +0200
Subject: [PATCH] chore: fixed typo

---
 content/posts/xz-backdoor/index.en.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/posts/xz-backdoor/index.en.md b/content/posts/xz-backdoor/index.en.md
index 83d89ea..d02def0 100644
--- a/content/posts/xz-backdoor/index.en.md
+++ b/content/posts/xz-backdoor/index.en.md
@@ -63,12 +63,12 @@ Distributions:
 - [SUSE Tumbleweed](https://news.opensuse.org/2024/03/29/xz-backdoor/)
 - [Kali Linux](https://infosec.exchange/@kalilinux/112180505434870941)
 
-The backdoored package is also contained in the repositories of following package managers:
+The backdoored package is also contained in the repositories of the following package managers:
 - Homebrew
 - MacPorts
 - pkgsrc
 
-At the moment we know that there are checks in the backdoor to [target Linux instances and only x86_64/amd64]() builds so the real number could be downsized, but since the entire situation is unclear I would not reccommend to keep a compromised package on your system.
+At the moment we know that there are checks in the backdoor to [target Linux instances and only x86_64/amd64](https://gist.github.com/thesamesam/223949d5a074ebc3dce9ee78baad9e27#design) builds so the real number could be downsized, but since the entire situation is unclear I would not reccommend to keep a compromised package on your system.
 
 ## Considerations