From 43f10924368c30cedd2fe8bfbb8f7434207747e5 Mon Sep 17 00:00:00 2001
From: Eduard Gert <kontakt@eduardgert.de>
Date: Thu, 20 Aug 2026 15:54:33 +0200
Subject: [PATCH] docs: reorder Assign Peers to Groups videos

Show the drag-to-group recording right after the text it illustrates,
then the group-from-selection flow.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---
 src/pages/manage/control-center/draft-mode.mdx | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/pages/manage/control-center/draft-mode.mdx b/src/pages/manage/control-center/draft-mode.mdx
index 94cc9b84..02b0280d 100644
--- a/src/pages/manage/control-center/draft-mode.mdx
+++ b/src/pages/manage/control-center/draft-mode.mdx
@@ -104,6 +104,11 @@ Right-click a node and choose **Rename**. We rename the server to `staging-01` a
 
 Drag the `staging-01` node onto the `Staging` group. The peer is absorbed into the group and the group's member count goes up. Membership travels with the group's change, so you never manage it separately.
 
+<p>
+    <Video src="/docs-static/img/manage/control-center/control-center-draft-drag-to-group.mp4"
+           label="Dragging the staging-01 peer onto the Staging group, which absorbs it and updates its member count"/>
+</p>
+
 To group several peers at once, drag a selection across them, then click **Create Group** in the selection menu (or press `G`) and name the group:
 
 <p>
@@ -111,11 +116,6 @@ To group several peers at once, drag a selection across them, then click **Creat
            label="Drag-selecting several peers, clicking Create Group in the selection menu, and naming the new group"/>
 </p>
 
-<p>
-    <Video src="/docs-static/img/manage/control-center/control-center-draft-drag-to-group.mp4"
-           label="Dragging the staging-01 peer onto the Staging group, which absorbs it and updates its member count"/>
-</p>
-
 ### Connect Nodes to Create Policies
 
 Drag the existing `DevOps` group from the components panel onto the canvas, then drag a connection from `DevOps` to `Staging`. The standard policy editor opens with both sides prefilled. Restrict it to what the team actually needs: TCP port `443` for the web app, not all traffic. The first policy you deploy should already be the least-privilege one.