Indent doc list continuations

3 files changed, 19 insertions, 19 deletions

diff --git a/crates/core/src/context_menu.rs b/crates/core/src/context_menu.rs
index f56c7b9..f06e07c 100644
--- a/crates/core/src/context_menu.rs
+++ b/crates/core/src/context_menu.rs
@@ -51,11 +51,11 @@ pub enum MenuAction {
     Separator,
     /// A non-interactive section label (`"Move to Workspace"`, `"Customize"`)
     /// - dimmer, smaller text, never highlighted, click is a no-op just
-    /// like [`Self::Separator`]. Replaces an earlier hack that embedded
-    /// box-drawing characters directly in an ordinary item's label, which
-    /// rendered (and behaved, right up until the dispatch site's own
-    /// special-case) exactly like a clickable row that happened to do
-    /// nothing - confusing on both counts.
+    ///   like [`Self::Separator`]. Replaces an earlier hack that embedded
+    ///   box-drawing characters directly in an ordinary item's label, which
+    ///   rendered (and behaved, right up until the dispatch site's own
+    ///   special-case) exactly like a clickable row that happened to do
+    ///   nothing - confusing on both counts.
     Header,
 }
 
@@ -180,8 +180,8 @@ impl ContextMenu {
     /// The y-offset row `index` starts at, relative to the menu's own top
     /// - every row height up to (not including) `index`, summed. `row_
     /// at`/rendering both walk rows this same way, so a mismatch between
-    /// "where a row is drawn" and "where a click resolves to" can't creep
-    /// in from computing the two differently.
+    ///   "where a row is drawn" and "where a click resolves to" can't creep
+    ///   in from computing the two differently.
     pub fn row_y(&self, index: usize) -> i32 {
         (0..index.min(self.items.len())).map(|i| self.row_height_for(i)).sum::<u32>() as i32
     }
diff --git a/crates/core/src/manager/mod.rs b/crates/core/src/manager/mod.rs
index 64cf5c3..77fcf3c 100644
--- a/crates/core/src/manager/mod.rs
+++ b/crates/core/src/manager/mod.rs
@@ -119,12 +119,12 @@ pub struct WindowManager {
     /// owns real output hardware (`drain_output_position_requests`) on its
     /// own next poll. Core has no way to reposition a real `Output` itself
     /// - monitor geometry flows one direction, backend into core, via
-    /// `set_monitors` - so a request from an IPC caller (an AGS display-
-    /// settings panel wanting to set up monitor mirroring, concretely) has
-    /// to cross back over that boundary the same indirect way window
-    /// geometry changes do in the other direction: queued here, applied by
-    /// the backend, and `set_monitors` reports the result back on the
-    /// backend's next monitor query, same as any other hotplug/reconfigure.
+    ///   `set_monitors` - so a request from an IPC caller (an AGS display-
+    ///   settings panel wanting to set up monitor mirroring, concretely) has
+    ///   to cross back over that boundary the same indirect way window
+    ///   geometry changes do in the other direction: queued here, applied by
+    ///   the backend, and `set_monitors` reports the result back on the
+    ///   backend's next monitor query, same as any other hotplug/reconfigure.
     output_position_requests: Vec<(MonitorId, i32, i32)>,
     /// Same cross-boundary-request pattern as `output_position_requests`
     /// just above, for Phase 2 of the multi-cursor plan - pinning a
@@ -206,9 +206,9 @@ pub struct WindowManager {
     /// switching workspace changes what's visible on every screen at
     /// once). Still meaningful even when `per_monitor_workspaces` is `true`
     /// - it's the fallback `workspace_for_monitor` returns for a monitor
-    /// that has never had its own workspace switched independently yet,
-    /// and what a plain `current_workspace()` call reports either way. See
-    /// `visible_windows`'s doc comment for the filter this actually drives.
+    ///   that has never had its own workspace switched independently yet,
+    ///   and what a plain `current_workspace()` call reports either way. See
+    ///   `visible_windows`'s doc comment for the filter this actually drives.
     current_workspace: WorkspaceId,
     /// Whichever workspace was current immediately before the current one
     /// became current - see `switch_workspace`'s doc comment.
@@ -244,7 +244,7 @@ pub struct WindowManager {
     /// turned on, or a newly connected monitor) falls back to
     /// `current_workspace`, the same shared value shared-mode always uses
     /// - see `workspace_for_monitor`. Unused, and left empty, whenever
-    /// `per_monitor_workspaces` is `false`.
+    ///   `per_monitor_workspaces` is `false`.
     monitor_workspaces: HashMap<MonitorId, WorkspaceId>,
     next_workspace_id: WorkspaceId,
     next_window_id: WindowId,
diff --git a/crates/core/src/window.rs b/crates/core/src/window.rs
index 21b7ab4..724aab3 100644
--- a/crates/core/src/window.rs
+++ b/crates/core/src/window.rs
@@ -498,8 +498,8 @@ pub const DECORATED_TOP_RESIZE_MARGIN: i32 = RESIZE_MARGIN;
 /// How much wider than [`RESIZE_MARGIN`] a corner's own diagonal-resize
 /// zone reaches, as a multiplier on whatever margin is actually in effect
 /// - see `ResizeEdge::resize_edge_at`'s doc comment for why corners need
-/// more room than a straight edge at all, not just a proportionally bigger
-/// dead-simple hit box.
+///   more room than a straight edge at all, not just a proportionally bigger
+///   dead-simple hit box.
 ///
 /// Bumped from `3` (18px at the default `RESIZE_MARGIN`) to `5` (30px):
 /// reported live as still too tight to land reliably, and there's real