[Workflows] Update unit for included GB-month

[mia303]

No description provided.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
/src/content/partials/workflows/	@celso, @deloreyj, @irvinebroque, @jonesphillip, @mia303, @rita3ko, @vy-ton, @cloudflare/product-owners

[cloudflare-workers-and-pages]

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://workflows-update-limits-doc.previews.developers.cloudflare.com (commit 16ae201)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status	Deployment URL	Commit	Updated (UTC)	See this deployment's details
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://0246545c.previews.developers.cloudflare.com	16ae201	2026-09-08T14:44:41.072Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://0a156078.previews.developers.cloudflare.com	25ed2b4	2026-09-04T14:25:20.501Z	Visit the dashboard ↗

[github-actions]

Preview URL: https://16ae2010.preview.developers.cloudflare.com
Preview Branch URL: https://workflows-update-limits-doc.preview.developers.cloudflare.com

[cloudflare-docs-bot]

Review

⚠️ 1 warning found in commit 16ae201.

👉 Fix in your agent 👈

Fix the following review findings in PR #33220 (https://github.com/cloudflare/cloudflare-docs/pull/33220).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.

---

## Conventions

### Warnings (1)

#### CV-c681f7cb878d · PR description
- **File:** PR-level finding
- **Issue:** The PR description is completely empty, providing no explanation of the change.
- **Fix:** Add a brief human-written description summarizing the unit update to the Workflows pricing partial.

Code Review

This code review is in beta and may not always be helpful — use your judgment.

_{No code review issues found.}

Conventions

Warnings (1)

File	Issue
PR	PR description — The PR description is completely empty, providing no explanation of the change. Fix: Add a brief human-written description summarizing the unit update to the Workflows pricing partial.

Style Guide Review

_{No style-guide issues found.}

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review	Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.
/rebase	Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.