From 2d45848fc718e013a4ff7a8caec02005c75a8fdd Mon Sep 17 00:00:00 2001
From: Christian Duerr <contact@christianduerr.com>
Date: Wed, 4 Sep 2024 11:37:14 +0200
Subject: [PATCH] Fix clippy warnings

---
 src/globals.rs | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/globals.rs b/src/globals.rs
index 6b16c6d5d..4486dbd84 100644
--- a/src/globals.rs
+++ b/src/globals.rs
@@ -7,13 +7,13 @@ use wayland_client::Proxy;
 /// argument.  For example:
 ///
 /// - A global that binds to `wl_compositor` with maximum version 4 could implement
-/// `ProvidesBoundGlobal<WlCompositor, 4>`, `ProvidesBoundGlobal<WlCompositor, 3>`,
-/// `ProvidesBoundGlobal<WlCompositor, 2>`, and `ProvidesBoundGlobal<WlCompositor, 1>` because
+///   `ProvidesBoundGlobal<WlCompositor, 4>`, `ProvidesBoundGlobal<WlCompositor, 3>`,
+///   `ProvidesBoundGlobal<WlCompositor, 2>`, and `ProvidesBoundGlobal<WlCompositor, 1>` because
 /// versions 2-4 only add additional requests to the `wl_surface` API.
 /// - A global that binds to `wl_compositor` with maximum version 5 may only implement
-/// `ProvidesBoundGlobal<WlCompositor, 5>` because version 5 makes using `wl_surface::attach` with
-/// a nonzero offset a protocol error.  A caller who is only aware of the version 4 API risks
-/// causing these protocol errors if it uses surfaces created by such a global.
+///   `ProvidesBoundGlobal<WlCompositor, 5>` because version 5 makes using `wl_surface::attach` with
+///   a nonzero offset a protocol error.  A caller who is only aware of the version 4 API risks
+///   causing these protocol errors if it uses surfaces created by such a global.
 ///
 /// Changes that cause compatibility breaks include:
 ///