diff --git a/content/blog/2023-07-25-wrapping-up-my-internship.md b/content/blog/2023-07-25-wrapping-up-my-internship.md
index 17572585..17d87917 100644
--- a/content/blog/2023-07-25-wrapping-up-my-internship.md
+++ b/content/blog/2023-07-25-wrapping-up-my-internship.md
@@ -19,7 +19,7 @@ I interned with the Flatcar team for 2 months from June 5th till July 25th 2023.
 
 The SparkNotes version: we're a community driven, fully open source, minimal, secure by default and always up-to-date container host Linux distribution. It doesn't feature a package manager (no `apt`!), and all OS components reside in a protected read-only partition. The build system for the OS takes after CoreOS' build system which itself is derived from ChromeOS. 
 
-I was tasked to work with adding a systemd-sysext build tool to the Flatcar Container Linux SDK and using it for a Docker sysext image, migrating from Torcx to it. Torcx is a boot-time addon manager used to ship Docker and Containerd. My project was structured mainly around plumbing efforts around Flatcar. I had the opportunity to not just work with the Flatcar team based out of Germany, but also collaborate and help assist community members. It was a great collaborative experience for me and I was able to work with such a diverse team! 
+I was tasked to work with adding a systemd-sysext build tool to the Flatcar Container Linux SDK and using it for a Docker sysext image, migrating from Torcx to it. Torcx is a boot-time addon manager used to ship Docker and Containerd. My project was structured mainly around plumbing efforts around Flatcar. I had the opportunity to not just work with the Flatcar team (distributed between Germany, India, Netherlands and France), but also collaborate and help assist community members. It was a great collaborative experience for me and I was able to work with such a diverse team! 
 
 The OS images we provided were not suitable as base for building Flatcar-specific sysext images: it lacked the package metadata and Portage configuration, in order to keep end user OS image clean. My script now retains this information and allows you to produce systemd-sysexts to extend the system. This script can be used to build a Flatcar sysext image. Recommended to run from image build folder. It was great to see my work on introducing the [build_sysext][build_sysext] script now also being used to build the OEM sysexts (such as for Azure) and being able to review that PR.