From e015e4359cbde27f0e4a6bc18ff12e8ca2f64ea3 Mon Sep 17 00:00:00 2001 From: bluebunny Date: Fri, 19 Jun 2026 12:53:37 +0000 Subject: [PATCH] docs: device-categorization: fix duplicate typo Signed-off-by: bluebunny --- docs/packaging/device-categorization.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/packaging/device-categorization.md b/docs/packaging/device-categorization.md index 543df94cd..c75893506 100644 --- a/docs/packaging/device-categorization.md +++ b/docs/packaging/device-categorization.md @@ -242,9 +242,9 @@ the date of the branching. If the maintainers cannot be contacted, or if two weeks and any additionally requested time pass and the device still does not meet the criteria, a merge request to move them to the now appropriate category should be opened. If the -device being demoted is in the main or community category is in the main or -community category, the community shall be notified through Fediverse and -blog posts (edge blog post, release notes, or next monthly blog post). +device being demoted is in the main or community category, the community shall +be notified through Fediverse and blog posts (edge blog post, release notes, or +next monthly blog post). Merge requests moving a device to a lower category are subject to the standard [pmaports approval rules](../merge-requests/approval-rules).