Fix md format (#8434)

The merge queue is failing due to md lint changes:

https://github.com/sigp/lighthouse/actions/runs/19491272535/job/55783746002

This PR fixes the lint. I'm targeting the release branch so we can get things merged for release tomorrow, and we'll merge back down to `unstable`.


  


Co-Authored-By: Jimmy Chen <jchen.tc@gmail.com>

Co-Authored-By: Michael Sproul <michael@sigmaprime.io>

Author: jimmygchen

book/book.toml

@@ -1,7 +1,6 @@
 [book]
 authors = ["Paul Hauner", "Age Manning"]
 language = "en"
-multilingual = false
 src = "src"
 title = "Lighthouse Book"
 

book/src/advanced_blobs.md

@@ -6,12 +6,12 @@ With the [Fusaka](https://ethereum.org/roadmap/fusaka) upgrade, the main feature
 
 Table below summarizes the role of relevant flags in Lighthouse beacon node:
 
-| | Post-Deneb, Pre-Fulu || Post-Fulu ||
-|-------|----------|----------|-----------|----------|
-| Flag | Usage | Can serve blobs? | Usage | Can serve blobs? |
-| --prune-blobs false | Does not prune blobs since using the flag | Yes, for blobs since using the flag and for the past 18 days | Does not prune data columns since using the flag | No |
-| --semi-supernode | - | - | Store half data columns | Yes, for blobs since using the flag for a max of 18 days |
-| --supernode | - | - | Store all data columns | Yes, for blobs since using the flag for a max of 18 days |
+|                     | Post-Deneb, Pre-Fulu                      |                                                              | Post-Fulu                                        |                                                          |
+|---------------------|-------------------------------------------|--------------------------------------------------------------|--------------------------------------------------|----------------------------------------------------------|
+| Flag                | Usage                                     | Can serve blobs?                                             | Usage                                            | Can serve blobs?                                         |
+| --prune-blobs false | Does not prune blobs since using the flag | Yes, for blobs since using the flag and for the past 18 days | Does not prune data columns since using the flag | No                                                       |
+| --semi-supernode    | -                                         | -                                                            | Store half data columns                          | Yes, for blobs since using the flag for a max of 18 days |
+| --supernode         | -                                         | -                                                            | Store all data columns                           | Yes, for blobs since using the flag for a max of 18 days |
 
 While both `--supernode` and `--semi-supernode` can serve blobs, a supernode will be faster to respond to blobs queries as it skips the blob reconstruction step. Running a supernode also helps the network by serving the data columns to its peers.
 

book/src/advanced_database.md

@@ -63,11 +63,11 @@ that we have observed are:
 
 The following table lists the data for different configurations. Note that the disk space requirement is for the `chain_db` and `freezer_db`, excluding the `blobs_db`.
 
-| Hierarchy Exponents | Storage Requirement | Sequential Slot Query | Uncached Query | Time to Sync |
-|---|---|---|---|---|
-| 5,9,11,13,16,18,21 (default) | 418 GiB | 250-700 ms | up to 10 s | 1 week |
-| 5,7,11 (frequent snapshots) | 589 GiB | 250-700 ms | up to 6 s | 1 week |
-| 0,5,7,11 (per-slot diffs) | 2500 GiB | 250-700 ms | up to 4 s | 7 weeks |
+| Hierarchy Exponents          | Storage Requirement | Sequential Slot Query | Uncached Query | Time to Sync |
+|------------------------------|---------------------|-----------------------|----------------|--------------|
+| 5,9,11,13,16,18,21 (default) | 418 GiB             | 250-700 ms            | up to 10 s     | 1 week       |
+| 5,7,11 (frequent snapshots)  | 589 GiB             | 250-700 ms            | up to 6 s      | 1 week       |
+| 0,5,7,11 (per-slot diffs)    | 2500 GiB            | 250-700 ms            | up to 4 s      | 7 weeks      |
 
 [Jim](https://github.com/mcdee) has done some experiments to study the response time of querying random slots (uncached query) for `--hierarchy-exponents 0,5,7,11` (per-slot diffs) and `--hierarchy-exponents 5,9,11,13,17,21` (per-epoch diffs), as show in the figures below. From the figures, two points can be concluded:
 

book/src/api_vc_endpoints.md

@@ -132,7 +132,7 @@ Returns information regarding the health of the host machine.
 
 | Property          | Specification                              |
 |-------------------|--------------------------------------------|
-| Path              | `/lighthouse/ui/health`                       |
+| Path              | `/lighthouse/ui/health`                    |
 | Method            | GET                                        |
 | Required Headers  | [`Authorization`](./api_vc_auth_header.md) |
 | Typical Responses | 200                                        |
@@ -178,7 +178,7 @@ Returns the graffiti that will be used for the next block proposal of each valid
 
 | Property          | Specification                              |
 |-------------------|--------------------------------------------|
-| Path              | `/lighthouse/ui/graffiti`                    |
+| Path              | `/lighthouse/ui/graffiti`                  |
 | Method            | GET                                        |
 | Required Headers  | [`Authorization`](./api_vc_auth_header.md) |
 | Typical Responses | 200                                        |

book/src/archived_merge_migration.md

@@ -25,14 +25,14 @@ All networks (**Mainnet**, **Goerli (Prater)**, **Ropsten**, **Sepolia**, **Kiln
 
 <div align="center">
 
-| Network | Bellatrix                     | The Merge                     | Remark     |
-|---------|-------------------------------|-------------------------------| -----------|
-| Ropsten | 2<sup>nd</sup> June 2022      | 8<sup>th</sup> June 2022      | Deprecated |
-| Sepolia  | 20<sup>th</sup> June 2022    | 6<sup>th</sup> July 2022      |            |
-| Goerli   | 4<sup>th</sup> August 2022   | 10<sup>th</sup> August 2022   | Previously named `Prater`|
-| Mainnet  | 6<sup>th</sup> September 2022| 15<sup>th</sup> September 2022|            |
-| Chiado   | 10<sup>th</sup> October 2022 | 4<sup>th</sup> November 2022  |            |
-| Gnosis   | 30<sup>th</sup> November 2022| 8<sup>th</sup> December 2022  |            |
+| Network | Bellatrix                     | The Merge                      | Remark                    |
+|---------|-------------------------------|--------------------------------|---------------------------|
+| Ropsten | 2<sup>nd</sup> June 2022      | 8<sup>th</sup> June 2022       | Deprecated                |
+| Sepolia | 20<sup>th</sup> June 2022     | 6<sup>th</sup> July 2022       |                           |
+| Goerli  | 4<sup>th</sup> August 2022    | 10<sup>th</sup> August 2022    | Previously named `Prater` |
+| Mainnet | 6<sup>th</sup> September 2022 | 15<sup>th</sup> September 2022 |                           |
+| Chiado  | 10<sup>th</sup> October 2022  | 4<sup>th</sup> November 2022   |                           |
+| Gnosis  | 30<sup>th</sup> November 2022 | 8<sup>th</sup> December 2022   |                           |
 
 </div>