diff --git a/README.md b/README.md
index aca4915..82eb8c0 100644
--- a/README.md
+++ b/README.md
@@ -164,8 +164,8 @@ A Rive.js `stateMachineInput` object.
 
 ## Examples
 
-The [examples](examples) shows a number of different ways to use Rive React. See the instructions for each example to run locally.
-
+This project uses [Storybook](https://storybook.js.org/) to build examples and API documentation. Check it out at:
+https://rive-app.github.io/rive-react. To run locally, simply run `npm run storybook`.
 
 ## Migration notes
 
diff --git a/examples/stories/AnimationPlayback.stories.mdx b/examples/stories/AnimationPlayback.stories.mdx
index 37bd40c..bd36ad8 100644
--- a/examples/stories/AnimationPlayback.stories.mdx
+++ b/examples/stories/AnimationPlayback.stories.mdx
@@ -95,5 +95,5 @@ While user interaction is a common way to control animation playback for Rives,
 
 ### API-driven playback
 
-Another common way to control animation playback is through API responses. As long as you hold a reference to the `rive` instance returned from the `useRive` hook, you can invoke control methods on that instance in places such as callbacks from API responses. 
+Another common way to control animation playback is through API responses. Imagine an API that you poll for loading progress of a task. Based on that progress response, you may play or stop a given animation. As long as you hold a reference to the `rive` instance returned from the `useRive` hook, you can invoke control methods on that instance in places such as callbacks from API responses.