Indent doc list continuations

2 files changed, 6 insertions, 6 deletions

diff --git a/crates/platform/src/ipc/types.rs b/crates/platform/src/ipc/types.rs
index 3243e31..0a8653c 100644
--- a/crates/platform/src/ipc/types.rs
+++ b/crates/platform/src/ipc/types.rs
@@ -422,9 +422,9 @@ pub(crate) struct WorkspacesEvent<'a> {
 
 /// A third, independently-diffed event on the same `subscribe` connection
 /// - see `WorkspacesEvent`'s own doc comment for why this isn't folded
-/// into either of the other two: a layout cycle touches no window and no
-/// workspace, so it needs its own change-diff to avoid pushing an
-/// unrelated payload on every unrelated change.
+///   into either of the other two: a layout cycle touches no window and no
+///   workspace, so it needs its own change-diff to avoid pushing an
+///   unrelated payload on every unrelated change.
 #[derive(Serialize)]
 pub(crate) struct KeyboardLayoutEvent<'a> {
     pub(crate) event: &'static str,
diff --git a/crates/platform/src/pam_auth.rs b/crates/platform/src/pam_auth.rs
index bdad439..e9e5841 100644
--- a/crates/platform/src/pam_auth.rs
+++ b/crates/platform/src/pam_auth.rs
@@ -34,9 +34,9 @@ const SERVICE: &str = "srdwm";
 /// password itself, resolves to `false`. Deliberately no distinction
 /// between "wrong password" and "something is broken" in the return value
 /// - fail secure means every non-success path stays locked, not just the
-/// ones that are the user's own fault. Logged at `warn` for whoever's
-/// debugging a setup problem, never at a level that would put the
-/// password itself in a log.
+///   ones that are the user's own fault. Logged at `warn` for whoever's
+///   debugging a setup problem, never at a level that would put the
+///   password itself in a log.
 pub fn authenticate(username: &str, password: &str) -> bool {
     let conversation = Conversation::with_credentials(username, password);
     let mut context = match Context::new(SERVICE, Some(username), conversation) {