add note about optimization React did for us

Closes #98

Author: kentcdodds

exercises/06.optimization/01.problem.parallel/README.mdx

@@ -2,6 +2,13 @@
 
 <EpicVideo url="https://www.epicreact.dev/workshops/react-suspense/parallel-loading" />
 
+<callout-warning>
+	The video was recorded with a beta version of React 19 and the behavior you
+	see in the video was fixed in the final release of React 19. Feel free to skip
+	this step if you'd like. Learn more from [issue #98 on the workshop
+	repo](https://github.com/epicweb-dev/react-suspense/issues/98).
+</callout-warning>
+
 👨‍💼 Right now our `ShipDetails` has to wait for the ship's data before we render
 the `ShipImg` component which will then start loading the image. However, we
 can start loading the image as soon as we have the ship's name.

exercises/06.optimization/README.mdx

@@ -2,6 +2,16 @@
 
 <EpicVideo url="https://www.epicreact.dev/workshops/react-suspense/intro-to-optimizations" />
 
+<callout-warning>
+	The problem of waterfalls is something we need to consider as web developers.
+	However, the specific example we use in this exercise was fixed by React 19
+	itself. I recommend you still go through this exercise to learn more about how
+	waterfalls work. We'll get into waterfalls more in the [React Server
+	Components](https://server-components.epicreact.dev/) workshop as well. Learn
+	more from [issue #98 on the workshop
+	repo](https://github.com/epicweb-dev/react-suspense/issues/98).
+</callout-warning>
+
 ## Waterfalls
 
 React Suspense is a powerful way to colocate data requirements with the UI that