Update v0.1.0.md

Author: baseplate-admin

apps/docs/docs/upgrade-guides/v0.1.0.md

@@ -16,7 +16,7 @@ docker compose up -d
 
 
 ## Breaking changes
-### Chithi frontend needs COEP (Cross-Origin-Embedder-Policy)
+### Chithi frontend needs COOP and COEP headers
 In previous version of `chithi`, we didn't do in browser convertion of files.
 
 Now `chithi` supports the following transformations:
@@ -25,13 +25,15 @@ Now `chithi` supports the following transformations:
 * HEIC -> PNG (using [heic-to](https://www.npmjs.com/package/heic-to))
 * JXL -> PNG (using [@jsquash/jxl](https://www.npmjs.com/package/@jsquash/jxl))
 
-To accomodate these with wasm threads, we have to enable COEP header.
+To accomodate these with wasm threads, we have to enable [COOP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cross-Origin-Opener-Policy) and [COEP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cross-Origin-Embedder-Policy) headers.
+
+You can read an [article on web.dev](https://web.dev/articles/why-coop-coep) on why COOP and COEP headers are needed.
 
 !!! info
 
-    Webassembly is really complex to get into. If you want some more information on this, you can read the [WASM threads spec](https://github.com/webassembly/threads)
+    While the site itself does not change much in meaningful way, having no COOP and COEP headers mean your fonts and other assets wont load properly.
 
-That means your reverse proxy of choice must add the security headers, otherwise the static assets like worker and fonts wont load properly.
+That means your reverse proxy of choice must add the security headers.
 
 Please see the deployment section for your reverse proxy of choice.