diff --git a/reqwest-retry/src/middleware.rs b/reqwest-retry/src/middleware.rs
index cd7cda3..e4f01d1 100644
--- a/reqwest-retry/src/middleware.rs
+++ b/reqwest-retry/src/middleware.rs
@@ -59,10 +59,10 @@ macro_rules! log_retry {
 ///
 /// Some workaround suggestions:
 /// * If you can fit the data in memory, you can instead build static request bodies e.g. with
-/// `Body`'s `From<String>` or `From<Bytes>` implementations.
+///   `Body`'s `From<String>` or `From<Bytes>` implementations.
 /// * You can wrap this middleware in a custom one which skips retries for streaming requests.
 /// * You can write a custom retry middleware that builds new streaming requests from the data
-/// source directly, avoiding the issue of streaming requests not being clonable.
+///   source directly, avoiding the issue of streaming requests not being clonable.
 pub struct RetryTransientMiddleware<
     T: RetryPolicy + Send + Sync + 'static,
     R: RetryableStrategy + Send + Sync + 'static = DefaultRetryableStrategy,