-
Notifications
You must be signed in to change notification settings - Fork 159
terminology fix - invoices instead of receipts #2614
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Warning It looks like this PR modifies one or more |
🔍 Preview links for changed docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🚀
Deferring the "statements" question to Brianne and Eric.
@briannebartlett how would you like us to position this in the docs? "statements, invoices, and receipts" everywhere we said "receipts"? |
@shainaraskas How many other places is it listed? I'd have to check with the Netsuite team but I'd imagine they get an actual receipt from the credit card processor and these artifacts are different. I'd recommend updating to invoices and statements if we're referring to what's available in the Cloud Billing History section specifically. |
@briannebartlett this is just referring to cloud surfaces, so I'll update it to "invoices and statements" as you recommended. |
Warning It looks like this PR modifies one or more |
"invoice" is present in the UI. confirmed with product (slack link)
do we need to inject "statements" anywhere?
fixes https://github.com/elastic/docs-feedback/issues/49