diff --git a/public/content/about/index.md b/public/content/about/index.md
index 6bfde56ad15..8f5cebc4739 100644
--- a/public/content/about/index.md
+++ b/public/content/about/index.md
@@ -6,7 +6,7 @@ lang: en
# About ethereum.org {#about-ethereumorg}
-ethereum.org is a public, open-source resource for the Ethereum community that anyone can contribute to. We have a small core team dedicated to maintaining and developing the site with contributions from thousands of community members across the globe.
+ethereum.org is a public, open-source resource for the [Ethereum](/) community that anyone can contribute to. We have a small core team dedicated to maintaining and developing the site with contributions from thousands of community members across the globe.
**Nobody from ethereum.org will ever contact you. Do not respond.**
diff --git a/public/content/bridges/index.md b/public/content/bridges/index.md
index ee9bc82a943..4fbb0c78355 100644
--- a/public/content/bridges/index.md
+++ b/public/content/bridges/index.md
@@ -18,7 +18,7 @@ Let's consider an example:
You're from the USA and are planning a trip to Europe. You have USD, but you need EUR to spend. To exchange your USD for EUR you can use a currency exchange for a small fee.
-But, what do you do if you want to make a similar exchange to use a different [blockchain](/glossary/#blockchain)? Let's say you want to exchange [ETH](/glossary/#ether) on Ethereum Mainnet for ETH on [Arbitrum](https://arbitrum.io/). Like the currency exchange we made for EUR, we need a mechanism to move our ETH from Ethereum to Arbitrum. Bridges make such a transaction possible. In this case, [Arbitrum has a native bridge](https://portal.arbitrum.io/bridge) that can transfer ETH from Mainnet onto Arbitrum.
+But, what do you do if you want to make a similar exchange to use a different [blockchain](/glossary/#blockchain)? Let's say you want to exchange [ETH](/glossary/#ether) on [Ethereum](/) Mainnet for ETH on [Arbitrum](https://arbitrum.io/). Like the currency exchange we made for EUR, we need a mechanism to move our ETH from Ethereum to Arbitrum. Bridges make such a transaction possible. In this case, [Arbitrum has a native bridge](https://portal.arbitrum.io/bridge) that can transfer ETH from Mainnet onto Arbitrum.
## Why do we need bridges? {#why-do-we-need-bridges}
diff --git a/public/content/community/grants/index.md b/public/content/community/grants/index.md
index 2bd34db2e29..c4cc26f7fb3 100644
--- a/public/content/community/grants/index.md
+++ b/public/content/community/grants/index.md
@@ -6,7 +6,7 @@ lang: en
# Ethereum grants {#ethereum-grants}
-The programs listed below offer a variety of funding grants for projects working to promote the success and growth of the Ethereum ecosystem. Use this as a guide to find and apply for funds to help make your next Ethereum project a success.
+The programs listed below offer a variety of funding grants for projects working to promote the success and growth of the [Ethereum](/) ecosystem. Use this as a guide to find and apply for funds to help make your next Ethereum project a success.
This list is curated by our community. If there's something missing or incorrect, please edit this page!
diff --git a/public/content/community/online/index.md b/public/content/community/online/index.md
index c27dc859518..eea3c4c7be1 100644
--- a/public/content/community/online/index.md
+++ b/public/content/community/online/index.md
@@ -6,7 +6,7 @@ lang: en
# Online communities {#online-communities}
-Hundreds of thousands of Ethereum enthusiasts gather in these online forums to share news, talk about recent developments, debate technical issues, and imagine the future.
+Hundreds of thousands of [Ethereum](/) enthusiasts gather in these online forums to share news, talk about recent developments, debate technical issues, and imagine the future.
## Listing policy {#listing-policy}
diff --git a/public/content/contributing/index.md b/public/content/contributing/index.md
index 5a18d529eb3..b37c2b4d20c 100644
--- a/public/content/contributing/index.md
+++ b/public/content/contributing/index.md
@@ -8,7 +8,7 @@ lang: en
Ethereum.org is an open-source run project with **12 000+** contributors that help translate, write, design and maintain the website.
-We are a welcoming community that will help you grow and educate in the Ethereum ecosystem while also meaningfully contribute and get relevant practical experience!
+We are a welcoming community that will help you grow and educate in the [Ethereum](/) ecosystem while also meaningfully contribute and get relevant practical experience!
## Ways to contribute {#ways-to-contribute}
diff --git a/public/content/contributing/translation-program/index.md b/public/content/contributing/translation-program/index.md
index c87ec18f936..a8250ff04c0 100644
--- a/public/content/contributing/translation-program/index.md
+++ b/public/content/contributing/translation-program/index.md
@@ -28,7 +28,7 @@ _Join the [ethereum.org Discord](https://discord.gg/ethereum-org) to collaborate
## About the Translation Program {#about-us}
-The Ethereum community aims to be global and inclusive, yet much of its content only caters to English speakers, leaving out the world's 6 billion non-English speakers. For ethereum.org to act as the portal into Ethereum for the worldwide community, we believe providing non-English speakers with Ethereum content in their native languages is essential.
+The [Ethereum](/) community aims to be global and inclusive, yet much of its content only caters to English speakers, leaving out the world's 6 billion non-English speakers. For ethereum.org to act as the portal into Ethereum for the worldwide community, we believe providing non-English speakers with Ethereum content in their native languages is essential.
The ethereum.org Translation Program aims to make Ethereum accessible to everyone by translating ethereum.org and other Ethereum content into as many languages as possible.
diff --git a/public/content/contributing/translation-program/translatathon/index.md b/public/content/contributing/translation-program/translatathon/index.md
index 686d3467cda..abcb62f1eec 100644
--- a/public/content/contributing/translation-program/translatathon/index.md
+++ b/public/content/contributing/translation-program/translatathon/index.md
@@ -24,7 +24,7 @@ template: translatathon
## Introduction {#introduction}
-We believe that Ethereum content and onboarding resources should be accessible to everyone, regardless of the language they speak.
+We believe that [Ethereum](/) content and onboarding resources should be accessible to everyone, regardless of the language they speak.
To move closer to this goal, the ethereum.org translation program is an initiative to translate the website into as many languages as possible.
As part of the translation program, we are organizing the 3rd edition of the Translatathon, our translation contest that aims to incentivize translation contributions in less-active languages, increase the number of languages and amount of content available on the site, onboard new contributors and reward our existing ones.
diff --git a/public/content/decentralized-identity/index.md b/public/content/decentralized-identity/index.md
index 714e8df822f..1f3f76c3d3c 100644
--- a/public/content/decentralized-identity/index.md
+++ b/public/content/decentralized-identity/index.md
@@ -15,7 +15,7 @@ Identity underpins virtually every aspect of your life today. Using online servi
However, traditional identity management systems have long relied on centralized intermediaries who issue, hold, and control your identifiers and [attestations](/glossary/#attestation). This means you cannot control your identity-related information or decide who has access to personally identifiable information (PII) and how much access these parties have.
-To solve these problems, we have decentralized identity systems built on public blockchains like Ethereum. Decentralized identity allows individuals to manage their identity-related information. With decentralized identity solutions, _you_ can create identifiers and claim and hold your attestations without relying on central authorities, like service providers or governments.
+To solve these problems, we have decentralized identity systems built on public blockchains like [Ethereum](/). Decentralized identity allows individuals to manage their identity-related information. With decentralized identity solutions, _you_ can create identifiers and claim and hold your attestations without relying on central authorities, like service providers or governments.
## What is identity? {#what-is-identity}
diff --git a/public/content/desci/index.md b/public/content/desci/index.md
index 2bacd4286c2..80656a9ed4a 100644
--- a/public/content/desci/index.md
+++ b/public/content/desci/index.md
@@ -41,7 +41,7 @@ An incomplete list of key problems in science and how decentralized science can
## Ethereum and DeSci {#ethereum-and-desci}
-A decentralized science system will require robust security, minimal monetary and transaction costs, and a rich ecosystem for application development. Ethereum provides everything needed for building a decentralized science technology.
+A decentralized science system will require robust security, minimal monetary and transaction costs, and a rich ecosystem for application development. [Ethereum](/) provides everything needed for building a decentralized science technology.
## DeSci use cases {#use-cases}
diff --git a/public/content/developers/docs/accounts/index.md b/public/content/developers/docs/accounts/index.md
index e79bb205ff8..c51c62a0331 100644
--- a/public/content/developers/docs/accounts/index.md
+++ b/public/content/developers/docs/accounts/index.md
@@ -4,7 +4,7 @@ description: An explanation of Ethereum accounts – their data structures and t
lang: en
---
-An Ethereum account is an entity with an ether (ETH) balance that can send messages on Ethereum. Accounts can be user-controlled or deployed as smart contracts.
+An [Ethereum](/) account is an entity with an ether (ETH) balance that can send messages on Ethereum. Accounts can be user-controlled or deployed as smart contracts.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/apis/backend/index.md b/public/content/developers/docs/apis/backend/index.md
index 1d17b3f5b47..7bcf0333c0f 100644
--- a/public/content/developers/docs/apis/backend/index.md
+++ b/public/content/developers/docs/apis/backend/index.md
@@ -4,7 +4,7 @@ description: An introduction to the Ethereum client APIs that let you interact w
lang: en
---
-In order for a software application to interact with the Ethereum blockchain (i.e., read blockchain data and/or send transactions to the network), it must connect to an Ethereum node.
+In order for a software application to interact with the [Ethereum](/) blockchain (i.e., read blockchain data and/or send transactions to the network), it must connect to an Ethereum node.
For this purpose, every Ethereum client implements the [JSON-RPC](/developers/docs/apis/json-rpc/) specification, so there is a uniform set of [methods](/developers/docs/apis/json-rpc/#json-rpc-methods) that applications can rely on.
diff --git a/public/content/developers/docs/apis/json-rpc/index.md b/public/content/developers/docs/apis/json-rpc/index.md
index 576b10c6028..85533399299 100755
--- a/public/content/developers/docs/apis/json-rpc/index.md
+++ b/public/content/developers/docs/apis/json-rpc/index.md
@@ -4,7 +4,7 @@ description: A stateless, light-weight remote procedure call (RPC) protocol for
lang: en
---
-In order for a software application to interact with the Ethereum blockchain - either by reading blockchain data or sending transactions to the network - it must connect to an Ethereum node.
+In order for a software application to interact with the [Ethereum](/) blockchain - either by reading blockchain data or sending transactions to the network - it must connect to an Ethereum node.
For this purpose, every [Ethereum client](/developers/docs/nodes-and-clients/#execution-clients) implements a [JSON-RPC specification](https://github.com/ethereum/execution-apis), so there is a uniform set of methods that applications can rely on regardless of the specific node or client implementation.
diff --git a/public/content/developers/docs/blocks/index.md b/public/content/developers/docs/blocks/index.md
index 1ad0f4c1725..3a02e25a49d 100644
--- a/public/content/developers/docs/blocks/index.md
+++ b/public/content/developers/docs/blocks/index.md
@@ -12,7 +12,7 @@ Blocks are a very beginner-friendly topic. But to help you better understand thi
## Why blocks? {#why-blocks}
-To ensure that all participants on the Ethereum network maintain a synchronized state and agree on the precise history of transactions, we batch transactions into blocks. This means dozens (or hundreds) of transactions are committed, agreed on, and synchronized all at once.
+To ensure that all participants on the [Ethereum](/) network maintain a synchronized state and agree on the precise history of transactions, we batch transactions into blocks. This means dozens (or hundreds) of transactions are committed, agreed on, and synchronized all at once.
_Diagram adapted from [Ethereum EVM illustrated](https://takenobu-hs.github.io/downloads/ethereum_evm_illustrated.pdf)_
diff --git a/public/content/developers/docs/bridges/index.md b/public/content/developers/docs/bridges/index.md
index 0357d8e5143..5c470b2a46c 100644
--- a/public/content/developers/docs/bridges/index.md
+++ b/public/content/developers/docs/bridges/index.md
@@ -23,7 +23,7 @@ Blockchains have unique strengths, weaknesses, and approaches to building applic
For developers, bridges enable the following:
- the transfer of any data, information, and assets across chains.
-- unlocking new features and use cases for protocols as bridges expand the design space for what protocols can offer. For example, a protocol for yield farming originally deployed on Ethereum Mainnet can offer liquidity pools across all EVM-compatible chains.
+- unlocking new features and use cases for protocols as bridges expand the design space for what protocols can offer. For example, a protocol for yield farming originally deployed on [Ethereum](/) Mainnet can offer liquidity pools across all EVM-compatible chains.
- the opportunity to leverage the strengths of different blockchains. For example, developers can benefit from the lower fees offered by the different L2 solutions by deploying their dapps across rollups, and sidechains and users can bridge across them.
- collaboration among developers from various blockchain ecosystems to build new products.
- attracting users and communities from various ecosystems to their dapps.
diff --git a/public/content/developers/docs/consensus-mechanisms/index.md b/public/content/developers/docs/consensus-mechanisms/index.md
index 2f9beca4247..f463a74a3e8 100644
--- a/public/content/developers/docs/consensus-mechanisms/index.md
+++ b/public/content/developers/docs/consensus-mechanisms/index.md
@@ -14,7 +14,7 @@ To better understand this page, we recommend you first read our [introduction to
By consensus, we mean that a general agreement has been reached. Consider a group of people going to the cinema. If there is no disagreement on a proposed choice of film, then a consensus is achieved. If there is disagreement, the group must have the means to decide which film to see. In extreme cases, the group will eventually split.
-In regard to the Ethereum blockchain, the process is formalized, and reaching consensus means that at least 66% of the nodes on the network agree on the global state of the network.
+In regard to the [Ethereum](/) blockchain, the process is formalized, and reaching consensus means that at least 66% of the nodes on the network agree on the global state of the network.
## What is a consensus mechanism? {#what-is-a-consensus-mechanism}
diff --git a/public/content/developers/docs/consensus-mechanisms/pos/attack-and-defense/index.md b/public/content/developers/docs/consensus-mechanisms/pos/attack-and-defense/index.md
index 7fab50d7e92..47ec0c54898 100644
--- a/public/content/developers/docs/consensus-mechanisms/pos/attack-and-defense/index.md
+++ b/public/content/developers/docs/consensus-mechanisms/pos/attack-and-defense/index.md
@@ -4,7 +4,7 @@ description: Learn about the known attack vectors on proof-of-stake Ethereum and
lang: en
---
-Thieves and saboteurs are constantly seeking opportunities to attack Ethereum’s client software. This page outlines the known attack vectors on Ethereum’s consensus layer and outlines how those attacks can be defended. The information on this page is adapted from a [longer form version](https://mirror.xyz/jmcook.eth/YqHargbVWVNRQqQpVpzrqEQ8IqwNUJDIpwRP7SS5FXs).
+Thieves and saboteurs are constantly seeking opportunities to attack [Ethereum](/)’s client software. This page outlines the known attack vectors on Ethereum’s consensus layer and outlines how those attacks can be defended. The information on this page is adapted from a [longer form version](https://mirror.xyz/jmcook.eth/YqHargbVWVNRQqQpVpzrqEQ8IqwNUJDIpwRP7SS5FXs).
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/consensus-mechanisms/pos/block-proposal/index.md b/public/content/developers/docs/consensus-mechanisms/pos/block-proposal/index.md
index 3253df6aa9b..4c081f3b56c 100644
--- a/public/content/developers/docs/consensus-mechanisms/pos/block-proposal/index.md
+++ b/public/content/developers/docs/consensus-mechanisms/pos/block-proposal/index.md
@@ -12,7 +12,7 @@ Block proposal is part of the proof-of-stake protocol. To help understand this p
## Who produces blocks? {#who-produces-blocks}
-Validator accounts propose blocks. Validator accounts are managed by node operators who run validator software as part of their execution and consensus clients and have deposited at least 32 ETH into the deposit contract. However, each validator is only occasionally responsible for proposing a block. Ethereum measures time in slots and epochs. Each slot is twelve seconds, and 32 slots (6.4 minutes) make up an epoch. Every slot is an opportunity to add a new block on Ethereum.
+Validator accounts propose blocks. Validator accounts are managed by node operators who run validator software as part of their execution and consensus clients and have deposited at least 32 ETH into the deposit contract. However, each validator is only occasionally responsible for proposing a block. [Ethereum](/) measures time in slots and epochs. Each slot is twelve seconds, and 32 slots (6.4 minutes) make up an epoch. Every slot is an opportunity to add a new block on Ethereum.
### Random selection {#random-selection}
diff --git a/public/content/developers/docs/consensus-mechanisms/pos/index.md b/public/content/developers/docs/consensus-mechanisms/pos/index.md
index 70a862bafab..47e09d9b0d3 100644
--- a/public/content/developers/docs/consensus-mechanisms/pos/index.md
+++ b/public/content/developers/docs/consensus-mechanisms/pos/index.md
@@ -4,7 +4,7 @@ description: An explanation of the proof-of-stake consensus protocol and its rol
lang: en
---
-Proof-of-stake (PoS) underlies Ethereum's [consensus mechanism](/developers/docs/consensus-mechanisms/). [Ethereum](/) switched on its proof-of-stake mechanism in 2022 because it is more secure, less energy-intensive, and better for implementing new scaling solutions compared to the previous [proof-of-work](/developers/docs/consensus-mechanisms/pow) architecture.
+Proof-of-stake (PoS) underlies Ethereum's [consensus mechanism](/developers/docs/consensus-mechanisms/). Ethereum switched on its proof-of-stake mechanism in 2022 because it is more secure, less energy-intensive, and better for implementing new scaling solutions compared to the previous [proof-of-work](/developers/docs/consensus-mechanisms/pow) architecture.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/consensus-mechanisms/pos/pos-vs-pow/index.md b/public/content/developers/docs/consensus-mechanisms/pos/pos-vs-pow/index.md
index 872f6834f35..244b4dff283 100644
--- a/public/content/developers/docs/consensus-mechanisms/pos/pos-vs-pow/index.md
+++ b/public/content/developers/docs/consensus-mechanisms/pos/pos-vs-pow/index.md
@@ -4,7 +4,7 @@ description: A comparison between Ethereum's proof-of-stake and proof-of-work ba
lang: en
---
-When Ethereum launched, proof-of-stake still needed a lot of research and development before it could be trusted to secure Ethereum. Proof-of-work was a simpler mechanism that had already been proven by Bitcoin, meaning core developers could implement it right away to get Ethereum launched. It took a further eight years to develop proof-of-stake to the point where it could be implemented.
+When [Ethereum](/) launched, proof-of-stake still needed a lot of research and development before it could be trusted to secure Ethereum. Proof-of-work was a simpler mechanism that had already been proven by Bitcoin, meaning core developers could implement it right away to get Ethereum launched. It took a further eight years to develop proof-of-stake to the point where it could be implemented.
This page explains the rationale behind Ethereum's switch to proof-of-stake from proof-of-work and the trade-offs involved.
diff --git a/public/content/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md
index d1b1208feca..48df0368231 100644
--- a/public/content/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md
+++ b/public/content/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md
@@ -4,7 +4,7 @@ description: Learn about the in-protocol incentives in proof-of-stake Ethereum.
lang: en
---
-Ethereum is secured using its native cryptocurrency, ether (ETH). Node operators that wish to participate in validating blocks and identifying the head of the chain, deposit ether into the [deposit contract](/staking/deposit-contract/) on Ethereum. They are then paid in ether to run validator software that checks the validity of new blocks received over the peer-to-peer network and apply the fork-choice algorithm to identify the head of the chain.
+[Ethereum](/) is secured using its native cryptocurrency, ether (ETH). Node operators that wish to participate in validating blocks and identifying the head of the chain, deposit ether into the [deposit contract](/staking/deposit-contract/) on Ethereum. They are then paid in ether to run validator software that checks the validity of new blocks received over the peer-to-peer network and apply the fork-choice algorithm to identify the head of the chain.
There are two primary roles for a validator: 1) checking new blocks and “attesting” to them if they are valid, 2) proposing new blocks when selected at random from the total validator pool. If the validator fails to do either of these tasks when asked they miss out on an ether payout. Validators are also sometimes tasked with signature aggregation and participating in sync committees.
diff --git a/public/content/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md
index 2f65bcc0885..2796fd851c5 100644
--- a/public/content/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md
+++ b/public/content/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md
@@ -12,7 +12,7 @@ To understand this page it is necessary to first understand the fundamentals of
## What problems does weak subjectivity solve? {#problems-ws-solves}
-Subjectivity is inherent to proof-of-stake blockchains because selecting the correct chain from multiple forks is done by counting historical votes. This exposes the blockchain to several attack vectors, including long-range attacks whereby nodes that participated very early in the chain maintain an alternative fork that they release much later to their own advantage. Alternatively, if 33% of validators withdraw their stake but continue to attest and produce blocks, they might generate an alternative fork that conflicts with the canonical chain. New nodes or nodes that have been offline for a long time might not be aware that these attacking validators have withdrawn their funds, so attackers could trick them into following an incorrect chain. Ethereum can solve these attack vectors by imposing constraints that diminish the subjective aspects of the mechanism—and therefore trust assumptions—to the bare minimum.
+Subjectivity is inherent to proof-of-stake blockchains because selecting the correct chain from multiple forks is done by counting historical votes. This exposes the blockchain to several attack vectors, including long-range attacks whereby nodes that participated very early in the chain maintain an alternative fork that they release much later to their own advantage. Alternatively, if 33% of validators withdraw their stake but continue to attest and produce blocks, they might generate an alternative fork that conflicts with the canonical chain. New nodes or nodes that have been offline for a long time might not be aware that these attacking validators have withdrawn their funds, so attackers could trick them into following an incorrect chain. [Ethereum](/) can solve these attack vectors by imposing constraints that diminish the subjective aspects of the mechanism—and therefore trust assumptions—to the bare minimum.
## Weak subjectivity checkpoints {#ws-checkpoints}
diff --git a/public/content/developers/docs/consensus-mechanisms/pow/index.md b/public/content/developers/docs/consensus-mechanisms/pow/index.md
index d56070c2863..20002a2885d 100644
--- a/public/content/developers/docs/consensus-mechanisms/pow/index.md
+++ b/public/content/developers/docs/consensus-mechanisms/pow/index.md
@@ -4,7 +4,7 @@ description: An explanation of the proof-of-work consensus protocol and its role
lang: en
---
-The Ethereum network began by using a consensus mechanism that involved **[Proof-of-work (PoW)](/developers/docs/consensus-mechanisms/pow)**. This allowed the nodes of the Ethereum network to agree on the state of all information recorded on the Ethereum blockchain and prevented certain kinds of economic attacks. However, Ethereum switched off proof-of-work in 2022 and started using [proof-of-stake](/developers/docs/consensus-mechanisms/pos) instead.
+The [Ethereum](/) network began by using a consensus mechanism that involved **[Proof-of-work (PoW)](/developers/docs/consensus-mechanisms/pow)**. This allowed the nodes of the Ethereum network to agree on the state of all information recorded on the Ethereum blockchain and prevented certain kinds of economic attacks. However, Ethereum switched off proof-of-work in 2022 and started using [proof-of-stake](/developers/docs/consensus-mechanisms/pos) instead.
diff --git a/public/content/developers/docs/consensus-mechanisms/pow/mining/index.md b/public/content/developers/docs/consensus-mechanisms/pow/mining/index.md
index 89ba6c6f9aa..d5696e44831 100644
--- a/public/content/developers/docs/consensus-mechanisms/pow/mining/index.md
+++ b/public/content/developers/docs/consensus-mechanisms/pow/mining/index.md
@@ -8,7 +8,7 @@ lang: en
-Proof-of-work is no longer underlying Ethereum's consensus mechanism, meaning mining has been switched off. Instead, Ethereum is secured by validators who stake ETH. You can start staking your ETH today. Read more on The Merge, proof-of-stake, and staking. This page is for historical interest only.
+Proof-of-work is no longer underlying Ethereum's consensus mechanism, meaning mining has been switched off. Instead, [Ethereum](/) is secured by validators who stake ETH. You can start staking your ETH today. Read more on The Merge, proof-of-stake, and staking. This page is for historical interest only.
diff --git a/public/content/developers/docs/dapps/index.md b/public/content/developers/docs/dapps/index.md
index 9d9a8de53ab..896604ee133 100644
--- a/public/content/developers/docs/dapps/index.md
+++ b/public/content/developers/docs/dapps/index.md
@@ -4,7 +4,7 @@ description:
lang: en
---
-A decentralized application (dapp) is an application built on a decentralized network that combines a [smart contract](/developers/docs/smart-contracts/) and a frontend user interface. On Ethereum, smart contracts are accessible and transparent – like open APIs – so your dapp can even include a smart contract that someone else has written.
+A decentralized application (dapp) is an application built on a decentralized network that combines a [smart contract](/developers/docs/smart-contracts/) and a frontend user interface. On [Ethereum](/), smart contracts are accessible and transparent – like open APIs – so your dapp can even include a smart contract that someone else has written.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/data-availability/index.md b/public/content/developers/docs/data-availability/index.md
index 07109c0b917..eb1673c15b5 100644
--- a/public/content/developers/docs/data-availability/index.md
+++ b/public/content/developers/docs/data-availability/index.md
@@ -6,7 +6,7 @@ lang: en
"Don't trust, verify" is a common maxim in Ethereum. The idea is that your node can independently verify that the information it receives is correct by executing all the transactions in the blocks they receive from peers to ensure that the changes proposed precisely match those computed independently by the node. This means nodes do not have to trust that the senders of the block are honest. This is not possible if data is missing.
-**Data availability** refers to the confidence a user can have that the data required to verify a block is really available to all network participants. For full nodes on Ethereum layer 1 this is relatively simple; the full node downloads a copy of all the data in each block - the data _has_ to be available for the downloading to be possible. A block with missing data would be discarded rather than being added to the blockchain. This is "onchain data availability" and it is a feature of monolithic blockchains. Full nodes cannot be tricked into accepting invalid transactions because they download and execute every transaction for themselves. However, for modular blockchains, layer 2 rollups and light clients, the data availability landscape is more complex, requiring some more sophisticated verification procedures.
+**Data availability** refers to the confidence a user can have that the data required to verify a block is really available to all network participants. For full nodes on [Ethereum](/) layer 1 this is relatively simple; the full node downloads a copy of all the data in each block - the data _has_ to be available for the downloading to be possible. A block with missing data would be discarded rather than being added to the blockchain. This is "onchain data availability" and it is a feature of monolithic blockchains. Full nodes cannot be tricked into accepting invalid transactions because they download and execute every transaction for themselves. However, for modular blockchains, layer 2 rollups and light clients, the data availability landscape is more complex, requiring some more sophisticated verification procedures.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/data-structures-and-encoding/patricia-merkle-trie/index.md b/public/content/developers/docs/data-structures-and-encoding/patricia-merkle-trie/index.md
index 6403c669d27..b3dac9cf97f 100644
--- a/public/content/developers/docs/data-structures-and-encoding/patricia-merkle-trie/index.md
+++ b/public/content/developers/docs/data-structures-and-encoding/patricia-merkle-trie/index.md
@@ -5,7 +5,7 @@ lang: en
sidebarDepth: 2
---
-The state of Ethereum (the totality of all accounts, balances, and smart contracts), is encoded into a special version of the data structure known generally in computer science as a Merkle Tree. This structure is useful for many applications in cryptography because it creates a verifiable relationship between all the individual pieces of data entangled in the tree, resulting in a single **root** value that can be used to prove things about the data.
+The state of [Ethereum](/) (the totality of all accounts, balances, and smart contracts), is encoded into a special version of the data structure known generally in computer science as a Merkle Tree. This structure is useful for many applications in cryptography because it creates a verifiable relationship between all the individual pieces of data entangled in the tree, resulting in a single **root** value that can be used to prove things about the data.
Ethereum's data structure is a 'modified Merkle-Patricia Trie', named so because it borrows some features of PATRICIA (the Practical Algorithm To Retrieve Information Coded in Alphanumeric), and because it is designed for efficient data re**trie**val of items that comprise the Ethereum state.
diff --git a/public/content/developers/docs/data-structures-and-encoding/rlp/index.md b/public/content/developers/docs/data-structures-and-encoding/rlp/index.md
index 0370d61c4f2..d825f28af4f 100644
--- a/public/content/developers/docs/data-structures-and-encoding/rlp/index.md
+++ b/public/content/developers/docs/data-structures-and-encoding/rlp/index.md
@@ -12,7 +12,7 @@ More information in [the Ethereum yellow paper (Appendix B)](https://ethereum.gi
To use RLP to encode a dictionary, the two suggested canonical forms are:
- use `[[k1,v1],[k2,v2]...]` with keys in lexicographic order
-- use the higher-level Patricia Tree encoding as Ethereum does
+- use the higher-level Patricia Tree encoding as [Ethereum](/) does
## Definition {#definition}
diff --git a/public/content/developers/docs/development-networks/index.md b/public/content/developers/docs/development-networks/index.md
index 9c60696a2d9..5e177db4564 100644
--- a/public/content/developers/docs/development-networks/index.md
+++ b/public/content/developers/docs/development-networks/index.md
@@ -4,7 +4,7 @@ description: An overview of development networks and the tools available to help
lang: en
---
-When building an Ethereum application with smart contracts, you'll want to run it on a local network to see how it works before deploying it.
+When building an [Ethereum](/) application with smart contracts, you'll want to run it on a local network to see how it works before deploying it.
Similar to how you might run a local server on your computer for web development, you can use a development network to create a local blockchain instance to test your dapp. These Ethereum development networks provide features that allow for much faster iteration than a public testnet (for instance you don’t need to deal with acquiring ETH from a testnet faucet).
diff --git a/public/content/developers/docs/evm/index.md b/public/content/developers/docs/evm/index.md
index 2c5fe403028..cad285b9cff 100644
--- a/public/content/developers/docs/evm/index.md
+++ b/public/content/developers/docs/evm/index.md
@@ -4,7 +4,7 @@ description: An introduction to the Ethereum virtual machine and how it relates
lang: en
---
-The [Ethereum](/) Virtual Machine (EVM) is a decentralized virtual environment that executes code consistently and securely across all [Ethereum](/) nodes. Nodes run the EVM to execute smart contracts, using "[gas](/developers/docs/gas/)" to measure the computational effort required for [operations](/developers/docs/evm/opcodes/), ensuring efficient resource allocation and network security.
+The Ethereum Virtual Machine (EVM) is a decentralized virtual environment that executes code consistently and securely across all [Ethereum](/) nodes. Nodes run the EVM to execute smart contracts, using "[gas](/developers/docs/gas/)" to measure the computational effort required for [operations](/developers/docs/evm/opcodes/), ensuring efficient resource allocation and network security.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/index.md b/public/content/developers/docs/index.md
index d843501b46e..cee013899b0 100644
--- a/public/content/developers/docs/index.md
+++ b/public/content/developers/docs/index.md
@@ -4,7 +4,7 @@ description: Introducing the ethereum.org developer documentation.
lang: en
---
-This documentation is designed to help you build with Ethereum. It covers Ethereum as a concept, explains the Ethereum tech stack, and documents advanced topics for more complex applications and use cases.
+This documentation is designed to help you build with [Ethereum](/). It covers Ethereum as a concept, explains the Ethereum tech stack, and documents advanced topics for more complex applications and use cases.
This is an open-source community effort, so feel free to suggest new topics, add new content, and provide examples wherever you think it might be helpful. All documentation can be edited via GitHub – if you're unsure how, [follow these instructions](https://github.com/ethereum/ethereum-org-website/blob/dev/docs/editing-markdown.md).
diff --git a/public/content/developers/docs/intro-to-ethereum/index.md b/public/content/developers/docs/intro-to-ethereum/index.md
index 749d63feab6..af1e26fedc2 100644
--- a/public/content/developers/docs/intro-to-ethereum/index.md
+++ b/public/content/developers/docs/intro-to-ethereum/index.md
@@ -14,7 +14,7 @@ A blockchain is a public database that is updated and shared across many compute
Every computer in the network must agree upon each new block and the chain as a whole. These computers are known as "nodes". Nodes ensure everyone interacting with the blockchain has the same data. To accomplish this distributed agreement, blockchains need a consensus mechanism.
-Ethereum uses a [proof-of-stake-based consensus mechanism](/developers/docs/consensus-mechanisms/pos/). Anyone who wants to add new blocks to the chain must stake ETH - the native currency in Ethereum - as collateral and run validator software. These "validators" can then be randomly selected to propose blocks that other validators check and add to the blockchain. There is a system of rewards and penalties that strongly incentivize participants to be honest and available online as much as possible.
+[Ethereum](/) uses a [proof-of-stake-based consensus mechanism](/developers/docs/consensus-mechanisms/pos/). Anyone who wants to add new blocks to the chain must stake ETH - the native currency in Ethereum - as collateral and run validator software. These "validators" can then be randomly selected to propose blocks that other validators check and add to the blockchain. There is a system of rewards and penalties that strongly incentivize participants to be honest and available online as much as possible.
If you would like to see how blockchain data is hashed and subsequently appended to the history of block references, be sure to check out [this demo](https://andersbrownworth.com/blockchain/blockchain) by Anders Brownworth and watch the accompanying video below.
diff --git a/public/content/developers/docs/mev/index.md b/public/content/developers/docs/mev/index.md
index 7d04757719b..ffd4471c73b 100644
--- a/public/content/developers/docs/mev/index.md
+++ b/public/content/developers/docs/mev/index.md
@@ -8,7 +8,7 @@ Maximal extractable value (MEV) refers to the maximum value that can be extracte
## Maximal extractable value {#maximal-extractable-value}
-Maximal extractable value was first applied in the context of [proof-of-work](/developers/docs/consensus-mechanisms/pow/), and initially referred to as "miner extractable value". This is because in proof-of-work, miners control transaction inclusion, exclusion, and ordering. However, since the transition to proof-of-stake via [The Merge](/roadmap/merge) validators have been responsible for these roles, and mining is no longer part of the Ethereum protocol. The value extraction methods still exist, though, so the term "Maximal extractable value" is now used instead.
+Maximal extractable value was first applied in the context of [proof-of-work](/developers/docs/consensus-mechanisms/pow/), and initially referred to as "miner extractable value". This is because in proof-of-work, miners control transaction inclusion, exclusion, and ordering. However, since the transition to proof-of-stake via [The Merge](/roadmap/merge) validators have been responsible for these roles, and mining is no longer part of the [Ethereum](/) protocol. The value extraction methods still exist, though, so the term "Maximal extractable value" is now used instead.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/networking-layer/index.md b/public/content/developers/docs/networking-layer/index.md
index c04adcc328e..7279690eb9f 100644
--- a/public/content/developers/docs/networking-layer/index.md
+++ b/public/content/developers/docs/networking-layer/index.md
@@ -5,7 +5,7 @@ lang: en
sidebarDepth: 2
---
-Ethereum is a peer-to-peer network with thousands of nodes that must be able to communicate with one another using standardized protocols. The "networking layer" is the stack of protocols that allow those nodes to find each other and exchange information. This includes "gossiping" information (one-to-many communication) over the network as well as swapping requests and responses between specific nodes (one-to-one communication). Each node must adhere to specific networking rules to ensure they are sending and receiving the correct information.
+[Ethereum](/) is a peer-to-peer network with thousands of nodes that must be able to communicate with one another using standardized protocols. The "networking layer" is the stack of protocols that allow those nodes to find each other and exchange information. This includes "gossiping" information (one-to-many communication) over the network as well as swapping requests and responses between specific nodes (one-to-one communication). Each node must adhere to specific networking rules to ensure they are sending and receiving the correct information.
There are two parts to the client software (execution clients and consensus clients), each with its own distinct networking stack. As well as communicating with other Ethereum nodes, the execution and consensus clients have to communicate with each other. This page gives an introductory explanation of the protocols that enable this communication.
diff --git a/public/content/developers/docs/networking-layer/network-addresses/index.md b/public/content/developers/docs/networking-layer/network-addresses/index.md
index 8fcfbf8a97c..5d6f9d9e298 100644
--- a/public/content/developers/docs/networking-layer/network-addresses/index.md
+++ b/public/content/developers/docs/networking-layer/network-addresses/index.md
@@ -5,7 +5,7 @@ lang: en
sidebarDepth: 2
---
-Ethereum nodes have to identify themselves with some basic information to connect to peers. To ensure any potential peer can interpret this information, it is relayed in one of three standardized formats that any Ethereum node can understand: multiaddr, enode, or Ethereum Node Records (ENRs). ENRs are the current standard for Ethereum network addresses.
+[Ethereum](/) nodes have to identify themselves with some basic information to connect to peers. To ensure any potential peer can interpret this information, it is relayed in one of three standardized formats that any Ethereum node can understand: multiaddr, enode, or Ethereum Node Records (ENRs). ENRs are the current standard for Ethereum network addresses.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/networking-layer/portal-network/index.md b/public/content/developers/docs/networking-layer/portal-network/index.md
index bac3a76de82..398fc9c59c0 100644
--- a/public/content/developers/docs/networking-layer/portal-network/index.md
+++ b/public/content/developers/docs/networking-layer/portal-network/index.md
@@ -4,7 +4,7 @@ description: An overview of the Portal Network - an in-development network desig
lang: en
---
-Ethereum is a network made up of computers that run Ethereum client software. Each of these computers is called a 'node'. The client software allows a node to send and receive data on the Ethereum network, and verifies data against the Ethereum protocol rules. Nodes keep a lot of historical data in their disk storage and add to it when they receive new packets of information, known as blocks, from other nodes on the network. This is necessary for always checking that a node has information consistent with the rest of the network. This means running a node can require a lot of disk space. Some node operations can require a lot of RAM too.
+[Ethereum](/) is a network made up of computers that run Ethereum client software. Each of these computers is called a 'node'. The client software allows a node to send and receive data on the Ethereum network, and verifies data against the Ethereum protocol rules. Nodes keep a lot of historical data in their disk storage and add to it when they receive new packets of information, known as blocks, from other nodes on the network. This is necessary for always checking that a node has information consistent with the rest of the network. This means running a node can require a lot of disk space. Some node operations can require a lot of RAM too.
To get around this disk storage problem, 'light' nodes have been developed that request information from full nodes instead of storing it all themselves. However, this means the light node is not independently verifying the information and is trusting another node instead. It also means that full nodes are required to take on extra work to serve those light nodes.
diff --git a/public/content/developers/docs/networks/index.md b/public/content/developers/docs/networks/index.md
index 439f7fda311..5c8cc7d0333 100644
--- a/public/content/developers/docs/networks/index.md
+++ b/public/content/developers/docs/networks/index.md
@@ -4,7 +4,7 @@ description: An overview of Ethereum's networks and where to get testnet ether (
lang: en
---
-Ethereum networks are groups of connected computers that communicate using the Ethereum protocol. There is only one Ethereum Mainnet, but independent networks conforming to the same protocol rules can be created for testing and development purposes. There are many independent "networks" that conform to the protocol without interacting with each other. You can even start one locally on your own computer for testing your smart contracts and web3 apps.
+[Ethereum](/) networks are groups of connected computers that communicate using the Ethereum protocol. There is only one Ethereum Mainnet, but independent networks conforming to the same protocol rules can be created for testing and development purposes. There are many independent "networks" that conform to the protocol without interacting with each other. You can even start one locally on your own computer for testing your smart contracts and web3 apps.
Your Ethereum account will work across the different networks, but your account balance and transaction history won't carry over from the main Ethereum network. For testing purposes, it's useful to know which networks are available and how to get testnet ETH to play around with. In general, for security considerations, it's not recommended to reuse mainnet accounts on testnets or vice versa.
diff --git a/public/content/developers/docs/nodes-and-clients/archive-nodes/index.md b/public/content/developers/docs/nodes-and-clients/archive-nodes/index.md
index a179c79fdba..196adecaed7 100644
--- a/public/content/developers/docs/nodes-and-clients/archive-nodes/index.md
+++ b/public/content/developers/docs/nodes-and-clients/archive-nodes/index.md
@@ -5,7 +5,7 @@ lang: en
sidebarDepth: 2
---
-An archive node is an instance of an Ethereum client configured to build an archive of all historical states. It is a useful tool for certain use cases but might be more tricky to run than a full node.
+An archive node is an instance of an [Ethereum](/) client configured to build an archive of all historical states. It is a useful tool for certain use cases but might be more tricky to run than a full node.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/nodes-and-clients/client-diversity/index.md b/public/content/developers/docs/nodes-and-clients/client-diversity/index.md
index 0a6c84a7534..3bd65be7c9e 100644
--- a/public/content/developers/docs/nodes-and-clients/client-diversity/index.md
+++ b/public/content/developers/docs/nodes-and-clients/client-diversity/index.md
@@ -5,7 +5,7 @@ lang: en
sidebarDepth: 2
---
-The behavior of an Ethereum node is controlled by the client software it runs. There are several production-level Ethereum clients, each one developed and maintained in different languages by separate teams. The clients are built to a common spec that ensures the clients seamlessly communicate with each other and have the same functionality and provide an equivalent user experience. However, at the moment the distribution of clients across nodes is not equal enough to realize this network fortification to its full potential. Ideally, users divide roughly equally across the various clients to bring as much client diversity as possible to the network.
+The behavior of an [Ethereum](/) node is controlled by the client software it runs. There are several production-level Ethereum clients, each one developed and maintained in different languages by separate teams. The clients are built to a common spec that ensures the clients seamlessly communicate with each other and have the same functionality and provide an equivalent user experience. However, at the moment the distribution of clients across nodes is not equal enough to realize this network fortification to its full potential. Ideally, users divide roughly equally across the various clients to bring as much client diversity as possible to the network.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/nodes-and-clients/index.md b/public/content/developers/docs/nodes-and-clients/index.md
index bb7b81d45a9..5a116b4b58b 100644
--- a/public/content/developers/docs/nodes-and-clients/index.md
+++ b/public/content/developers/docs/nodes-and-clients/index.md
@@ -5,7 +5,7 @@ lang: en
sidebarDepth: 2
---
-Ethereum is a distributed network of computers (known as nodes) running software that can verify blocks and transaction data. The software must be run on your computer to turn it into an Ethereum node. There are two separate pieces of software (known as 'clients') required to form a node.
+[Ethereum](/) is a distributed network of computers (known as nodes) running software that can verify blocks and transaction data. The software must be run on your computer to turn it into an Ethereum node. There are two separate pieces of software (known as 'clients') required to form a node.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/nodes-and-clients/light-clients/index.md b/public/content/developers/docs/nodes-and-clients/light-clients/index.md
index 564ad96b657..ac930d7f5ce 100644
--- a/public/content/developers/docs/nodes-and-clients/light-clients/index.md
+++ b/public/content/developers/docs/nodes-and-clients/light-clients/index.md
@@ -4,7 +4,7 @@ description: Introduction to Ethereum light clients.
lang: en
---
-Running a full node is the most trustless, private, decentralized and censorship resistant way to interact with Ethereum. With a full node you keep your own copy of the blockchain that you can query instantly and you get direct access to Ethereum's peer-to-peer network. However, running a full node requires a significant amount of memory, storage and CPU. This means it is not feasible for everyone to run their own node. There are several solutions to this on the Ethereum roadmap, including statelessness, but they are several years away from being implemented. The answer in the near-term is to trade-off some of the benefits of running a full node for large performance improvements that allow nodes to run with very low hardware requirements. Nodes that make this trade-off are known as light nodes.
+Running a full node is the most trustless, private, decentralized and censorship resistant way to interact with [Ethereum](/). With a full node you keep your own copy of the blockchain that you can query instantly and you get direct access to Ethereum's peer-to-peer network. However, running a full node requires a significant amount of memory, storage and CPU. This means it is not feasible for everyone to run their own node. There are several solutions to this on the Ethereum roadmap, including statelessness, but they are several years away from being implemented. The answer in the near-term is to trade-off some of the benefits of running a full node for large performance improvements that allow nodes to run with very low hardware requirements. Nodes that make this trade-off are known as light nodes.
## What is a light client {#what-is-a-light-client}
diff --git a/public/content/developers/docs/nodes-and-clients/run-a-node/index.md b/public/content/developers/docs/nodes-and-clients/run-a-node/index.md
index a197c5031d4..844aa496ac2 100644
--- a/public/content/developers/docs/nodes-and-clients/run-a-node/index.md
+++ b/public/content/developers/docs/nodes-and-clients/run-a-node/index.md
@@ -5,7 +5,7 @@ lang: en
sidebarDepth: 2
---
-Running your own node provides you various benefits, opens new possibilities, and helps to support the ecosystem. This page will guide you through spinning up your own node and taking part in validating Ethereum transactions.
+Running your own node provides you various benefits, opens new possibilities, and helps to support the ecosystem. This page will guide you through spinning up your own node and taking part in validating [Ethereum](/) transactions.
Note that after [The Merge](/roadmap/merge), two clients are required to run an Ethereum node; an **execution layer (EL)** client and a **consensus layer (CL)** client. This page will show how to install, configure and connect these two clients to run an Ethereum node.
diff --git a/public/content/developers/docs/oracles/index.md b/public/content/developers/docs/oracles/index.md
index 0d1078e4f94..98d591b3170 100644
--- a/public/content/developers/docs/oracles/index.md
+++ b/public/content/developers/docs/oracles/index.md
@@ -10,7 +10,7 @@ Giving smart contracts the ability to execute using offchain data extends the ut
## Prerequisites {#prerequisites}
-This page assumes the reader is familiar with Ethereum fundamentals, including [nodes](/developers/docs/nodes-and-clients/), [consensus mechanisms](/developers/docs/consensus-mechanisms/), and the [EVM](/developers/docs/evm/). You should also have a good grasp of [smart contracts](/developers/docs/smart-contracts/) and [smart contract anatomy](/developers/docs/smart-contracts/anatomy/), especially [events](/glossary/#events).
+This page assumes the reader is familiar with [Ethereum](/) fundamentals, including [nodes](/developers/docs/nodes-and-clients/), [consensus mechanisms](/developers/docs/consensus-mechanisms/), and the [EVM](/developers/docs/evm/). You should also have a good grasp of [smart contracts](/developers/docs/smart-contracts/) and [smart contract anatomy](/developers/docs/smart-contracts/anatomy/), especially [events](/glossary/#events).
## What is a blockchain oracle? {#what-is-a-blockchain-oracle}
diff --git a/public/content/developers/docs/scaling/index.md b/public/content/developers/docs/scaling/index.md
index c5e4c9bb8f4..6617e6be365 100644
--- a/public/content/developers/docs/scaling/index.md
+++ b/public/content/developers/docs/scaling/index.md
@@ -7,7 +7,7 @@ sidebarDepth: 3
## Scaling overview {#scaling-overview}
-As the number of people using Ethereum has grown, the blockchain has reached certain capacity limitations. This has driven up the cost of using the network, creating the need for "scaling solutions." There are multiple solutions being researched, tested and implemented that take different approaches to achieve similar goals.
+As the number of people using [Ethereum](/) has grown, the blockchain has reached certain capacity limitations. This has driven up the cost of using the network, creating the need for "scaling solutions." There are multiple solutions being researched, tested and implemented that take different approaches to achieve similar goals.
The main goal of scalability is to increase transaction speed (faster finality) and transaction throughput (higher number of transactions per second) without sacrificing decentralization or security. On the layer 1 Ethereum blockchain, high demand leads to slower transactions and nonviable [gas prices](/developers/docs/gas/). Increasing the network capacity in terms of speed and throughput is fundamental to the meaningful and mass adoption of Ethereum.
diff --git a/public/content/developers/docs/scaling/optimistic-rollups/index.md b/public/content/developers/docs/scaling/optimistic-rollups/index.md
index 1aa94adaa82..d63f2239988 100644
--- a/public/content/developers/docs/scaling/optimistic-rollups/index.md
+++ b/public/content/developers/docs/scaling/optimistic-rollups/index.md
@@ -4,7 +4,7 @@ description: An introduction to optimistic rollups—a scaling solution used by
lang: en
---
-Optimistic rollups are layer 2 (L2) protocols designed to extend the throughput of Ethereum's base layer. They reduce computation on the main Ethereum chain by processing transactions offchain, offering significant improvements in processing speeds. Unlike other scaling solutions, such as [sidechains](/developers/docs/scaling/sidechains/), optimistic rollups derive security from Mainnet by publishing transaction results onchain, or [plasma chains](/developers/docs/scaling/plasma/), which also verify transactions on Ethereum with fraud proofs, but store transaction data elsewhere.
+Optimistic rollups are layer 2 (L2) protocols designed to extend the throughput of Ethereum's base layer. They reduce computation on the main [Ethereum](/) chain by processing transactions offchain, offering significant improvements in processing speeds. Unlike other scaling solutions, such as [sidechains](/developers/docs/scaling/sidechains/), optimistic rollups derive security from Mainnet by publishing transaction results onchain, or [plasma chains](/developers/docs/scaling/plasma/), which also verify transactions on Ethereum with fraud proofs, but store transaction data elsewhere.
As computation is the slow, expensive part of using Ethereum, optimistic rollups can offer up to 10-100x improvements in scalability. Optimistic rollups also write transactions to Ethereum as `calldata` or in [blobs](/roadmap/danksharding/), reducing gas costs for users.
diff --git a/public/content/developers/docs/scaling/plasma/index.md b/public/content/developers/docs/scaling/plasma/index.md
index e4489ace36b..da728621477 100644
--- a/public/content/developers/docs/scaling/plasma/index.md
+++ b/public/content/developers/docs/scaling/plasma/index.md
@@ -6,7 +6,7 @@ incomplete: true
sidebarDepth: 3
---
-A Plasma chain is a separate blockchain anchored to Ethereum Mainnet but executing transactions offchain with its own mechanism for block validation. Plasma chains are sometimes referred to as "child" chains, essentially smaller copies of the Ethereum Mainnet. Plasma chains use [fraud proofs](/glossary/#fraud-proof) (like [optimistic rollups](/developers/docs/scaling/optimistic-rollups/)) to arbitrate disputes.
+A Plasma chain is a separate blockchain anchored to [Ethereum](/) Mainnet but executing transactions offchain with its own mechanism for block validation. Plasma chains are sometimes referred to as "child" chains, essentially smaller copies of the Ethereum Mainnet. Plasma chains use [fraud proofs](/glossary/#fraud-proof) (like [optimistic rollups](/developers/docs/scaling/optimistic-rollups/)) to arbitrate disputes.
Merkle trees enable the creation of an endless stack of these chains that can work to offload bandwidth from parent chains (including Ethereum Mainnet). However, while these chains derive some security from Ethereum (via fraud proofs), their security and efficiency are affected by several design limitations.
diff --git a/public/content/developers/docs/scaling/sidechains/index.md b/public/content/developers/docs/scaling/sidechains/index.md
index a13aa17da04..7d08b13b352 100644
--- a/public/content/developers/docs/scaling/sidechains/index.md
+++ b/public/content/developers/docs/scaling/sidechains/index.md
@@ -5,7 +5,7 @@ lang: en
sidebarDepth: 3
---
-A sidechain is a separate blockchain that runs independent of Ethereum and is connected to Ethereum Mainnet by a two-way bridge. Sidechains can have separate block parameters and [consensus algorithms](/developers/docs/consensus-mechanisms/), which are often designed for efficient processing of transactions. Using a sidechain involves trade-offs, though, as they do not inherit Ethereum's security properties. Unlike [layer 2 scaling solutions](/layer-2/), sidechains do not post state changes and transaction data back to Ethereum Mainnet.
+A sidechain is a separate blockchain that runs independent of [Ethereum](/) and is connected to Ethereum Mainnet by a two-way bridge. Sidechains can have separate block parameters and [consensus algorithms](/developers/docs/consensus-mechanisms/), which are often designed for efficient processing of transactions. Using a sidechain involves trade-offs, though, as they do not inherit Ethereum's security properties. Unlike [layer 2 scaling solutions](/layer-2/), sidechains do not post state changes and transaction data back to Ethereum Mainnet.
Sidechains also sacrifice some measure of decentralization or security to achieve high throughput ([scalability trilemma](https://vitalik.eth.limo/general/2021/05/23/scaling.html)). Ethereum is, however, committed to scaling without compromising on decentralization and security.
diff --git a/public/content/developers/docs/scaling/state-channels/index.md b/public/content/developers/docs/scaling/state-channels/index.md
index 7050dd42339..5154fa97448 100644
--- a/public/content/developers/docs/scaling/state-channels/index.md
+++ b/public/content/developers/docs/scaling/state-channels/index.md
@@ -5,7 +5,7 @@ lang: en
sidebarDepth: 3
---
-State channels allow participants to securely transact offchain while keeping interaction with Ethereum Mainnet at a minimum. Channel peers can conduct an arbitrary number of offchain transactions while only submitting two onchain transactions to open and close the channel. This allows for extremely high transaction throughput and results in lower costs for users.
+State channels allow participants to securely transact offchain while keeping interaction with [Ethereum](/) Mainnet at a minimum. Channel peers can conduct an arbitrary number of offchain transactions while only submitting two onchain transactions to open and close the channel. This allows for extremely high transaction throughput and results in lower costs for users.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/scaling/validium/index.md b/public/content/developers/docs/scaling/validium/index.md
index 81033327411..0610bf788c5 100644
--- a/public/content/developers/docs/scaling/validium/index.md
+++ b/public/content/developers/docs/scaling/validium/index.md
@@ -5,7 +5,7 @@ lang: en
sidebarDepth: 3
---
-Validium is a [scaling solution](/developers/docs/scaling/) that enforces integrity of transactions using validity proofs like [ZK-rollups](/developers/docs/scaling/zk-rollups/), but doesn’t store transaction data on the Ethereum Mainnet. While offchain data availability introduces trade-offs, it can lead to massive improvements in scalability (validiums can process [~9,000 transactions, or more, per second](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263)).
+Validium is a [scaling solution](/developers/docs/scaling/) that enforces integrity of transactions using validity proofs like [ZK-rollups](/developers/docs/scaling/zk-rollups/), but doesn’t store transaction data on the [Ethereum](/) Mainnet. While offchain data availability introduces trade-offs, it can lead to massive improvements in scalability (validiums can process [~9,000 transactions, or more, per second](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263)).
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/scaling/zk-rollups/index.md b/public/content/developers/docs/scaling/zk-rollups/index.md
index 4df80ea5bc2..2234531b29a 100644
--- a/public/content/developers/docs/scaling/zk-rollups/index.md
+++ b/public/content/developers/docs/scaling/zk-rollups/index.md
@@ -4,7 +4,7 @@ description: An introduction to zero-knowledge rollups—a scaling solution used
lang: en
---
-Zero-knowledge rollups (ZK-rollups) are layer 2 [scaling solutions](/developers/docs/scaling/) that increase throughput on Ethereum Mainnet by moving computation and state-storage offchain. ZK-rollups can process thousands of transactions in a batch and then only post some minimal summary data to Mainnet. This summary data defines the changes that should be made to the Ethereum state and some cryptographic proof that those changes are correct.
+Zero-knowledge rollups (ZK-rollups) are layer 2 [scaling solutions](/developers/docs/scaling/) that increase throughput on [Ethereum](/) Mainnet by moving computation and state-storage offchain. ZK-rollups can process thousands of transactions in a batch and then only post some minimal summary data to Mainnet. This summary data defines the changes that should be made to the Ethereum state and some cryptographic proof that those changes are correct.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/smart-contracts/anatomy/index.md b/public/content/developers/docs/smart-contracts/anatomy/index.md
index a697559c2d0..0d9b62a2670 100644
--- a/public/content/developers/docs/smart-contracts/anatomy/index.md
+++ b/public/content/developers/docs/smart-contracts/anatomy/index.md
@@ -31,7 +31,7 @@ contract SimpleStorage {
storedData: int128
```
-If you've already programmed object-oriented languages, you'll likely be familiar with most types. However, `address` should be new to you if you're new to Ethereum development.
+If you've already programmed object-oriented languages, you'll likely be familiar with most types. However, `address` should be new to you if you're new to [Ethereum](/) development.
An `address` type can hold an Ethereum address which equates to 20 bytes or 160 bits. It returns in hexadecimal notation with a leading 0x.
diff --git a/public/content/developers/docs/smart-contracts/formal-verification/index.md b/public/content/developers/docs/smart-contracts/formal-verification/index.md
index 03102cccc57..4d7ca26ee51 100644
--- a/public/content/developers/docs/smart-contracts/formal-verification/index.md
+++ b/public/content/developers/docs/smart-contracts/formal-verification/index.md
@@ -163,7 +163,7 @@ An execution trace that results in an integer overflow would need to satisfy the
Formal verification is used to assess the correctness of safety-critical systems whose failure can have devastating consequences, such as death, injury, or financial ruin. Smart contracts are high-value applications controlling enormous amounts of value, and simple errors in design can lead to [irrecoverable losses for users](https://www.freecodecamp.org/news/a-hacker-stole-31m-of-ether-how-it-happened-and-what-it-means-for-ethereum-9e5dc29e33ce/amp/). Formally verifying a contract before deployment, however, can increase guarantees that it will perform as expected once running on the blockchain.
-Reliability is a highly desired quality in any smart contract, especially because code deployed in the Ethereum Virtual Machine (EVM) is typically immutable. With post-launch upgrades not readily accessible, the need to guarantee reliability of contracts makes formal verification necessary. Formal verification is able to detect tricky issues, such as integer underflows and overflow, re-entrancy, and poor gas optimizations, which may slip past auditors and testers.
+Reliability is a highly desired quality in any smart contract, especially because code deployed in the [Ethereum](/) Virtual Machine (EVM) is typically immutable. With post-launch upgrades not readily accessible, the need to guarantee reliability of contracts makes formal verification necessary. Formal verification is able to detect tricky issues, such as integer underflows and overflow, re-entrancy, and poor gas optimizations, which may slip past auditors and testers.
#### Prove functional correctness {#prove-functional-correctness}
diff --git a/public/content/developers/docs/smart-contracts/languages/index.md b/public/content/developers/docs/smart-contracts/languages/index.md
index 21c3f3b7e94..755913a8cb0 100644
--- a/public/content/developers/docs/smart-contracts/languages/index.md
+++ b/public/content/developers/docs/smart-contracts/languages/index.md
@@ -4,7 +4,7 @@ description: An overview and comparison of the two main smart contract languages
lang: en
---
-A great aspect about Ethereum is that smart contracts can be programmed using relatively developer-friendly languages. If you're experienced with Python or any [curly-bracket language](https://wikipedia.org/wiki/List_of_programming_languages_by_type#Curly-bracket_languages), you can find a language with familiar syntax.
+A great aspect about [Ethereum](/) is that smart contracts can be programmed using relatively developer-friendly languages. If you're experienced with Python or any [curly-bracket language](https://wikipedia.org/wiki/List_of_programming_languages_by_type#Curly-bracket_languages), you can find a language with familiar syntax.
The two most active and maintained languages are:
diff --git a/public/content/developers/docs/smart-contracts/security/index.md b/public/content/developers/docs/smart-contracts/security/index.md
index 50e2f97c0b1..76197beff1d 100644
--- a/public/content/developers/docs/smart-contracts/security/index.md
+++ b/public/content/developers/docs/smart-contracts/security/index.md
@@ -6,7 +6,7 @@ lang: en
Smart contracts are extremely flexible, and capable of controlling large amounts of value and data, while running immutable logic based on code deployed on the blockchain. This has created a vibrant ecosystem of trustless and decentralized applications that provide many advantages over legacy systems. They also represent opportunities for attackers looking to profit by exploiting vulnerabilities in smart contracts.
-Public blockchains, like Ethereum, further complicate the issue of securing smart contracts. Deployed contract code _usually_ cannot be changed to patch security flaws, while assets stolen from smart contracts are extremely difficult to track and mostly irrecoverable due to immutability.
+Public blockchains, like [Ethereum](/), further complicate the issue of securing smart contracts. Deployed contract code _usually_ cannot be changed to patch security flaws, while assets stolen from smart contracts are extremely difficult to track and mostly irrecoverable due to immutability.
Although figures vary, it is estimated that the total amount of value stolen or lost due to security defects in smart contracts is easily over $1 billion. This includes high-profile incidents, such as the [DAO hack](https://hackingdistributed.com/2016/06/18/analysis-of-the-dao-exploit/) (3.6M ETH stolen, worth over $1B in today’s prices), [Parity multi-sig wallet hack](https://www.coindesk.com/markets/2017/07/19/30-million-ether-reported-stolen-due-to-parity-wallet-breach) ($30M lost to hackers), and the [Parity frozen wallet issue](https://www.theguardian.com/technology/2017/nov/08/cryptocurrency-300m-dollars-stolen-bug-ether) (over $300M in ETH locked forever).
diff --git a/public/content/developers/docs/standards/tokens/erc-721/index.md b/public/content/developers/docs/standards/tokens/erc-721/index.md
index d618534b2b6..85b5735d6f9 100644
--- a/public/content/developers/docs/standards/tokens/erc-721/index.md
+++ b/public/content/developers/docs/standards/tokens/erc-721/index.md
@@ -31,7 +31,7 @@ uses the `tokenId` as input and outputs an image of something cool, like zombies
## Body {#body}
-The ERC-721 (Ethereum Request for Comments 721), proposed by William Entriken, Dieter Shirley, Jacob Evans,
+The ERC-721 ([Ethereum](/) Request for Comments 721), proposed by William Entriken, Dieter Shirley, Jacob Evans,
Nastassia Sachs in January 2018, is a Non-Fungible Token Standard that implements an API for tokens within Smart Contracts.
It provides functionalities like to transfer tokens from one account to another, to get the current token balance of an
diff --git a/public/content/developers/docs/standards/tokens/index.md b/public/content/developers/docs/standards/tokens/index.md
index f2711c739be..9f7ebbab87a 100644
--- a/public/content/developers/docs/standards/tokens/index.md
+++ b/public/content/developers/docs/standards/tokens/index.md
@@ -7,7 +7,7 @@ incomplete: true
## Introduction {#introduction}
-Many Ethereum development standards focus on token interfaces. These standards help ensure smart contracts remain composable, so when a new project issues a token, it stays compatible with existing decentralized exchanges and applications.
+Many [Ethereum](/) development standards focus on token interfaces. These standards help ensure smart contracts remain composable, so when a new project issues a token, it stays compatible with existing decentralized exchanges and applications.
Token standards define how tokens behave and interact across the Ethereum ecosystem. They make it easier for developers to build without reinventing the wheel, ensuring that tokens work seamlessly with wallets, exchanges, and DeFi platforms. Whether in gaming, governance, or other use cases, these standards provide consistency and make Ethereum more interconnected.
diff --git a/public/content/developers/docs/transactions/index.md b/public/content/developers/docs/transactions/index.md
index c5175ec1529..e0c09dfa4fc 100644
--- a/public/content/developers/docs/transactions/index.md
+++ b/public/content/developers/docs/transactions/index.md
@@ -4,7 +4,7 @@ description: An overview of Ethereum transactions – how they work, their data
lang: en
---
-Transactions are cryptographically signed instructions from accounts. An account will initiate a transaction to update the state of the Ethereum network. The simplest transaction is transferring ETH from one account to another.
+Transactions are cryptographically signed instructions from accounts. An account will initiate a transaction to update the state of the [Ethereum](/) network. The simplest transaction is transferring ETH from one account to another.
## Prerequisites {#prerequisites}
diff --git a/public/content/developers/docs/web2-vs-web3/index.md b/public/content/developers/docs/web2-vs-web3/index.md
index e7181d71a96..0f0d96b79d2 100644
--- a/public/content/developers/docs/web2-vs-web3/index.md
+++ b/public/content/developers/docs/web2-vs-web3/index.md
@@ -4,7 +4,7 @@ description: Compare centralized Web2 services with decentralized Web3 applicati
lang: en
---
-Web2 refers to the version of the internet most of us know today. An internet dominated by companies that provide services in exchange for your personal data. Web3, in the context of Ethereum, refers to decentralized apps that run on the blockchain. These are apps that allow anyone to participate without monetising their personal data.
+Web2 refers to the version of the internet most of us know today. An internet dominated by companies that provide services in exchange for your personal data. Web3, in the context of [Ethereum](/), refers to decentralized apps that run on the blockchain. These are apps that allow anyone to participate without monetising their personal data.
Looking for a more beginner-friendly resource? See our [introduction to web3](/web3/).
diff --git a/public/content/developers/tutorials/how-to-mint-an-nft/index.md b/public/content/developers/tutorials/how-to-mint-an-nft/index.md
index 5f1bcbf37c1..2cde7e5ea50 100644
--- a/public/content/developers/tutorials/how-to-mint-an-nft/index.md
+++ b/public/content/developers/tutorials/how-to-mint-an-nft/index.md
@@ -20,7 +20,7 @@ Let’s get started!
## Step 1: Install Web3 {#install-web3}
-If you followed the first tutorial on creating your NFT smart contract, you already have experience using Ethers.js. Web3 is similar to Ethers, as it is a library used to make creating requests to the Ethereum blockchain easier. In this tutorial we’ll be using [Alchemy Web3](https://docs.alchemyapi.io/alchemy/documentation/alchemy-web3), which is an enhanced Web3 library that offers automatic retries and robust WebSocket support.
+If you followed the first tutorial on creating your NFT smart contract, you already have experience using Ethers.js. Web3 is similar to Ethers, as it is a library used to make creating requests to the [Ethereum](/) blockchain easier. In this tutorial we’ll be using [Alchemy Web3](https://docs.alchemyapi.io/alchemy/documentation/alchemy-web3), which is an enhanced Web3 library that offers automatic retries and robust WebSocket support.
In your project home directory run:
diff --git a/public/content/eips/index.md b/public/content/eips/index.md
index 6fdd3ebe67b..fe0de245834 100644
--- a/public/content/eips/index.md
+++ b/public/content/eips/index.md
@@ -8,7 +8,7 @@ lang: en
## What are EIPs? {#what-are-eips}
-[Ethereum Improvement Proposals (EIPs)](https://eips.ethereum.org/) are standards specifying potential new features or processes for Ethereum. EIPs contain technical specifications for the proposed changes and act as the “source of truth” for the community. Network upgrades and application standards for Ethereum are discussed and developed through the EIP process.
+[Ethereum Improvement Proposals (EIPs)](https://eips.ethereum.org/) are standards specifying potential new features or processes for Ethereum. EIPs contain technical specifications for the proposed changes and act as the “source of truth” for the community. Network upgrades and application standards for [Ethereum](/) are discussed and developed through the EIP process.
Anyone within the Ethereum community has the ability to create an EIP. Guidelines for writing EIPs are included in [EIP-1](https://eips.ethereum.org/EIPS/eip-1). An EIP should primarily provide a concise technical specification with a small amount of motivation. The EIP author is responsible for reaching consensus within the community and documenting alternative opinions. Given the high technical barrier for submitting a well-formed EIP, historically, most EIP authors are typically application or protocol developers.
diff --git a/public/content/energy-consumption/index.md b/public/content/energy-consumption/index.md
index 784bb951f64..ed85755ef97 100644
--- a/public/content/energy-consumption/index.md
+++ b/public/content/energy-consumption/index.md
@@ -6,7 +6,7 @@ lang: en
# Ethereum's energy expenditure {#proof-of-stake-energy}
-Ethereum is a green blockchain. Ethereum's [proof-of-stake](/developers/docs/consensus-mechanisms/pos) consensus mechanism uses ETH instead of [energy to secure the network](/developers/docs/consensus-mechanisms/pow). Ethereum's energy consumption is approximately [~0.0026 TWh/yr](https://carbon-ratings.com/eth-report-2022) across the entire global network.
+[Ethereum](/) is a green blockchain. Ethereum's [proof-of-stake](/developers/docs/consensus-mechanisms/pos) consensus mechanism uses ETH instead of [energy to secure the network](/developers/docs/consensus-mechanisms/pow). Ethereum's energy consumption is approximately [~0.0026 TWh/yr](https://carbon-ratings.com/eth-report-2022) across the entire global network.
The energy consumption estimate for Ethereum comes from a [CCRI (Crypto Carbon Ratings Institute)](https://carbon-ratings.com) study. They generated bottom-up estimates of the electricity consumption and carbon footprint of the Ethereum network ([see the report](https://carbon-ratings.com/eth-report-2022)). They measured the electricity consumption of different nodes with various hardware and client software configurations. The estimated **2,601 MWh** (0.0026 TWh) for the network’s annual electricity consumption corresponds to yearly carbon emissions of **870 tonnes CO2e** applying regional-specific carbon intensity factors. This value changes as nodes enter and leave the network - you can keep track using a rolling 7-day average estimate by the [Cambridge Blockchain network Sustainability Index](https://ccaf.io/cbnsi/ethereum) (note that they use a slightly different method for their estimates - details available on their site).
diff --git a/public/content/ethereum-forks/index.md b/public/content/ethereum-forks/index.md
index 3dbac7db7dd..178d5fbf234 100644
--- a/public/content/ethereum-forks/index.md
+++ b/public/content/ethereum-forks/index.md
@@ -7,7 +7,7 @@ sidebarDepth: 1
# Timeline of all Ethereum forks (2014 to present) {#the-history-of-ethereum}
-A timeline of all the major milestones, forks, and updates to the Ethereum blockchain.
+A timeline of all the major milestones, forks, and updates to the [Ethereum](/) blockchain.
diff --git a/public/content/roadmap/account-abstraction/index.md b/public/content/roadmap/account-abstraction/index.md
index 86377629931..d200261d4e2 100644
--- a/public/content/roadmap/account-abstraction/index.md
+++ b/public/content/roadmap/account-abstraction/index.md
@@ -10,7 +10,7 @@ summaryPoints:
# Account abstraction {#account-abstraction}
-Most existing users interact with Ethereum using **[externally owned accounts (EOAs)](/glossary/#eoa)**. This limits how users can interact with Ethereum. For example, it makes it difficult to do batches of transactions and requires users to always keep an ETH balance to pay transaction fees.
+Most existing users interact with [Ethereum](/) using **[externally owned accounts (EOAs)](/glossary/#eoa)**. This limits how users can interact with Ethereum. For example, it makes it difficult to do batches of transactions and requires users to always keep an ETH balance to pay transaction fees.
Account abstraction is a way to solve these problems by allowing users to flexibly program more security and better user experiences into their accounts. This can happen by [upgrading EOAs](https://eips.ethereum.org/EIPS/eip-7702) (EIP-7702) so they can be controlled by smart contracts. There is also another path involving adding a [second, separate transaction system](https://eips.ethereum.org/EIPS/eip-4337) (EIP-4337) to run in parallel to the existing protocol. Regardless of the route, the outcome is access to Ethereum via smart contract wallets, either natively supported as part of the existing protocol or via an add-on transaction network.
diff --git a/public/content/roadmap/fusaka/index.md b/public/content/roadmap/fusaka/index.md
index 3f4738dea07..4ccc4a0ef3d 100644
--- a/public/content/roadmap/fusaka/index.md
+++ b/public/content/roadmap/fusaka/index.md
@@ -8,7 +8,7 @@ lang: en
**Ethereum's highly anticipated Fusaka upgrade went live on December 3, 2025**
-The Fusaka network upgrade follows [Pectra](/roadmap/pectra/) and brings more new features and improves the experience for every Ethereum user and developer. The name consists of the execution layer upgrade Osaka and the consensus layer version named after the Fulu star. Both parts of Ethereum receive an upgrade that pushes Ethereum scaling, security and user experience to the future.
+The Fusaka network upgrade follows [Pectra](/roadmap/pectra/) and brings more new features and improves the experience for every [Ethereum](/) user and developer. The name consists of the execution layer upgrade Osaka and the consensus layer version named after the Fulu star. Both parts of Ethereum receive an upgrade that pushes Ethereum scaling, security and user experience to the future.
diff --git a/public/content/roadmap/fusaka/peerdas/index.md b/public/content/roadmap/fusaka/peerdas/index.md
index abedd39d07c..9a3f52b9312 100644
--- a/public/content/roadmap/fusaka/peerdas/index.md
+++ b/public/content/roadmap/fusaka/peerdas/index.md
@@ -6,7 +6,7 @@ lang: en
# PeerDAS {#peer-das}
-The Ethereum protocol is undergoing its most significant scaling upgrade since the [introduction of blob transactions with EIP-4844](/roadmap/danksharding/). As part of the [Fusaka upgrade](/roadmap/fusaka/), PeerDAS introduces a new way of handling blob data, delivering roughly an order-of-magnitude increase in **[data availability (DA)](/developers/docs/data-availability/)** capacity for L2s.
+The [Ethereum](/) protocol is undergoing its most significant scaling upgrade since the [introduction of blob transactions with EIP-4844](/roadmap/danksharding/). As part of the [Fusaka upgrade](/roadmap/fusaka/), PeerDAS introduces a new way of handling blob data, delivering roughly an order-of-magnitude increase in **[data availability (DA)](/developers/docs/data-availability/)** capacity for L2s.
[More on blob scaling roadmap](https://blog.ethereum.org/2025/08/22/protocol-update-002)
diff --git a/public/content/roadmap/merge/index.md b/public/content/roadmap/merge/index.md
index 45137b669b0..49d78ced82f 100644
--- a/public/content/roadmap/merge/index.md
+++ b/public/content/roadmap/merge/index.md
@@ -12,7 +12,7 @@ summaryPoint4: The Merge reduced Ethereum's energy consumption by ~99.95%.
---
- The Merge was executed on September 15, 2022. This completed [Ethereum's](/) transition to proof-of-stake consensus, officially deprecating proof-of-work and reducing energy consumption by ~99.95%.
+ The Merge was executed on September 15, 2022. This completed Ethereum's transition to proof-of-stake consensus, officially deprecating proof-of-work and reducing energy consumption by ~99.95%.
## What was The Merge? {#what-is-the-merge}
diff --git a/public/content/roadmap/merge/issuance/index.md b/public/content/roadmap/merge/issuance/index.md
index e756b03e479..65fea16510f 100644
--- a/public/content/roadmap/merge/issuance/index.md
+++ b/public/content/roadmap/merge/issuance/index.md
@@ -6,7 +6,7 @@ lang: en
# How The Merge impacted ETH supply {#how-the-merge-impacts-ETH-supply}
-The Merge represented the Ethereum network's transition from proof-of-work to proof-of-stake which occurred in September 2022. The way ETH was issued underwent changes at time of that transition. Previously, new ETH was issued from two sources: the execution layer (i.e., Mainnet) and the consensus layer (i.e., Beacon Chain). Since The Merge, issuance on the execution layer is now zero. Let's break this down.
+The Merge represented the [Ethereum](/) network's transition from proof-of-work to proof-of-stake which occurred in September 2022. The way ETH was issued underwent changes at time of that transition. Previously, new ETH was issued from two sources: the execution layer (i.e., Mainnet) and the consensus layer (i.e., Beacon Chain). Since The Merge, issuance on the execution layer is now zero. Let's break this down.
## Components of ETH issuance {#components-of-eth-issuance}
diff --git a/public/content/roadmap/pbs/index.md b/public/content/roadmap/pbs/index.md
index b4ff9925917..a91ff134839 100644
--- a/public/content/roadmap/pbs/index.md
+++ b/public/content/roadmap/pbs/index.md
@@ -6,7 +6,7 @@ lang: en
# Proposer-builder separation {#proposer-builder-separation}
-Present-day Ethereum validators create _and_ broadcast blocks. They bundle together transactions that they have heard about through the gossip network and package them into a block that is sent out to peers on the Ethereum network. **Proposer-builder separation (PBS)** splits these tasks across multiple validators. Block builders become responsible for creating blocks and offering them to the block proposer in each slot. The block proposer cannot see the contents of the block, they simply choose the most profitable one, paying a fee to the block builder before sending the block to its peers.
+Present-day [Ethereum](/) validators create _and_ broadcast blocks. They bundle together transactions that they have heard about through the gossip network and package them into a block that is sent out to peers on the Ethereum network. **Proposer-builder separation (PBS)** splits these tasks across multiple validators. Block builders become responsible for creating blocks and offering them to the block proposer in each slot. The block proposer cannot see the contents of the block, they simply choose the most profitable one, paying a fee to the block builder before sending the block to its peers.
This is an important upgrade for several reasons. First, it creates opportunities to prevent transaction censorship at the protocol level. Second, it prevents hobbyist validators from being out-competed by institutional players that can better optimize the profitability of their block building. Third, it helps with scaling Ethereum by enabling the Danksharding upgrades.
diff --git a/public/content/roadmap/pectra/index.md b/public/content/roadmap/pectra/index.md
index 9253ce1753d..76f32dfacbf 100644
--- a/public/content/roadmap/pectra/index.md
+++ b/public/content/roadmap/pectra/index.md
@@ -6,7 +6,7 @@ lang: en
# Pectra {#pectra}
-The Pectra network upgrade followed [Dencun](/roadmap/dencun/) and brought changes to both the execution and consensus layer of Ethereum. The shortened name Pectra is a combination of Prague and Electra, which are the respective names for the execution and consensus layer specification changes. Together, these changes bring a number of improvements to Ethereum users, developers and validators.
+The Pectra network upgrade followed [Dencun](/roadmap/dencun/) and brought changes to both the execution and consensus layer of Ethereum. The shortened name Pectra is a combination of Prague and Electra, which are the respective names for the execution and consensus layer specification changes. Together, these changes bring a number of improvements to [Ethereum](/) users, developers and validators.
This upgrade was successfully activated on Ethereum mainnet at epoch `364032`, on **07-May-2025 at 10:05 (UTC)**.
diff --git a/public/content/roadmap/single-slot-finality/index.md b/public/content/roadmap/single-slot-finality/index.md
index 0f24eab6d6a..c9f0c960123 100644
--- a/public/content/roadmap/single-slot-finality/index.md
+++ b/public/content/roadmap/single-slot-finality/index.md
@@ -6,7 +6,7 @@ lang: en
# Single slot finality {#single-slot-finality}
-It takes about 15 minutes for an Ethereum block to finalize. However, we can make Ethereum's consensus mechanism validate blocks more efficiently and decrease time-to-finality dramatically. Instead of waiting for fifteen minutes, blocks could get proposed and finalized in the same slot. This concept is known as **single slot finality (SSF)**.
+It takes about 15 minutes for an [Ethereum](/) block to finalize. However, we can make Ethereum's consensus mechanism validate blocks more efficiently and decrease time-to-finality dramatically. Instead of waiting for fifteen minutes, blocks could get proposed and finalized in the same slot. This concept is known as **single slot finality (SSF)**.
## What is finality? {#what-is-finality}
diff --git a/public/content/roadmap/statelessness/index.md b/public/content/roadmap/statelessness/index.md
index aad8c9e7209..9ad4f0cc773 100644
--- a/public/content/roadmap/statelessness/index.md
+++ b/public/content/roadmap/statelessness/index.md
@@ -6,7 +6,7 @@ lang: en
# Statelessness, state expiry and history expiry {#statelessness}
-The ability to run Ethereum nodes on modest hardware is critical for true decentralization. This is because running a node gives users the ability to verify information by performing cryptographic checks independently rather than trusting a third party to feed them data. Running a node allows users to submit transactions directly to the Ethereum peer-to-peer network rather than having to trust an intermediary. Decentralization is not possible if these benefits are only available to users with expensive hardware. Instead, nodes should be able to run with extremely modest processing and memory requirements so that they can run on mobile phones, micro-computers or unnoticeably on a home computer.
+The ability to run [Ethereum](/) nodes on modest hardware is critical for true decentralization. This is because running a node gives users the ability to verify information by performing cryptographic checks independently rather than trusting a third party to feed them data. Running a node allows users to submit transactions directly to the Ethereum peer-to-peer network rather than having to trust an intermediary. Decentralization is not possible if these benefits are only available to users with expensive hardware. Instead, nodes should be able to run with extremely modest processing and memory requirements so that they can run on mobile phones, micro-computers or unnoticeably on a home computer.
Today, high disk space requirements is the main barrier preventing universal access to nodes. This is primarily due to the need to store large chunks of Ethereum's state data. This state data contains critical information required to correctly process new blocks and transactions. At the time of writing, a fast 2TB SSD is recommended for running a full Ethereum node. For a node that does not prune any older data, the storage requirement grows at around 14GB/week, and archive nodes that store all data since genesis are approaching 12 TB (at time of writing, in Feb 2023).
diff --git a/public/content/roadmap/verkle-trees/index.md b/public/content/roadmap/verkle-trees/index.md
index 68b95a333d1..e716f444830 100644
--- a/public/content/roadmap/verkle-trees/index.md
+++ b/public/content/roadmap/verkle-trees/index.md
@@ -9,7 +9,7 @@ summaryPoints:
# Verkle trees {#verkle-trees}
-Verkle trees (a portmanteau of "Vector commitment" and "Merkle Trees") are a data structure that can be used to upgrade Ethereum nodes so that they can stop storing large amounts of state data without losing the ability to validate blocks.
+Verkle trees (a portmanteau of "Vector commitment" and "Merkle Trees") are a data structure that can be used to upgrade [Ethereum](/) nodes so that they can stop storing large amounts of state data without losing the ability to validate blocks.
## Statelessness {#statelessness}
diff --git a/public/content/security/index.md b/public/content/security/index.md
index 7269f69ea3b..da60fb99324 100644
--- a/public/content/security/index.md
+++ b/public/content/security/index.md
@@ -16,7 +16,7 @@ Rising interest in cryptocurrency brings with it growing risk from scammers and
### Level up your knowledge {#level-up-your-knowledge}
-Misunderstandings about how crypto works can lead to costly mistakes. For example, if someone pretends to be a customer service agent who can return lost ETH in exchange for your private keys, they are preying on people not understanding that Ethereum is a decentralized network lacking this kind of functionality. Educating yourself on how Ethereum works is a worthwhile investment.
+Misunderstandings about how crypto works can lead to costly mistakes. For example, if someone pretends to be a customer service agent who can return lost ETH in exchange for your private keys, they are preying on people not understanding that [Ethereum](/) is a decentralized network lacking this kind of functionality. Educating yourself on how Ethereum works is a worthwhile investment.
What is Ethereum?
diff --git a/public/content/social-networks/index.md b/public/content/social-networks/index.md
index 63057618efe..b462bea54c3 100644
--- a/public/content/social-networks/index.md
+++ b/public/content/social-networks/index.md
@@ -11,7 +11,7 @@ summaryPoint2: Decentralized social media networks protect user privacy and enha
summaryPoint3: Tokens and NFTs create new ways to monetize content.
---
-Social networks play a massive role in our daily communications and interactions. However, centralized control of these platforms has created many problems: data breaches, server outages, de-platforming, censorship, and privacy violations are some of the trade-offs social media often make. To combat these issues, developers are building social networks on Ethereum. Decentralized social networks can fix many of the problems of traditional social networking platforms and improve users' overall experience.
+Social networks play a massive role in our daily communications and interactions. However, centralized control of these platforms has created many problems: data breaches, server outages, de-platforming, censorship, and privacy violations are some of the trade-offs social media often make. To combat these issues, developers are building social networks on [Ethereum](). Decentralized social networks can fix many of the problems of traditional social networking platforms and improve users' overall experience.
## What are decentralized social networks? {#what-are-decentralized-social-networks}
diff --git a/public/content/staking/dvt/index.md b/public/content/staking/dvt/index.md
index 36021a01669..1f8b4f0e399 100644
--- a/public/content/staking/dvt/index.md
+++ b/public/content/staking/dvt/index.md
@@ -18,7 +18,7 @@ It does this by **splitting the private key** used to secure a validator **acros
Validators generate two public-private key pairs: validator keys for participating in consensus and withdrawal keys for accessing funds. While validators can secure withdrawal keys in cold storage, validator private keys must be online 24/7. If a validator private key is compromised, an attacker can control the validator, potentially leading to slashing or the loss of the staker's ETH. DVT can help mitigate this risk. Here's how:
-By using DVT, stakers can participate in staking while keeping the validator private key in cold storage. This is achieved by encrypting the original, full validator key and then splitting it into key shares. The key shares live online and are distributed to multiple nodes which enable the distributed operation of the validator. This is possible because Ethereum validators use BLS signatures that are additive, meaning the full key can be reconstructed by summing their component parts. This allows the staker to keep the full, original 'master' validator key securely offline.
+By using DVT, stakers can participate in staking while keeping the validator private key in cold storage. This is achieved by encrypting the original, full validator key and then splitting it into key shares. The key shares live online and are distributed to multiple nodes which enable the distributed operation of the validator. This is possible because [Ethereum](/) validators use BLS signatures that are additive, meaning the full key can be reconstructed by summing their component parts. This allows the staker to keep the full, original 'master' validator key securely offline.
### No single points of failure {#no-single-point-of-failure}
diff --git a/public/content/staking/pools/index.md b/public/content/staking/pools/index.md
index 1a7c2492eb1..7d4a985ea29 100644
--- a/public/content/staking/pools/index.md
+++ b/public/content/staking/pools/index.md
@@ -33,7 +33,7 @@ In addition to the benefits we outlined in our [intro to staking](/staking/), st
## What to consider {#what-to-consider}
-Pooled or delegated staking is not natively supported by the Ethereum protocol, but given the demand for users to stake less than 32 ETH a growing number of solutions have been built out to serve this demand.
+Pooled or delegated staking is not natively supported by the [Ethereum](/) protocol, but given the demand for users to stake less than 32 ETH a growing number of solutions have been built out to serve this demand.
Each pool and the tools or smart contracts they use have been built out by different teams, and each comes with benefits and risks. Pools enable users to swap their ETH for a token representing staked ETH. The token is useful because it allows users to swap any amount of ETH to an equivalent amount of a yield-bearing token that generates a return from the staking rewards applied to the underlying staked ETH (and vice versa) on decentralized exchanges even though the actual ETH stays staked on the consensus layer. This means swaps back and forth from a yield-bearing staked-ETH product and "raw ETH" is quick, easy and not only available in multiples of 32 ETH.
diff --git a/public/content/staking/saas/index.md b/public/content/staking/saas/index.md
index 6c2f41abc00..879250cd699 100644
--- a/public/content/staking/saas/index.md
+++ b/public/content/staking/saas/index.md
@@ -19,7 +19,7 @@ Staking as a service (“SaaS") represents a category of staking services where
## Why stake with a service? {#why-stake-with-a-service}
-The Ethereum protocol does not natively support delegation of stake, so these services have been built out to fill this demand. If you have 32 ETH to stake, but don't feel comfortable dealing with hardware, SaaS services allow you to delegate the hard part while you earn native block rewards.
+The [Ethereum](/) protocol does not natively support delegation of stake, so these services have been built out to fill this demand. If you have 32 ETH to stake, but don't feel comfortable dealing with hardware, SaaS services allow you to delegate the hard part while you earn native block rewards.
diff --git a/public/content/staking/solo/index.md b/public/content/staking/solo/index.md
index dc5e13df513..2168937b569 100644
--- a/public/content/staking/solo/index.md
+++ b/public/content/staking/solo/index.md
@@ -17,7 +17,7 @@ summaryPoints:
Home staking is the act of [running an Ethereum node](/run-a-node/) connected to the internet and depositing 32 ETH to activate a [validator](#faq), giving you the ability to participate directly in network consensus.
-**Home staking increases the decentralization of the Ethereum network**, making Ethereum more censorship-resistant and robust against attacks. Other staking methods may not help the network in the same ways. Home staking is the best staking option for securing Ethereum.
+**Home staking increases the decentralization of the Ethereum network**, making [Ethereum](/) more censorship-resistant and robust against attacks. Other staking methods may not help the network in the same ways. Home staking is the best staking option for securing Ethereum.
An Ethereum node consists of both an execution layer (EL) client, as well as a consensus layer (CL) client. These clients are software that work together, along with a valid set of signing keys, to verify transactions and blocks, attest to the correct head of the chain, aggregate attestations, and propose blocks.
diff --git a/public/content/staking/withdrawals/index.md b/public/content/staking/withdrawals/index.md
index fcae6e6284a..943f3179c8c 100644
--- a/public/content/staking/withdrawals/index.md
+++ b/public/content/staking/withdrawals/index.md
@@ -25,7 +25,7 @@ Any balance above 32 ETH earned through rewards does not actually contribute to
### How did we get here? {#how-did-we-get-here}
-Over the past few years Ethereum has undergone several network upgrades transitioning to a network secured by ETH itself, instead of energy-intensive mining as it once was. Participating in consensus on Ethereum is now known as "staking", as participants have voluntarily locked up ETH, placing it "at stake" for the ability to participate in the network. Users who follow the rules will be rewarded, while attempts to cheat can be penalized.
+Over the past few years [Ethereum](/) has undergone several network upgrades transitioning to a network secured by ETH itself, instead of energy-intensive mining as it once was. Participating in consensus on Ethereum is now known as "staking", as participants have voluntarily locked up ETH, placing it "at stake" for the ability to participate in the network. Users who follow the rules will be rewarded, while attempts to cheat can be penalized.
Since the launch of the staking deposit contract in November 2020, some brave Ethereum pioneers have voluntarily locked funds up to activate "validators", special accounts that have the right to formally attest to and propose blocks, following network rules.
diff --git a/public/content/web3/index.md b/public/content/web3/index.md
index 2b6535236bc..a001274da29 100644
--- a/public/content/web3/index.md
+++ b/public/content/web3/index.md
@@ -39,7 +39,7 @@ The Web 2.0 period began in 2004 with the emergence of social media platforms. I
## Web 3.0: Read-Write-Own {#web3}
-The premise of 'Web 3.0' was coined by [Ethereum](/what-is-ethereum/) co-founder Gavin Wood shortly after Ethereum launched in 2014. Gavin put into words a solution for a problem that many early crypto adopters felt: the Web required too much trust. That is, most of the Web that people know and use today relies on trusting a handful of private companies to act in the public's best interests.
+The premise of 'Web 3.0' was coined by [Ethereum](/) co-founder Gavin Wood shortly after Ethereum launched in 2014. Gavin put into words a solution for a problem that many early crypto adopters felt: the Web required too much trust. That is, most of the Web that people know and use today relies on trusting a handful of private companies to act in the public's best interests.
@@ -108,7 +108,7 @@ However, people define many Web3 communities as DAOs. These communities all have
Traditionally, you would create an account for every platform you use. For example, you might have a Twitter account, a YouTube account, and a Reddit account. Want to change your display name or profile picture? You have to do it across every account. You can use social sign-ins in some cases, but this presents a familiar problem—censorship. In a single click, these platforms can lock you out of your entire online life. Even worse, many platforms require you to trust them with personally identifiable information to create an account.
-Web3 solves these problems by allowing you to control your digital identity with an Ethereum address and [Ethereum Name Service (ENS)](/glossary/#ens) profile. Using an [Ethereum](/) address provides a single login across platforms that is secure, censorship-resistant, and anonymous.
+Web3 solves these problems by allowing you to control your digital identity with an Ethereum address and [Ethereum Name Service (ENS)](/glossary/#ens) profile. Using an Ethereum address provides a single login across platforms that is secure, censorship-resistant, and anonymous.
### Native payments {#native-payments}
diff --git a/public/content/whitepaper/index.md b/public/content/whitepaper/index.md
index 4bf3981292e..0f6434c7265 100644
--- a/public/content/whitepaper/index.md
+++ b/public/content/whitepaper/index.md
@@ -14,7 +14,7 @@ _While several years old, we maintain the original paper below because it contin
## A Next-Generation Smart Contract and Decentralized Application Platform {#a-next-generation-smart-contract-and-decentralized-application-platform}
-Satoshi Nakamoto's development of Bitcoin in 2009 has often been hailed as a radical development in money and currency, being the first example of a digital asset which simultaneously has no backing or "[intrinsic value](https://bitcoinmagazine.com/culture/an-exploration-of-intrinsic-value-what-it-is-why-bitcoin-doesnt-have-it-and-why-bitcoin-does-have-it)" and no centralized issuer or controller. However, another, arguably more important, part of the Bitcoin experiment is the underlying blockchain technology as a tool of distributed consensus, and attention is rapidly starting to shift to this other aspect of Bitcoin. Commonly cited alternative applications of blockchain technology include using on-blockchain digital assets to represent custom currencies and financial instruments ("[colored coins](https://docs.google.com/a/buterin.com/document/d/1AnkP_cVZTCMLIzw4DvsW6M8Q2JC0lIzrTLuoWu2z1BE/edit)"), the ownership of an underlying physical device ("[smart property](https://en.bitcoin.it/wiki/Smart_Property)"), non-fungible assets such as domain names ("[Namecoin](http://namecoin.org)"), as well as more complex applications involving having digital assets being directly controlled by a piece of code implementing arbitrary rules ("[smart contracts](http://www.fon.hum.uva.nl/rob/Courses/InformationInSpeech/CDROM/Literature/LOTwinterschool2006/szabo.best.vwh.net/idea.html)") or even blockchain-based "[decentralized autonomous organizations](http://bitcoinmagazine.com/7050/bootstrapping-a-decentralized-autonomous-corporation-part-i/)" (DAOs). What [Ethereum](/) intends to provide is a blockchain with a built-in fully fledged Turing-complete programming language that can be used to create "contracts" that can be used to encode arbitrary state transition functions, allowing users to create any of the systems described above, as well as many others that we have not yet imagined, simply by writing up the logic in a few lines of code.
+Satoshi Nakamoto's development of Bitcoin in 2009 has often been hailed as a radical development in money and currency, being the first example of a digital asset which simultaneously has no backing or "[intrinsic value](https://bitcoinmagazine.com/culture/an-exploration-of-intrinsic-value-what-it-is-why-bitcoin-doesnt-have-it-and-why-bitcoin-does-have-it)" and no centralized issuer or controller. However, another, arguably more important, part of the Bitcoin experiment is the underlying blockchain technology as a tool of distributed consensus, and attention is rapidly starting to shift to this other aspect of Bitcoin. Commonly cited alternative applications of blockchain technology include using on-blockchain digital assets to represent custom currencies and financial instruments ("[colored coins](https://docs.google.com/a/buterin.com/document/d/1AnkP_cVZTCMLIzw4DvsW6M8Q2JC0lIzrTLuoWu2z1BE/edit)"), the ownership of an underlying physical device ("[smart property](https://en.bitcoin.it/wiki/Smart_Property)"), non-fungible assets such as domain names ("[Namecoin](http://namecoin.org)"), as well as more complex applications involving having digital assets being directly controlled by a piece of code implementing arbitrary rules ("[smart contracts](http://www.fon.hum.uva.nl/rob/Courses/InformationInSpeech/CDROM/Literature/LOTwinterschool2006/szabo.best.vwh.net/idea.html)") or even blockchain-based "[decentralized autonomous organizations](http://bitcoinmagazine.com/7050/bootstrapping-a-decentralized-autonomous-corporation-part-i/)" (DAOs). What Ethereum intends to provide is a blockchain with a built-in fully fledged Turing-complete programming language that can be used to create "contracts" that can be used to encode arbitrary state transition functions, allowing users to create any of the systems described above, as well as many others that we have not yet imagined, simply by writing up the logic in a few lines of code.
## Introduction to Bitcoin and Existing Concepts {#introduction-to-bitcoin-and-existing-concepts}
diff --git a/public/content/wrapped-eth/index.md b/public/content/wrapped-eth/index.md
index df0858b24b4..daf1b438bde 100644
--- a/public/content/wrapped-eth/index.md
+++ b/public/content/wrapped-eth/index.md
@@ -32,7 +32,7 @@ You are able to unwrap WETH for ETH by using the WETH smart contract. You can re
| | **Ether (ETH)** | **Wrapped Ether (WETH)** |
|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Supply | The [supply of ETH](/eth/supply/) is managed by the Ethereum protocol. The [issuance](/roadmap/merge/issuance) of ETH is handled by Ethereum validators when processing transactions and creating blocks. | WETH is an ERC-20 token whose supply is managed by a smart contract. New units of WETH are issued by the contract after it receives ETH deposits from users, or units of WETH are burned when a user wishes to redeem WETH for ETH. |
+| Supply | The [supply of ETH](/eth/supply/) is managed by the [Ethereum](/) protocol. The [issuance](/roadmap/merge/issuance) of ETH is handled by Ethereum validators when processing transactions and creating blocks. | WETH is an ERC-20 token whose supply is managed by a smart contract. New units of WETH are issued by the contract after it receives ETH deposits from users, or units of WETH are burned when a user wishes to redeem WETH for ETH. |
| Ownership | Ownership is managed by the Ethereum protocol through your account balance. | Ownership of WETH is managed by the WETH token smart contract, secured by the Ethereum protocol. |
| Gas | Ether (ETH) is the accepted unit of payment for computation on the Ethereum network. Gas fees are denominated in gwei (a unit of ether). | Paying gas with WETH tokens is not natively supported. |
diff --git a/public/content/zero-knowledge-proofs/index.md b/public/content/zero-knowledge-proofs/index.md
index 3c8727bb338..414ddfb9220 100644
--- a/public/content/zero-knowledge-proofs/index.md
+++ b/public/content/zero-knowledge-proofs/index.md
@@ -36,7 +36,7 @@ Cryptocurrencies were intended to provide a means for users to conduct private,
There are specific “privacy coins” designed for completely anonymous transactions. Privacy-focused blockchains, such as Zcash and Monero, shield transaction details, including sender/receiver addresses, asset type, quantity, and the transaction timeline.
-By baking in zero-knowledge technology into the protocol, privacy-focused [blockchain](/glossary/#blockchain) networks allow [nodes](/glossary/#node) to validate transactions without needing to access transaction data. [EIP-7503](https://eips.ethereum.org/EIPS/eip-7503) is an example of a proposed design that will enable native private transfers of value on the Ethereum blockchain. Such proposals are, however, difficult to implement due to a mixture of security, regulatory, and UX concerns.
+By baking in zero-knowledge technology into the protocol, privacy-focused [blockchain](/glossary/#blockchain) networks allow [nodes](/glossary/#node) to validate transactions without needing to access transaction data. [EIP-7503](https://eips.ethereum.org/EIPS/eip-7503) is an example of a proposed design that will enable native private transfers of value on the [Ethereum](/) blockchain. Such proposals are, however, difficult to implement due to a mixture of security, regulatory, and UX concerns.
**Zero-knowledge proofs are also being applied to anonymizing transactions on public blockchains**. An example is Tornado Cash, a decentralized, non-custodial service that allows users to conduct private transactions on Ethereum. Tornado Cash uses zero-knowledge proofs to obfuscate transaction details and guarantee financial privacy. Unfortunately, because these are "opt-in" privacy tools they are associated with illicit activity. To overcome this, privacy has to eventually become the default on public blockchains. Learn more about [privacy on Ethereum](/privacy/).
diff --git a/src/intl/en/page-community.json b/src/intl/en/page-community.json
index 1243451d2c0..b6008003f0c 100644
--- a/src/intl/en/page-community.json
+++ b/src/intl/en/page-community.json
@@ -27,7 +27,7 @@
"page-community-get-eth-description": "ETH is the native currency of Ethereum. You'll need some ETH in your wallet to use Ethereum applications.",
"page-community-get-eth-title": "Get some ETH",
"page-community-get-involved-title": "How can I get involved?",
- "page-community-get-involved-description": "There are many ways to get involved in the fast-growing Ethereum community; you can join one of the popular online communities, attend an event, join a meetup group, contribute to a project, or participate in one of the many online forums about Ethereum.",
+ "page-community-get-involved-description": "There are many ways to get involved in the fast-growing Ethereum community; you can join one of the popular online communities, attend an event, join a meetup group, contribute to a project, or participate in one of the many online forums about Ethereum.",
"page-community-get-involved-image-alt": "Get Involved",
"page-community-hero-alt": "Ethereum community hub",
"page-community-hero-header": "Welcome to the Ethereum community hub",
@@ -61,4 +61,4 @@
"page-index-get-started-eth-image-alt": "Illustration of a group of people marvelling at an ether (ETH) glyph in awe.",
"page-index-get-started-dapps-image-alt": "Illustration of a doge using a computer.",
"page-index-get-started-devs-image-alt": "An illustration of a hand creating an ETH logo made of lego bricks."
-}
+}
\ No newline at end of file
diff --git a/src/intl/en/page-get-eth.json b/src/intl/en/page-get-eth.json
index c3253865563..ebfe5d1fe16 100644
--- a/src/intl/en/page-get-eth.json
+++ b/src/intl/en/page-get-eth.json
@@ -9,7 +9,7 @@
"page-get-eth-cex-desc": "Exchanges are businesses that let you buy crypto using traditional currencies. They have custody over any ETH you buy until you send it to a wallet you control.",
"page-get-eth-checkout-dapps-btn": "Check out dapps",
"page-get-eth-community-safety": "Community posts on security",
- "page-get-eth-description": "Ethereum isn't controlled by any single organization - it is decentralized.",
+ "page-get-eth-description": "Ethereum isn't controlled by any single organization - it is decentralized.",
"page-get-eth-dex": "Decentralized exchanges (DEXs)",
"page-get-eth-dex-desc": "If you want more control, buy ETH using smart contracts. With a DEX you can trade digital assets without ever giving control of your funds to a centralized company.",
"page-get-eth-peers": "Receive ETH from your peers",
@@ -76,4 +76,4 @@
"page-get-eth-your-address-wallet-link": "Check out wallets",
"listing-policy-raise-issue-link": "Raise issue",
"page-find-wallet-last-updated": "Last updated"
-}
+}
\ No newline at end of file
diff --git a/src/intl/en/page-layer-2.json b/src/intl/en/page-layer-2.json
index 000d51dc3f4..a880da7ab2c 100644
--- a/src/intl/en/page-layer-2.json
+++ b/src/intl/en/page-layer-2.json
@@ -13,7 +13,7 @@
"page-layer-2-meta-title": "Intro to Ethereum Layer 2: benefits and uses",
"page-layer-2-meta-description": "Learn about Ethereum layer 2 networks",
"page-layer-2-powered-by-ethereum-title": "Powered by Ethereum",
- "page-layer-2-powered-by-ethereum-description-1": "Ethereum is no longer just a single network.",
+ "page-layer-2-powered-by-ethereum-description-1": "Ethereum is no longer just a single network.",
"page-layer-2-powered-by-ethereum-description-2": "With hundreds of blockchains now built on top of it, Ethereum has become more cost-effective, faster, and accessible for everyday use.",
"page-layer-2-powered-by-ethereum-description-3": "Embrace the future by joining one of the many networks powered by Ethereum!",
"page-layer-2-man-and-dog-alt": "Man and dog playing",
@@ -58,4 +58,4 @@
"page-layer-2-unichain-description": "Unichain is a DeFi-native Ethereum L2, built to be the home for liquidity across chains",
"page-layer-2-ink-description": "Ink is an Ethereum OP Stack layer 2 blockchain designed to be the house of DeFi for the Superchain; a powerful baselayer for deploying innovative DeFi protocols.",
"page-layer-2-zircuit-description": "Zircuit is an EVM-compatible ZK Rollup featuring AI-powered Sequencer-Level Security to detect and prevent malicious transactions."
-}
+}
\ No newline at end of file
diff --git a/src/intl/en/page-roadmap.json b/src/intl/en/page-roadmap.json
index f82dba5e149..f0a5de9ff5e 100644
--- a/src/intl/en/page-roadmap.json
+++ b/src/intl/en/page-roadmap.json
@@ -4,7 +4,7 @@
"page-roadmap-meta-description": "The path to more scalability, security and sustainability for Ethereum.",
"page-roadmap-banner-notification": "Ethereum's development is community-driven and subject to change.",
"page-roadmap-changes-coming-title": "What changes are coming to Ethereum?",
- "page-roadmap-changes-coming-description": "Ethereum is already a powerful platform, but it is still being improved. An ambitious set of improvements will upgrade Ethereum from its current form into a fully scaled, maximally resilient platform.",
+ "page-roadmap-changes-coming-description": "Ethereum is already a powerful platform, but it is still being improved. An ambitious set of improvements will upgrade Ethereum from its current form into a fully scaled, maximally resilient platform.",
"page-roadmap-cheaper-transactions-title": "Cheaper transactions",
"page-roadmap-cheaper-transactions-description": "Rollups are too expensive and rely on centralized components, causing users to place too much trust in their operators. The roadmap includes fixes for both of these problems.",
"page-roadmap-cheaper-transactions-button": "More on reducing fees",
@@ -99,4 +99,4 @@
"page-roadmap-glamsterdam-discussed-title": "Scheduled for Glamsterdam",
"page-roadmap-glamsterdam-discussed-item-1": "Enshrined Proposer-Builder Separation (ePBS)",
"page-roadmap-glamsterdam-discussed-item-2": "Block-level Access Lists (BALs)"
-}
+}
\ No newline at end of file
diff --git a/src/intl/en/page-run-a-node.json b/src/intl/en/page-run-a-node.json
index 5a1b796ae8c..512863a78fa 100644
--- a/src/intl/en/page-run-a-node.json
+++ b/src/intl/en/page-run-a-node.json
@@ -118,7 +118,7 @@
"page-run-a-node-voice-your-choice-2": "If you're staking ETH, running your own node allows you to choose your own client, to minimize your risk of slashing and to react to fluctuating demands of the network over time. Staking with a third party forfeits your vote on which client you think is the best choice.",
"page-run-a-node-what-title": "What does it mean to \"run a node\"?",
"page-run-a-node-what-1-subtitle": "Run software.",
- "page-run-a-node-what-1-text": "Known as a 'client', this software downloads a copy of the Ethereum blockchain and verifies the validity of every block, then keeps it up-to-date with new blocks and transactions, and helps others download and update their own copies.",
+ "page-run-a-node-what-1-text": "Known as a 'client', this software downloads a copy of the Ethereum blockchain and verifies the validity of every block, then keeps it up-to-date with new blocks and transactions, and helps others download and update their own copies.",
"page-run-a-node-what-2-subtitle": "With hardware.",
"page-run-a-node-what-2-text": "Ethereum is designed to run a node on average consumer-grade computers. You can use any personal computer, but most users opt to run their node on dedicated hardware to eliminate the performance impact on their machine and minimize node downtime.",
"page-run-a-node-what-3-subtitle": "While online.",
@@ -130,4 +130,4 @@
"page-run-a-node-who-copy-3": "Having your own node means you don't need to trust information about the state of the network provided by a third party.",
"page-run-a-node-who-copy-bold": "Don't trust. Verify.",
"page-run-a-node-why-title": "Why run a node?"
-}
+}
\ No newline at end of file
diff --git a/src/intl/en/page-stablecoins.json b/src/intl/en/page-stablecoins.json
index 459f98d01b3..9c7f0031ea3 100644
--- a/src/intl/en/page-stablecoins.json
+++ b/src/intl/en/page-stablecoins.json
@@ -98,7 +98,7 @@
"page-stablecoins-precious-metals-description": "Like fiat-backed coins, instead these stablecoins use resources like gold to maintain their value. These are 'stable' in that their price is consistently pegged to the value of another asset, and are akin to onchain ownership tracking of real-world assets",
"page-stablecoins-precious-metals-pro-1": "Safe against crypto volatility.",
"page-stablecoins-prices": "Stablecoin prices",
- "page-stablecoins-prices-definition": "Stablecoins are cryptocurrencies without the volatility. They share a lot of the same powers as ETH but their value is steady, more like a traditional currency. So you have access to stable money that you can use on Ethereum. ",
+ "page-stablecoins-prices-definition": "Stablecoins are cryptocurrencies without the volatility. They share a lot of the same powers as ETH but their value is steady, more like a traditional currency. So you have access to stable money that you can use on Ethereum. ",
"page-stablecoins-prices-definition-how": "How stablecoins get their stability",
"page-stablecoins-research-warning": "Ethereum is a new technology and most applications are new. Make sure you're aware of the risk and only deposit what you can afford to lose.",
"page-stablecoins-research-warning-title": "Always do your own research",
@@ -193,4 +193,4 @@
"summerfi-logo": "Summer.fi logo",
"uniswap-logo": "Uniswap logo",
"page-stablecoins-go-to": "Go to"
-}
+}
\ No newline at end of file
diff --git a/src/intl/en/page-staking.json b/src/intl/en/page-staking.json
index b1c2e35cc3b..b60a6ebb9ef 100644
--- a/src/intl/en/page-staking.json
+++ b/src/intl/en/page-staking.json
@@ -24,7 +24,7 @@
"page-staking-benefits-3-title": "More sustainable",
"page-staking-benefits-3-description": "Stakers don't need to do energy-intensive proof-of-work computations to participate in securing the network meaning staking nodes can run on relatively modest hardware using very little energy.",
"page-staking-benefits-3-link": "More on Ethereum's energy consumption",
- "page-staking-description": "Staking is the act of depositing 32 ETH to activate validator software. As a validator you’ll be responsible for storing data, processing transactions, and adding new blocks to the blockchain. This will keep Ethereum secure for everyone and earn you new ETH in the process.",
+ "page-staking-description": "Staking is the act of depositing 32 ETH to activate validator software. As a validator you’ll be responsible for storing data, processing transactions, and adding new blocks to the blockchain. This will keep Ethereum secure for everyone and earn you new ETH in the process.",
"page-staking-hero-title": "How to stake your ETH",
"page-staking-hero-header": "Earn rewards while securing Ethereum",
"page-staking-hero-subtitle": "Any user with any amount of ETH can help secure the network and earn rewards in the process.",
@@ -49,7 +49,7 @@
"page-staking-guide-title-somer-esat": "Somer Esat",
"page-staking-guide-title-rocket-pool": "Rocket Pool Node Operators",
"page-staking-guide-title-stakewise": "StakeWise Node Operators",
- "page-staking-guide-title-lido-csm":"Lido CSM Node Operators",
+ "page-staking-guide-title-lido-csm": "Lido CSM Node Operators",
"page-staking-guide-description-linux": "Linux (CLI)",
"page-staking-guide-description-mac-linux": "Linux, macOS (CLI)",
"page-staking-guide-description-mac-linux-windows": "Linux, Windows, MacOS (CLI)",
@@ -237,4 +237,4 @@
"page-staking-comparison-with-other-options": "Comparison with other options",
"page-staking-any-amount": "Any amount",
"page-staking-network-testnet": "{network} testnet"
-}
+}
\ No newline at end of file
diff --git a/src/intl/en/page-wallets.json b/src/intl/en/page-wallets.json
index 22f38d267ff..37b5c84f6b1 100644
--- a/src/intl/en/page-wallets.json
+++ b/src/intl/en/page-wallets.json
@@ -12,7 +12,7 @@
"page-wallets-desc-2-link": "More on ETH",
"page-wallets-desc-3": "Your wallet is a tool for interacting with your Ethereum account. That means you can swap wallet providers at any time. Many wallets also let you manage several Ethereum accounts from one application.",
"page-wallets-desc-4": "Wallet providers don't have custody of your funds. They just provide you a window to see your assets on Ethereum and tools to easily manage them.",
- "page-wallets-description": "Ethereum wallets are applications that give you control over your account. Just like your physical wallet, it contains everything you need to prove your identity and handle your assets. Your wallet allows you to sign in to applications, read your balance, send transactions and verify your identity.",
+ "page-wallets-description": "Ethereum wallets are applications that give you control over your account. Just like your physical wallet, it contains everything you need to prove your identity and handle your assets. Your wallet allows you to sign in to applications, read your balance, send transactions and verify your identity.",
"page-wallets-desktop": "Desktop applications if you prefer to manage your funds via macOS, Windows or Linux",
"page-wallets-ethereum-wallet": "A wallet is a tool that lets you interact with your account, using your keys. It allows you to view your account balance, send transactions, and more.",
"page-wallets-explore": "Explore Ethereum",
@@ -63,4 +63,4 @@
"page-wallets-your-login-desc": "Your wallet lets you connect to applications using your Ethereum account. It's like a login you can use across many apps.",
"additional-reading-how-to-create-an-ethereum-account": "How to create an Ethereum account",
"additional-reading-how-to-use-a-wallet": "How to use a wallet"
-}
+}
\ No newline at end of file
diff --git a/src/intl/en/page-what-is-ethereum.json b/src/intl/en/page-what-is-ethereum.json
index 1f4fc869379..6167c71fbda 100644
--- a/src/intl/en/page-what-is-ethereum.json
+++ b/src/intl/en/page-what-is-ethereum.json
@@ -4,7 +4,7 @@
"page-what-is-ethereum-title": "What is Ethereum?",
"page-what-is-ethereum-hero-description-1": "Ethereum is a decentralized blockchain network and software development platform, powered by the cryptocurrency ether (ETH).",
"page-what-is-ethereum-hero-description-2": "It's home to thousands of cryptocurrencies and applications across DeFi, NFTs, gaming, decentralized social media and stablecoins.",
- "page-what-is-ethereum-ethereum-intro-1": "Ethereum is an open, public blockchain launched in July 2015 by a software developer called Vitalik Buterin and a small team of co-founders.",
+ "page-what-is-ethereum-ethereum-intro-1": "Ethereum is an open, public blockchain launched in July 2015 by a software developer called Vitalik Buterin and a small team of co-founders.",
"page-what-is-ethereum-ethereum-intro-2": "The idea behind Ethereum was simple. While Bitcoin lets you send and receive digital cash, Ethereum would build on this with open-source programs called smart contracts.",
"page-what-is-ethereum-ethereum-intro-3": "Smart contracts let anyone create their own digital assets and decentralized applications (dapps) that run 24/7, globally. And unlike banks, corporations or other institutions, smart contracts are available to anyone with an internet connection.",
"page-what-is-ethereum-ethereum-intro-4": "Since 2015, Ethereum has grown into a thriving ecosystem of digital assets like stablecoins, non-fungible tokens (NFTs), and governance tokens, as well as a sprawling world of dapps for decentralized finance (DeFi), art and collectibles, gaming and decentralized social media.",
@@ -184,4 +184,4 @@
"page-what-is-ethereum-banner-what-alt": "Four futuristic humans and a doge gazing into an Ethereum prism",
"page-what-is-ethereum-banner-start-alt": "Futuristic community gathering center",
"page-what-is-ethereum-banner-when-who-alt": "Two humans walking and talking"
-}
+}
\ No newline at end of file