Merge pull request #11231 from ethereum/fixBrokenLink

Add invalid link check to markdown checker

Author: corwintines

src/content/contributing/translation-program/content-buckets/index.md

@@ -91,7 +91,7 @@ Below is a breakdown of the website pages each content bucket contains.
 - [Improving user experience](/roadmap/user-experience/)
 - [Future-proofing Ethereum](/roadmap/future-proofing/)
 - [Danksharding](/roadmap/danksharding/)
-- [Single slot finality](roadmap/single-slot-finality/)
+- [Single slot finality](/roadmap/single-slot-finality/)
 - [Proposer-builder separation](/roadmap/pbs/)
 - [Secret leader election](/roadmap/secret-leader-election/)
 - [Account abstraction](/roadmap/account-abstraction/)

src/content/developers/docs/consensus-mechanisms/pos/block-proposal/index.md

@@ -64,6 +64,6 @@ The block proposer receives payment for their work. There is a `base_reward` cal
 
 - [Introduction to blocks](/developers/docs/blocks/)
 - [Introduction to proof-of-stake](/developers/docs/consensus-mechanisms/pos/)
-- [Ethereum consensus specs](www.github.com/ethereum/consensus-specs)
+- [Ethereum consensus specs](https://github.com/ethereum/consensus-specs)
 - [Introduction to Gasper](/developers/docs/consensus-mechanisms/pos/)
 - [Upgrading Ethereum](https://eth2book.info/)

src/content/developers/docs/consensus-mechanisms/pow/index.md

@@ -68,7 +68,7 @@ To complicate things further, transactions rejected on the temporary fork may no
 
 ## Proof-of-work energy-usage {#energy}
 
-A major criticism of proof-of-work is the amount of energy output required to keep the network safe. To maintain security and decentralization, Ethereum on proof-of-work consumed large amounts of energy. Shortly before switching to proof-of-stake, Ethereum miners were collectively consuming about 70 TWh/yr (about the same as the Czech Republic - according to [digiconomist](digiconomist.net) on 18-July-2022).
+A major criticism of proof-of-work is the amount of energy output required to keep the network safe. To maintain security and decentralization, Ethereum on proof-of-work consumed large amounts of energy. Shortly before switching to proof-of-stake, Ethereum miners were collectively consuming about 70 TWh/yr (about the same as the Czech Republic - according to [digiconomist](https://digiconomist.net/) on 18-July-2022).
 
 ## Pros and cons {#pros-and-cons}
 

src/content/developers/docs/data-and-analytics/index.md

@@ -30,7 +30,7 @@ Using [GraphQL](https://graphql.org/), developers can query any of the curated o
 
 ## Client diversity
 
-[Client diversity](/developers/docs/nodes-and-clients/client-diversity/) is important for the overall health of the Ethereum network because it provides resilience to bugs and exploits. There are now several client diversity dashboards including [clientdiversity.org](https://clientdiversity.org/), [rated.network](rated.network), [execution-diversity.info](https://execution-diversity.info/) and [Ethernodes](https://ethernodes.org/).
+[Client diversity](/developers/docs/nodes-and-clients/client-diversity/) is important for the overall health of the Ethereum network because it provides resilience to bugs and exploits. There are now several client diversity dashboards including [clientdiversity.org](https://clientdiversity.org/), [rated.network](https://www.rated.network), [execution-diversity.info](https://execution-diversity.info/) and [Ethernodes](https://ethernodes.org/).
 
 ## Dune Analytics {#dune-analytics}
 

src/content/developers/docs/networking-layer/portal-network/index.md

@@ -24,7 +24,7 @@ The Portal Network aims to provide an alternative way for light nodes to get the
 
 ## How does the Portal Network work? {#how-does-portal-network-work}
 
-Ethereum nodes have strict protocols that define how they communicate with each other. Execution clients communicate using a set of subprotocols known as [DevP2P](developers/docs/networking-layer/#devp2p), while consensus clients use a different stack of subprotocols called [libP2P](/developers/docs/networking-layer/#libp2p). These define the types of data that can be passed between nodes.
+Ethereum nodes have strict protocols that define how they communicate with each other. Execution clients communicate using a set of subprotocols known as [DevP2P](/developers/docs/networking-layer/#devp2p), while consensus clients use a different stack of subprotocols called [libP2P](/developers/docs/networking-layer/#libp2p). These define the types of data that can be passed between nodes.
 
 ![devP2P and libP2P](portal-network-devp2p-libp2p.png)
 
@@ -79,4 +79,4 @@ If one client experiences issues or vulnerabilities, other clients can continue
 
 - [The Portal Network (Piper Merriam at Devcon Bogota)](https://www.youtube.com/watch?v=0stc9jnQLXA).
 - [The Portal Network discord](https://discord.gg/CFFnmE7Hbs)
-- [The Portal Network website](ethportal.net)
+- [The Portal Network website](https://www.ethportal.net/)

src/content/developers/docs/nodes-and-clients/archive-nodes/index.md

@@ -56,7 +56,7 @@ Before starting your own archive node, learn about the differences between the c
 
 ## Recommended practices
 
-Apart from general [recommendations for running a node](developers/docs/nodes-and-clients/run-a-node/), an archive node may be more demanding on hardware and maintenance. Considering Erigons [key features](https://github.com/ledgerwatch/erigon#key-features), the most practical approach is using the [Erigon](/developers/docs/nodes-and-clients/#erigon) client implementation.
+Apart from general [recommendations for running a node](/developers/docs/nodes-and-clients/run-a-node/), an archive node may be more demanding on hardware and maintenance. Considering Erigons [key features](https://github.com/ledgerwatch/erigon#key-features), the most practical approach is using the [Erigon](/developers/docs/nodes-and-clients/#erigon) client implementation.
 
 ### Hardware
 

src/content/developers/tutorials/run-node-raspberry-pi/index.md

@@ -119,7 +119,7 @@ sudo journalctl -u lighthouse-beacon
 
 Note that the consensus client will sync in a few minutes because it uses checkpoint sync. The execution client will take longer - potentially several hours, and it will not start until the consensus client is already finished syncing (this is because the execution client needs a target to sync to, which the synced consensus client provides).
 
-With the Geth and Lighthouse services running and synced, your Raspberry Pi is now an Ethereum node! It is most common to interact with the Ethereum network using Geth's Javascript console, which can be attached to the Geth client on port 8545. It is also possible to submit commands formatted as JSON objects using a request tool such as Curl. See more in the [Geth documentation](geth.ethereum.org).
+With the Geth and Lighthouse services running and synced, your Raspberry Pi is now an Ethereum node! It is most common to interact with the Ethereum network using Geth's Javascript console, which can be attached to the Geth client on port 8545. It is also possible to submit commands formatted as JSON objects using a request tool such as Curl. See more in the [Geth documentation](https://geth.ethereum.org/).
 
 Geth is preconfigured to report metrics to a Grafana dashboard which can be viewed in the browser. More advanced users might wish to use this feature to monitor the health of their node by navigating to `ipaddress:3000`, passing `user: admin` and `passwd: ethereum`.
 

src/content/translations/de/glossary/index.md

@@ -705,7 +705,7 @@ Ein Wert in der Kryptographie, der nur einmal verwendet werden kann. Eine Konto-
 
 ### Ommer- (Onkel-)Block {#ommer}
 
-Wenn ein [Miner](#miner) einen gültigen [Block](#block) findet, könnte ein anderer Miner einen Konkurrenzblock veröffentlicht haben, der zuerst der Spitze der Blockchain hinzugefügt wird. Dieser gültige, aber veraltete Block kann von neueren Blöcken als _Ommers_ aufgenommen werden und erhält eine Teilblockbelohnung. Der Begriff „Ommer" ist der bevorzugte geschlechtsneutrale Begriff für das Geschwisterteil eines Elternblocks, aber es wird auch manchmal „Onkel" verwendet. Dies war für Ethereum relevant, als es sich um ein [Proof-of-Work](pow) Netzwerk handelte, aber die Ommers sind keine Eigenschaft von [Proof-of-Stake](#pos) Ethereum, weil genau ein Block-Antragsteller in jedem Slot ausgewählt wird.
+Wenn ein [Miner](#miner) einen gültigen [Block](#block) findet, könnte ein anderer Miner einen Konkurrenzblock veröffentlicht haben, der zuerst der Spitze der Blockchain hinzugefügt wird. Dieser gültige, aber veraltete Block kann von neueren Blöcken als _Ommers_ aufgenommen werden und erhält eine Teilblockbelohnung. Der Begriff „Ommer" ist der bevorzugte geschlechtsneutrale Begriff für das Geschwisterteil eines Elternblocks, aber es wird auch manchmal „Onkel" verwendet. Dies war für Ethereum relevant, als es sich um ein [Proof-of-Work](#pow) Netzwerk handelte, aber die Ommers sind keine Eigenschaft von [Proof-of-Stake](#pos) Ethereum, weil genau ein Block-Antragsteller in jedem Slot ausgewählt wird.
 
 ### Optimistische Rollups (Optimistic Rollups) {#optimistic-rollup}
 

src/content/translations/de/roadmap/statelessness/index.md

@@ -66,7 +66,7 @@ Schwache Zustandslosigkeit beinhaltet Änderungen dazu, wie Ethereum Nodes Zusta
 
 **Bei der schwachen Zustandslosigkeit brauchen Blöcke Zugriff auf die vollen Zustandsdaten, jedoch benötigt das Verifizieren von Blöcken keine Zustandsdaten**
 
-Damit dies passieren kann, müssten [Verkle Bäume](../verkle-trees) bereits in Ethereum Clients implementiert sein. Verkle-Bäume sind eine Datenersetzungsstruktur um Ethereums Zustandsdaten zu speichern. Sie erlauben kleine "Zeugen" fester Größe, die dazu da sind Daten zwischen Peers zu vermitteln und Blöcke direkt, anstatt gegen lokale Datenbanken zu verifizieren. [Proposer-Builder Separation](/roadmap/pbs/) wird zudem benötigt, da es Blockerzeugern erlaubt spezialisierte Nodes mit leistungsfähigerer Hardware zu sein und da sie es sind, die Zugriff auf die vollen Zustandsdaten brauchen.
+Damit dies passieren kann, müssten [Verkle Bäume](/roadmap/verkle-trees/) bereits in Ethereum Clients implementiert sein. Verkle-Bäume sind eine Datenersetzungsstruktur um Ethereums Zustandsdaten zu speichern. Sie erlauben kleine "Zeugen" fester Größe, die dazu da sind Daten zwischen Peers zu vermitteln und Blöcke direkt, anstatt gegen lokale Datenbanken zu verifizieren. [Proposer-Builder Separation](/roadmap/pbs/) wird zudem benötigt, da es Blockerzeugern erlaubt spezialisierte Nodes mit leistungsfähigerer Hardware zu sein und da sie es sind, die Zugriff auf die vollen Zustandsdaten brauchen.
 
 <ExpandableCard title="Warum ist es OK ist sich auf weniger Block Proposer zu stützen?" eventCategory="/roadmap/statelessness" eventName="clicked why is it OK to rely on fewer block proposers?">
 

src/content/translations/es/developers/docs/consensus-mechanisms/index.md

@@ -56,7 +56,7 @@ Los validadores crean bloques. Un validador se selecciona aleatoriamente en cada
 
 Un sistema de prueba de participación es criptoeconómicamente seguro, porque un atacante que intente tomar el control de la cadena debe destruir una cantidad masiva de ETH. Un sistema de recompensas alienta a participantes individuales a comportarse honestamente, y las penalizaciones desaniman a los participantes a actuar malintencionadamente.
 
-Más información sobre la [prueba de participación](developers/docs/consensus-mechanisms/pos/).
+Más información sobre la [prueba de participación](/developers/docs/consensus-mechanisms/pos/).
 
 ### Una guía visual {#types-of-consensus-video}