fix numbers in the premium plan grid - #1150
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The displayed ratio, coverage wording, and linked overview remain inconsistent.
Get a fresh assessment by requesting another Copilot review.
Pull request overview
Updates Premium plan documentation with revised Community Blocklist coverage figures and a guide link.
Changes:
- Changes coverage figures from 3k/50k to 15k/60k.
- Updates comparison content and related messaging.
- Adds a Community Blocklist guide link.
File summaries
| File | Review summary |
|---|---|
crowdsec-docs/unversioned/console/premium_upgrade.mdx |
Correct the upgrade ratio to ×4, use “up to 60k IPs,” and update the linked overview’s inconsistent figures. |
Review details
Suppressed comments (3)
crowdsec-docs/unversioned/console/premium_upgrade.mdx:318
- This description still says the Premium list is up from 3,000, while the card and the linked blocklist documentation now use 15k for Community. That leaves the SecOps tab internally inconsistent; please change 3,000 to 15,000.
description="Top 60k most aggressive attackers (up from 3,000 in Community)."
crowdsec-docs/unversioned/console/premium_upgrade.mdx:165
- The canonical Community Blocklist page describes Premium coverage as up to 60k IPs, so
60k+overstates the blocklist coverage and conflicts with the card's 60k cap. Please use wording such asup to 60k IPshere.
- **Better blocking**: Access to 60k+ IPs and organization-specific threat intel
crowdsec-docs/unversioned/console/premium_upgrade.mdx:70
- This page links readers to
unversioned/console/premium_upgrade/features_overview.mdx, but that linked page still advertises3k → 50kandtop 3k/top 50k. Updating this grid without updating the linked overview leaves users with contradictory Premium coverage numbers; please update both pages in the same change.
metric="15k → 60k IPs"
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
blotus
approved these changes
Sep 15, 2026
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.