diff --git a/blog/posts/pwa-vs-iwa.md b/blog/posts/pwa-vs-iwa.md
index 97eb05b2cb..b4735e8973 100644
--- a/blog/posts/pwa-vs-iwa.md
+++ b/blog/posts/pwa-vs-iwa.md
@@ -30,8 +30,8 @@ Isolated Web Apps (IWAs) build on the work done on PWAs and [Web Packaging](http
 Google [distinguishes](https://chromeos.dev/en/web/isolated-web-apps) between the drive by web, PWAs, and IWAs. The drive by web requires more conservative access to the system as the most accessible and is therefore least trusted. PWAs are a bit more trusted and can integrate a bit more deeply into the system as a result. IWAs are the most trusted and, as such, can have deeper access into the system and more powerful capabilities.
 
 <figure markdown>
-  ![Diagram showing the drive by web, a PWA, then a dotted line separating them from IWAs](../assets/images/iwa-the-future-of-web-apps/iwa-diagram.png)
-  <figcaption>source: <a href="https://chromeos.dev/en/web/isolated-web-apps">Google</a></figcaption>
+  ![Diagram showing the drive by web, a PWA, and then a dotted line separating them from IWAs](../assets/images/iwa-the-future-of-web-apps/iwa-diagram.png)
+  <figcaption>source: <a href="https://chromeos.dev/en/web/isolated-web-apps">chromeos.dev</a></figcaption>
 </figure>
 
 This higher security assurance from isolated and signed web applications and the inherently more trusted nature of a natively installed app will allow for IWAs to safely access APIs which wouldn't be safe to allow normal websites to access, like [Direct Sockets](https://github.com/WICG/direct-sockets/blob/main/docs/explainer.md).