Clarify object throughput logic

[evanSegment]

Proposed changes

We don't document the billing logic used to determine object throughput. This leads to customer confusion, and especially pertinent now that some customer are being billed for throughput on volume pricing plans.

Merge timing

• ASAP once approved

[netlify]

✔️ Deploy Preview for segment-docs ready!

🔨 Explore the source changes: 150d15a

🔍 Inspect the deploy log: https://app.netlify.com/sites/segment-docs/deploys/613a3b07ffef830007803123

😎 Browse the preview: https://deploy-preview-1827--segment-docs.netlify.app

[evanSegment]

@markzegarelli , @brookstaylorjr , I made some updates to the copy to correct my usage of the term "throughput". I'm not really happy with the readability of the copy, but the concept of throughput it really complicated and hard to reason about, so I'm not sure what else to do. Could you please review the updated copy?

[markzegarelli]

@evanSegment The copy is clear to me. I think we can ship as-is pending feedback from @brookstaylorjr.

[brookstaylorjr]

Approved! It feels a little weird to me, that we wait so long on the page to actually define what an object is (when we reference them way up in the "Throughput" definition), but ultimately what matters is that the content is somewhere.

[evanSegment]

Thanks guys! I wonder if it would make sense to include this formula higher up the page where we first define throughput? The current copy under #what-is-throughput actually appears to define throughput limit rather than throughput itself!