Skip to content

Commit

Permalink
Updating billing page language (#4413)
Browse files Browse the repository at this point in the history
## What are you changing in this pull request and why?

Adding some language that was missed in the previous update 

## Checklist

- [x] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
and [About
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
so my content adheres to these guidelines.
- [x] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."
  • Loading branch information
matthewshaver authored Nov 8, 2023
2 parents b71c94a + 6f2200a commit 5526f04
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion website/docs/docs/cloud/billing.md
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ On each Project Home page, any user with access to that project can see how many

In addition, you can look at the Job Details page's Insights tab to show how many models are being built per month for that particular job and which models are taking the longest to build.

Any usage data is only an estimate of your usage, and there may be a delay in showing usage data in the product — your final usage for the month will be visible on your monthly statements (statements applicable to Team and Enterprise plans).
Usage information is available to customers on consumption-based plans, and some usage visualizations might not be visible to customers on legacy plans. Any usage data shown in dbt Cloud is only an estimate of your usage, and there could be a delay in showing usage data in the product. Your final usage for the month will be visible on your monthly statements (statements applicable to Team and Enterprise plans).


## Plans and Billing
Expand Down

0 comments on commit 5526f04

Please sign in to comment.