diff --git a/src/content/docs/stream/pricing.mdx b/src/content/docs/stream/pricing.mdx
index 1a3033b79d7c3e7..37bf47b37448de5 100644
--- a/src/content/docs/stream/pricing.mdx
+++ b/src/content/docs/stream/pricing.mdx
@@ -30,6 +30,7 @@ Storage is not consumed by:
 - Expired Direct Creator upload links
 - Deleted videos
 - Downloadable files generated for [MP4 Downloads](/stream/viewing-videos/download-videos/)
+- Multiple quality levels that Stream generates for each uploaded original
 
 Storage consumption is rounded up to the second of video duration; file size does not matter. Video stored in Stream does not incur additional storage fees from other storage products such as R2.
 
@@ -45,31 +46,31 @@ Delivery is a post-paid, usage-based pricing dimension billed at $1 per 1,000 mi
 
 Delivery is counted for the following uses:
 
-- Playback via HLS or DASH
+- Playback on the web or an app using [Stream's built-in player](/stream/viewing-videos/using-the-stream-player/) or the [HLS or DASH manifests](/stream/viewing-videos/using-own-player/)
 - MP4 Downloads
 - Simulcasting via SRT or RTMP live outputs
 
 Delivery is counted by HTTP requests for video segments or parts of the MP4. Therefore:
 
 - Client-side preloading and buffering is counted as billable delivery.
-- Content played from client-side/browser cache is not billable, like a short looping video. Some mobile app player libraries do not cache HLS segments by default.
+- Content played from client-side/browser cache is _not_ billable, like a short looping video. Some mobile app player libraries do not cache HLS segments by default.
 - MP4 Downloads are billed by percentage of the file delivered.
 
-Minutes delivered for web playback (HLS and DASH) are rounded to the _segment_ length: for uploaded content, segments are four seconds. Live broadcast and recording segments are determined by the keyframe interval or GOP size of the original broadcast.
+Minutes delivered for web playback (Stream Player, HLS, and DASH) are rounded to the _segment_ length: for uploaded content, segments are four seconds. Live broadcast and recording segments are determined by the keyframe interval or GOP size of the original broadcast.
 
 ## Example scenarios
 
-**Two people each watch thirty minutes of a broadcast. How much would it cost?**
+**Two people each watch thirty minutes of a video or live broadcast. How much would it cost?**
 
 This will result in 60 minutes of Minutes Delivered usage (or $0.06). Stream bills on minutes of video delivered, not per viewer.
 
 **I have a really large file. Does that cost more?**
 
-The cost to store a video is based only on its duration, not its file size. If the file is within the [30GB max file size limitation](/stream/faq/#is-there-a-limit-to-the-amount-of-videos-i-can-upload), it will be accepted. Be sure to use an upload method like Upload from Link or TUS that handles large files well.
+The cost to store a video is based only on its duration, not its file size. If the file is within the [30GB max file size limitation](/stream/faq/#is-there-a-limit-to-the-amount-of-videos-i-can-upload), it will be accepted. Be sure to use an [upload method](/stream/uploading-videos/) like Upload from Link or TUS that handles large files well.
 
 **If I make a Direct Creator Upload link with a maximum duration (`maxDurationSeconds`) of 600 seconds which expires in 1 hour, how is storage consumed?**
 
-- Ten minutes will be subtracted from your available storage immediately.
+- Ten minutes (600 seconds) will be subtracted from your available storage immediately.
 - If the link is unused in one hour, those 10 minutes will be released.
 - If the creator link is used to upload a five minute video, when the video is uploaded and processed, the 10 minute reservation will be released and the true five minute duration of the file will be counted.
 - If the creator link is used to upload a five minute video but it fails to encode, the video will be marked as errored, the reserved storage will be released, and no storage use will be counted.