fmt: format with dprint

Author: simonsan

src/functional/generics-type-classes.md

@@ -260,21 +260,21 @@ It is also used by several popular crates to allow API flexibility:
   concept, and a slightly different technique. [^6]
 
 [^1]: See:
-[impl From\<CString\> for Vec\<u8\>](https://doc.rust-lang.org/1.59.0/src/std/ffi/c_str.rs.html#803-811)
+    [impl From\<CString\> for Vec\<u8\>](https://doc.rust-lang.org/1.59.0/src/std/ffi/c_str.rs.html#803-811)
 
 [^2]: See:
-[impl\<T: Ord\> FromIterator\<T\> for BinaryHeap\<T\>](https://web.archive.org/web/20201030132806/https://doc.rust-lang.org/stable/src/alloc/collections/binary_heap.rs.html#1330-1335)
+    [impl\<T: Ord\> FromIterator\<T\> for BinaryHeap\<T\>](https://web.archive.org/web/20201030132806/https://doc.rust-lang.org/stable/src/alloc/collections/binary_heap.rs.html#1330-1335)
 
 [^3]: See:
-[impl\<'\_\> ToString for Cow\<'\_, str>](https://doc.rust-lang.org/stable/src/alloc/string.rs.html#2235-2240)
+    [impl\<'\_\> ToString for Cow\<'\_, str>](https://doc.rust-lang.org/stable/src/alloc/string.rs.html#2235-2240)
 
 [^4]: Example:
-[https://docs.rs/stm32f30x-hal/0.1.0/stm32f30x_hal/gpio/gpioa/struct.PA0.html](https://docs.rs/stm32f30x-hal/0.1.0/stm32f30x_hal/gpio/gpioa/struct.PA0.html)
+    [https://docs.rs/stm32f30x-hal/0.1.0/stm32f30x_hal/gpio/gpioa/struct.PA0.html](https://docs.rs/stm32f30x-hal/0.1.0/stm32f30x_hal/gpio/gpioa/struct.PA0.html)
 
 [^5]: See:
-[https://docs.rs/hyper/0.14.5/hyper/client/struct.Client.html](https://docs.rs/hyper/0.14.5/hyper/client/struct.Client.html)
+    [https://docs.rs/hyper/0.14.5/hyper/client/struct.Client.html](https://docs.rs/hyper/0.14.5/hyper/client/struct.Client.html)
 
 [^6]: See:
-[The Case for the Type State Pattern](https://web.archive.org/web/20210325065112/https://www.novatec-gmbh.de/en/blog/the-case-for-the-typestate-pattern-the-typestate-pattern-itself/)
-and
-[Rusty Typestate Series (an extensive thesis)](https://web.archive.org/web/20210328164854/https://rustype.github.io/notes/notes/rust-typestate-series/rust-typestate-index)
+    [The Case for the Type State Pattern](https://web.archive.org/web/20210325065112/https://www.novatec-gmbh.de/en/blog/the-case-for-the-typestate-pattern-the-typestate-pattern-itself/)
+    and
+    [Rusty Typestate Series (an extensive thesis)](https://web.archive.org/web/20210328164854/https://rustype.github.io/notes/notes/rust-typestate-series/rust-typestate-index)

src/intro.md

@@ -45,4 +45,5 @@ chapters:
   when coding. However, while design patterns give us benefits, anti-patterns
   create more problems.
 
-[^1]: <https://www.infoq.com/podcasts/software-architecture-hard-parts/> ([Archive](https://web.archive.org/web/20240124025806/https://www.infoq.com/podcasts/software-architecture-hard-parts/)]
+[^1]: <https://www.infoq.com/podcasts/software-architecture-hard-parts/>
+    ([Archive](https://web.archive.org/web/20240124025806/https://www.infoq.com/podcasts/software-architecture-hard-parts/)]

src/patterns/ffi/wrappers.md

@@ -153,8 +153,8 @@ optimizations that C code cannot attain. Being denied access to certain
 shortcuts is the price Rust programmers need to pay.
 
 [^1]: For the C programmers out there scratching their heads, the iterator need
-not be read *during* this code to cause the UB. The exclusivity rule also
-enables compiler optimizations which may cause inconsistent observations by the
-iterator's shared reference (e.g. stack spills or reordering instructions for
-efficiency). These observations may happen *any time after* the mutable
-reference is created.
+    not be read *during* this code to cause the UB. The exclusivity rule also
+    enables compiler optimizations which may cause inconsistent observations by
+    the iterator's shared reference (e.g. stack spills or reordering
+    instructions for efficiency). These observations may happen *any time after*
+    the mutable reference is created.