From 65d4c718e34d6ff86430bc4e2c85f0961f013d7e Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Thu, 11 Jul 2024 17:23:46 +0200 Subject: [PATCH] Fix broken links (#30143) --- docs/fundamentals/peer-to-peer.md | 2 +- docs/interacting-with-geth/rpc/index.md | 2 +- docs/monitoring/understanding-dashboards.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/fundamentals/peer-to-peer.md b/docs/fundamentals/peer-to-peer.md index aab1886b0d..7eedbc8c82 100644 --- a/docs/fundamentals/peer-to-peer.md +++ b/docs/fundamentals/peer-to-peer.md @@ -3,7 +3,7 @@ title: Connecting To The Network description: Guide to connecting Geth to a peer-to-peer network --- -The default behaviour for Geth is to connect to Ethereum Mainnet. However, Geth can also connect to public testnets, [private networks](/docs/fundamentals/private-network) and [local testnets](/docs/developers/geth-developer/dev-mode). For convenience, the two public testnets with long term support, Goerli and Sepolia, have their own command line flag. Geth can connect to these testnets simply by passing: +The default behaviour for Geth is to connect to Ethereum Mainnet. However, Geth can also connect to public testnets, [private networks](/docs/fundamentals/private-network) and [local testnets](/docs/developers/dapp-developer/dev-mode). For convenience, the two public testnets with long term support, Goerli and Sepolia, have their own command line flag. Geth can connect to these testnets simply by passing: - `--goerli`, Goerli proof-of-authority test network - `--sepolia` Sepolia proof-of-work test network diff --git a/docs/interacting-with-geth/rpc/index.md b/docs/interacting-with-geth/rpc/index.md index 38834fead1..486e9e11cd 100644 --- a/docs/interacting-with-geth/rpc/index.md +++ b/docs/interacting-with-geth/rpc/index.md @@ -117,7 +117,7 @@ As a general rule IPC is most secure because it is limited to interactions on th The Engine-API is a set of RPC methods that enable communication between Geth and the [consensus client](/docs/getting-started/consensus-clients). These are not designed to be exposed to the user - instead they are called automatically by the clients when they need to exchange information. The Engine API is enabled by default - the user is not required to pass any instruction to Geth to enable these methods. -Read more in the [Engine API spec](https://github.com/ethereum/execution-apis/blob/main/src/engine/specification.md). +Read more in the [Engine API spec](https://github.com/ethereum/execution-apis/blob/main/src/engine). ## Summary {#summary} diff --git a/docs/monitoring/understanding-dashboards.md b/docs/monitoring/understanding-dashboards.md index 15009b6495..ff1d5342de 100644 --- a/docs/monitoring/understanding-dashboards.md +++ b/docs/monitoring/understanding-dashboards.md @@ -3,7 +3,7 @@ title: Understanding Geth's dashboard description: How to use a dashboard to understand a Geth node's performance --- -Our [dashboards page](/docs/monitoring/dashboards.md) explains how to set up a Grafana dashboard for monitoring your Geth node. This page explores the dashboard itself, explaining what the various metrics are and what they mean for the health of a node. Note that the raw data informing the dashboard can be viewed in JSON format in the browser by navigating to the ip address and port passed to `--metrics.addr` and `--metrics.port` (`127.0.0.1:6060` by default). +Our [dashboards page](/docs/monitoring/dashboards) explains how to set up a Grafana dashboard for monitoring your Geth node. This page explores the dashboard itself, explaining what the various metrics are and what they mean for the health of a node. Note that the raw data informing the dashboard can be viewed in JSON format in the browser by navigating to the ip address and port passed to `--metrics.addr` and `--metrics.port` (`127.0.0.1:6060` by default). ## What does the dashboard look like?