Update migration.mdx

Author: JonnyBurger

packages/docs/docs/client-side-rendering/migration.mdx

@@ -31,10 +31,6 @@ Start using the [`useDelayRender()`](/docs/use-delay-render) hook instead, which
 
 Unlike server-side rendering, where video and audio assets are downloaded in a Node.js process, and where images can be captured even if they are [tainted](https://developer.mozilla.org/en-US/docs/Web/HTML/How_to/CORS_enabled_image#security_and_tainted_canvases), in client-side rendering, CORS is enforced and images and canvas may not be tainted.
 
-### Why CORS is required
-
-Client-side rendering draws images to a `<canvas>` element. For security reasons, browsers restrict access to image data from different origins. If an image from another domain is drawn to a canvas without proper CORS headers, the canvas becomes "tainted" and its contents cannot be extracted.
-
 ### Common error messages
 
 If you use an image that doesn't support CORS, you'll see an error like:
@@ -53,14 +49,6 @@ The image is in a broken state.
 This usually means the image failed to load - check that the URL is valid and accessible.
 ```
 
-### Solutions
-
-1. **Host images with CORS headers**: Ensure your image server responds with `Access-Control-Allow-Origin: *` or a specific origin.
-
-2. **Self-host images**: Download remote images and serve them from your own domain.
-
-3. **Use a CORS proxy**: Route requests through a proxy that adds CORS headers.
-
 ## Use `@remotion/media`
 
 The only video and audio tags that are supported are [`<Video>`](/docs/media/video) and [`<Audio>`](/docs/media/audio) from `@remotion/media`.