fix: correct duplicated word in tagsets guide (Test PR)

[KumarNirupam1]

Notes for Reviewers

Test PR to validate the PR preview workflows. Change is a minimal typo fix in content/en/kanvas/designer/tagsets/index.md ("exceeds that exceeds" → "that exceeds").
Audit findings (report-only): pull_request_target in labeler.yml, label-commenter.yml, copilot-pr-handler.yml; wait-for-pages-deployment: false present; actions SHA-pinned; Hugo 0.158.0 matches modules; no dead Hugo/Dart Sass code.

Signed commits

• Yes, I signed my commits.

Summary by CodeRabbit

• Documentation
  • Corrected the performance warning to clarify that grouping is disabled when a loaded design contains more than 10 tags.

[coderabbitai]

Warning

Review limit reached

@KumarNirupam1, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1b7baeb7-ca99-4073-9b5c-0eee39bea007

📥 Commits

Reviewing files that changed from the base of the PR and between f5357fd and c4c80ee.

📒 Files selected for processing (1)

• content/en/cloud/_index.md

📝 Walkthrough

Walkthrough

The designer documentation now states that automatic tag grouping is disabled when a loaded design exceeds 10 tags.

Changes

Tag grouping documentation

Layer / File(s)	Summary
Correct tag grouping warning content/en/kanvas/designer/tagsets/index.md	Corrected duplicated wording in the warning about designs exceeding 10 tags.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: correcting a duplicated word in the tagsets guide.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@content/en/kanvas/designer/tagsets/index.md`:
- Line 33: Revise the sentence describing automatic tag-grouping behavior to
remove the repeated “design” phrasing, using a direct condition for designs
exceeding 10 tags. Preserve the existing behavior and the instruction about
manually enabling grouping via the “Group Components” button.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7d9e393d-282b-444f-b449-743ca4122620

📥 Commits

Reviewing files that changed from the base of the PR and between 6e719b0 and f5357fd.

📒 Files selected for processing (1)

• content/en/kanvas/designer/tagsets/index.md

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Remove the repeated design phrase.

The sentence still repeats the scope in “a design that exceeds 10 tags within a single design.” Use a direct condition instead.

Proposed wording

- Upon loading a design that exceeds 10 tags within a single design, Kanvas will automatically disable grouping by tags.
+ When Kanvas loads a design with more than 10 tags, it automatically disables grouping by tags.

As per coding guidelines, content/en/**/*.md must use a professional, clear, concise tone and accurate content.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Upon loading a design that exceeds 10 tags within a single design, Kanvas will automatically disable grouping by tags. You can manually enable grouping by tags by clicking the "Group Components" button in the Designer dock.
	When Kanvas loads a design with more than 10 tags, it automatically disables grouping by tags.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@content/en/kanvas/designer/tagsets/index.md` at line 33, Revise the sentence
describing automatic tag-grouping behavior to remove the repeated “design”
phrasing, using a direct condition for designs exceeding 10 tags. Preserve the
existing behavior and the instruction about manually enabling grouping via the
“Group Components” button.

Source: Coding guidelines

[github-actions]

🚀 Preview deployment: https://docs.layer5.io/pr-preview/pr-1202/

Note: Preview may take a moment (GitHub Pages deployment in progress). Please wait and refresh. Track deployment here

[KumarNirupam1]

hey @banana-three-join , I finished the layer5 docs test PR workflow validation is all done.

what works:

• build triggers on the paths, page renders, change visible, re-renders on a new commit, reopen re-triggers the build + deploy
• comment posted with the shared template

audit findings (report-only):

• pull_request_target in labeler.yml, label-commenter.yml, copilot-pr-handler.yml
• wait-for-pages-deployment: false present
• actions are SHA-pinned to latest majors
• hugo 0.158.0 matches modules
• no dead hugo/dart sass code

one gap i noticed: closing a PR leaves the preview deployed - no cleanup or comment, it just stays until the retention prune removes it. happy to help fix it if you want to take that up.