diff --git a/apps/macos/Sources/Clawdis/Onboarding.swift b/apps/macos/Sources/Clawdis/Onboarding.swift
index 03d9570cf..3bc6368a4 100644
--- a/apps/macos/Sources/Clawdis/Onboarding.swift
+++ b/apps/macos/Sources/Clawdis/Onboarding.swift
@@ -487,7 +487,7 @@ struct OnboardingView: View {
             .keyboardShortcut(.return)
             .buttonStyle(.borderedProminent)
         }
-        .padding(.horizontal, 20)
+        .padding(.horizontal, 28)
         .padding(.bottom, 12)
         .frame(height: 60)
     }
@@ -497,6 +497,7 @@ struct OnboardingView: View {
             content()
             Spacer()
         }
+        .padding(.horizontal, 28)
         .frame(width: self.pageWidth, alignment: .top)
     }
 
diff --git a/docs/mac/remote.md b/docs/mac/remote.md
index 203ea7981..a85fde7c4 100644
--- a/docs/mac/remote.md
+++ b/docs/mac/remote.md
@@ -22,6 +22,7 @@ This flow lets the macOS app act as a full remote control for a Clawdis gateway
 1) Open *Settings → General*.
 2) Under **Clawdis runs**, pick **Remote over SSH** and set:
    - **SSH target**: `user@host` (optional `:port`).
+     - If the gateway is on the same LAN and advertises Bonjour, pick it from the discovered list to auto-fill this field.
    - **Identity file** (advanced): path to your key.
    - **Project root** (advanced): remote checkout path used for commands.
 3) Hit **Test remote**. Success indicates the remote `clawdis status --json` runs correctly. Failures usually mean PATH/CLI issues; exit 127 means the CLI isn’t found remotely.