fmt docs

Author: raphael-istari

docs/design.md

@@ -3,17 +3,16 @@
 We wrote Badger with these design goals in mind:
 
 - Write a key-value database in pure Go
-- Use latest research to build the fastest KV database for data sets spanning
-  terabytes
+- Use latest research to build the fastest KV database for data sets spanning terabytes
 - Optimize for modern storage devices
 
 Badger’s design is based on a paper titled
 [WiscKey: Separating Keys from Values in SSD-conscious Storage](https://www.usenix.org/system/files/conference/fast16/fast16-papers-lu.pdf).
 
 ## References
 
-The following blog posts are a great starting point for learning more about
-Badger and the underlying design principles:
+The following blog posts are a great starting point for learning more about Badger and the
+underlying design principles:
 
 - [Introducing Badger: A fast key-value store written natively in Go](https://hypermode.com/blog/badger/)
 - [Make Badger crash resilient with ALICE](https://hypermode.com/blog/alice/)
@@ -37,22 +36,19 @@ Badger and the underlying design principles:
 | TTL support                   | Yes                                    | Yes                          | No      |
 | 3D access (key-value-version) | Yes<sup>4</sup>                        | No                           | No      |
 
-<sup>1</sup> The WiscKey paper (on which Badger is based) saw big wins with
-separating values from keys, significantly reducing the write amplification
-compared to a typical LSM tree.
+<sup>1</sup> The WiscKey paper (on which Badger is based) saw big wins with separating values from
+keys, significantly reducing the write amplification compared to a typical LSM tree.
 
-<sup>2</sup> RocksDB is an SSD-optimized version of LevelDB, which was designed
-specifically for rotating disks. As such RocksDB's design isn't aimed at SSDs.
+<sup>2</sup> RocksDB is an SSD-optimized version of LevelDB, which was designed specifically for
+rotating disks. As such RocksDB's design isn't aimed at SSDs.
 
-<sup>3</sup> SSI: Serializable Snapshot Isolation. For more details, see the
-blog post [Concurrent ACID Transactions in
-Badger](https://hypermode.com/blog/badger-txn/)
+<sup>3</sup> SSI: Serializable Snapshot Isolation. For more details, see the blog post
+[Concurrent ACID Transactions in Badger](https://hypermode.com/blog/badger-txn/)
 
-<sup>4</sup> Badger provides direct access to value versions via its Iterator
-API. Users can also specify how many versions to keep per key via Options.
+<sup>4</sup> Badger provides direct access to value versions via its Iterator API. Users can also
+specify how many versions to keep per key via Options.
 
 ## Benchmarks
 
-We've run comprehensive benchmarks against RocksDB, BoltDB, and LMDB. The
-benchmarking code with detailed logs are in the
-[badger-bench](https://github.com/dgraph-io/badger-bench) repo.
+We've run comprehensive benchmarks against RocksDB, BoltDB, and LMDB. The benchmarking code with
+detailed logs are in the [badger-bench](https://github.com/dgraph-io/badger-bench) repo.

docs/index.md

@@ -2,19 +2,17 @@
 
 ## What is Badger?
 
-BadgerDB is an embeddable, persistent, and fast key-value (KV) database written
-in pure Go. It is the underlying database for [Dgraph](https://github.com/dgraph-io/dgraph), a
-fast, distributed graph database. It is meant to be an efficient alternative to
-non-Go-based key-value stores like RocksDB.
+BadgerDB is an embeddable, persistent, and fast key-value (KV) database written in pure Go. It is
+the underlying database for [Dgraph](https://github.com/dgraph-io/dgraph), a fast, distributed graph
+database. It is meant to be an efficient alternative to non-Go-based key-value stores like RocksDB.
 
 ## Changelog
 
-We keep the
-[repo Changelog](https://github.com/dgraph-io/badger/blob/main/CHANGELOG.md)
-up to date with each release.
+We keep the [repo Changelog](https://github.com/dgraph-io/badger/blob/main/CHANGELOG.md) up to date
+with each release.
 
 [Quickstart](quickstart.md)
 
 [Design](design.md)
 
-[Troubleshooting](troubleshooting.md)
+[Troubleshooting](troubleshooting.md)