Merge pull request #5252 from ethereum/header-ids

Fix glossary term header ids

src/content/glossary/index.md

@@ -123,11 +123,11 @@ A group of at least 128 [validators](#validator) assigned to beacon and shard bl
 
 When numerous nodes (usually most nodes on the network) all have the same blocks in their locally validated best blockchain. Not to be confused with [consensus rules](#consensus-rules).
 
-### consensus client {consensus-client}
+### consensus client {#consensus-client}
 
 Consensus clients (such as Prysm, Teku, Nimbus, Lighthouse, Lodestar) run Ethereum's [proof-of-stake](#pos) consensus algorithm allowing the network to reach agreement about the head of the Beacon Chain. Consensus clients do not participate in validating/broadcasting transactions or executing state transitions. This is done by [execution clients](#execution-client).
 
-### consensus layer {consensus-layer}
+### consensus layer {#consensus-layer}
 
 Ethereum's consensus layer is the network of [consensus clients](#consensus-client).
 
@@ -261,7 +261,7 @@ In the context of cryptography, lack of predictability or level of randomness. W
 
 Execution clients (f.k.a. "Eth1 clients"), such as Besu, Erigon, go-ethereum, Nethermind, are tasked with processing and broadcasting transactions, as well as with managing Ethereum's state. They run the computations for each transaction in the [Ethereum Virtual Machine](#evm) to ensure that the rules of the protocol are followed. Today, they also handle proof of work consensus. After the transition to [proof of stake](#pos), they will delegate this to consensus clients.
 
-### execution layer
+### execution layer {#execution-layer}
 
 Ethereum's execution layer is the network of [execution clients](#execution-client).