Fix 404 errors. (#1829)

Signed-off-by: bgravenorst <[email protected]>

Author: bgravenorst

docs/private-networks/how-to/monitor/opentelemetry.md

@@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem';
 
 # Use OpenTelemetry
 
-You can use the OpenTelemetry monitoring and tracing service to gather node metrics and traces. To enable OpenTelemetry to access Besu, use the [`--metrics-enabled`](../../../public-networks/reference/cli/options.md#metrics-enabled) and [`--metrics-protocol=opentelemetry`](../../../public-networks/reference/cli/options.md#metrics-protocol) options. Use [Splunk](https://splunk.com) to visualize the collected data. A [Besu Sync example](https://github.com/splunk/splunk-connect-for-ethereum/tree/master/examples/besu-sync) is available.
+You can use the OpenTelemetry monitoring and tracing service to gather node metrics and traces. To enable OpenTelemetry to access Besu, use the [`--metrics-enabled`](../../../public-networks/reference/cli/options.md#metrics-enabled) and [`--metrics-protocol=opentelemetry`](../../../public-networks/reference/cli/options.md#metrics-protocol) options. Use [Splunk](https://splunk.com) to visualize the collected data.
 
 :::tip
 
@@ -145,8 +145,6 @@ You can also install exporters that send system metrics to OpenTelemetry to moni
 
     </Tabs>
 
-    You can also refer to this [Docker-compose example](https://github.com/splunk/splunk-connect-for-ethereum/blob/989dc2ccae7d8235bf3ce2a83a18cf0cd1713294/examples/besu-sync/full-sync/docker-compose.yaml).
-
 2.  Start Besu with the [`--metrics-enabled`](../../../public-networks/reference/cli/options.md#metrics-enabled) and [`--metrics-protocol=opentelemetry`](../../../public-networks/reference/cli/options.md#metrics-protocol) options. For example, run the following command to start a single node:
 
     <Tabs>

docs/private-networks/how-to/monitor/splunk.md

@@ -16,7 +16,6 @@ Splunk can aggregate multiple logs in one place and run complex queries without
 Options for running Splunk and Besu are:
 
 - [Developer Quickstart with Splunk](#developer-quickstart-with-splunk)
-- [Splunk Connect for Ethereum Docker Compose](#splunk-connect-for-ethereum-docker-compose)
 - [Use Splunk Enterprise as a Docker container](#use-splunk-enterprise-as-a-docker-container)
 - [Run a Splunk Enterprise instance](#run-a-splunk-enterprise-instance)
 
@@ -27,47 +26,6 @@ To view the Quickstart network logs in Splunk:
 1. [Start the Developer Quickstart with Besu](../../tutorials/quickstart.md), selecting Splunk monitoring.
 1. Open the [Splunk UI](http://localhost:8000).
 
-## Splunk Connect for Ethereum Docker Compose
-
-To run a development Besu node and connect it to Splunk Enterprise, use the Splunk Connect for Ethereum demonstration Docker Compose environment provided by Splunk.
-
-### Requirements
-
-- [Git](https://git-scm.com/)
-- [Docker and Docker-compose](https://docs.docker.com/compose/install/)
-
-:::info
-
-A Splunk license is not required to use the Splunk Connect for Ethereum demonstration.
-
-:::
-
-### Steps
-
-1.  Clone the Splunk Connect for Ethereum repository:
-
-    ```bash
-    git clone https://github.com/splunk/splunk-connect-for-ethereum.git
-    cd splunk-connect-for-ethereum
-    ```
-
-1.  Start the demonstration environment by following the Splunk Connect for Ethereum repository [README](https://github.com/splunk/splunk-connect-for-ethereum/tree/master/examples/besu).
-
-    :::note
-
-    Splunk enterprise takes some time to start.
-
-    Run `docker ps` and wait for the `STATUS` of the 3 containers to be `Up [number] seconds (healthy)`.
-
-    ```
-    CONTAINER ID        IMAGE                        COMMAND                  CREATED             STATUS                    PORTS                                                                            NAMES
-    127600dd1173        splunkdlt/ethlogger:latest   "ethlogger"              53 seconds ago      Up 51 seconds (healthy)                                                                                    ethlogger
-    88dfcee683c4        splunk/splunk:latest         "/sbin/entrypoint.sh…"   53 seconds ago      Up 52 seconds (healthy)   8065/tcp, 8088-8089/tcp, 8191/tcp, 9887/tcp, 9997/tcp, 0.0.0.0:18000->8000/tcp   splunk
-    111b0c6d6072        hyperledger/besu:1.4.4       "besu"                   53 seconds ago      Up 52 seconds (healthy)   8545-8547/tcp, 30303/tcp                                                         besu
-    ```
-
-    :::
-
 ## Use Splunk Enterprise as a Docker container
 
 ### Prerequisites
@@ -83,7 +41,8 @@ A Splunk license is not required to use the trial version of the Splunk Docker i
 
 :::note
 
-If running [Besu as a Docker container](../../get-started/install/run-docker-image.md), consider using [Splunk Connect for Ethereum Docker Compose](#splunk-connect-for-ethereum-docker-compose) or [Kubernetes](../deploy/kubernetes.md) instead of the Splunk Enterprise trial container.
+If running [Besu as a Docker container](../../get-started/install/run-docker-image.md), consider using
+[Kubernetes](../deploy/kubernetes.md) instead of the Splunk Enterprise trial container.
 
 :::
 
@@ -144,7 +103,7 @@ If running [Besu as a Docker container](../../get-started/install/run-docker-ima
 
     ![Splunk search page](../../../assets/images/splunk-ui.png)
 
-5.  Stop Besu with ++ctrl+c++. Stop the Splunk container with `docker stop splunk-demo`.
+5.  Stop Besu with **ctrl+c**. Stop the Splunk container with `docker stop splunk-demo`.
 
 ## Run a Splunk Enterprise instance
 

docs/private-networks/tutorials/contracts/index.md

@@ -164,7 +164,7 @@ curl -X POST --data '{"jsonrpc":"2.0","method":"eth_sendTransaction","params":[{
 
 ## Use `eea_sendRawTransaction` for private contracts with web3js-quorum
 
-To deploy a private contract to another node or [privacy group](../../concepts/privacy/privacy-groups.md) member, use the [web3js-quorum](https://www.npmjs.com/package/web3js-quorum) library and the [`eea_sendRawTransaction`](../../reference/api/index.md#eea_sendrawtransaction) API call. You must use this API call instead of [`eth_sendTransaction`](https://ethereum.github.io/execution-apis/api-documentation) because Besu keeps account management separate for stronger security.
+To deploy a private contract to another node or [privacy group](../../concepts/privacy/privacy-groups.md) member, use the [web3js-quorum](https://www.npmjs.com/package/web3js-quorum) library and the [`eea_sendRawTransaction`](../../reference/api/index.md#eea_sendrawtransaction) API call. You must use this API call instead of [`eth_sendTransaction`](https://ethereum.github.io/execution-apis/) because Besu keeps account management separate for stronger security.
 
 The Developer Quickstart provides an [example of a private transaction script](https://github.com/ConsenSys/quorum-dev-quickstart/blob/1e8cc281098923802845cd829ec20c88513c2e1c/files/besu/smart_contracts/privacy/scripts/private_tx.js).
 

docs/public-networks/how-to/use-besu-api/authenticate.md

@@ -215,10 +215,10 @@ option depending on your needs.
 :::danger Private key security
 
 The private key must be kept secret. Never share private keys publicly or on a Web site, even if advertised as secure.
-
+<!-- markdown-link-check-disable -->
 Always keep your private keys safe -- ideally using [hardware](https://connect2id.com/products/nimbus-jose-jwt/examples/pkcs11) or [vault](https://www.vaultproject.io/docs/secrets/identity/identity-token) -- and define a strong security policy and
 [best practices](https://auth0.com/docs/secure/tokens/token-best-practices).
-
+<!-- markdown-link-check-enable -->
 Compromised keys can provide attackers access to your node's RPC-API.
 
 :::

docs/public-networks/tutorials/besu-teku-testnet.md

@@ -339,7 +339,7 @@ If you're running Teku as a beacon node only, you're all set. If you're also run
 
 Stake your testnet ETH for one or more validators using the [Holesky Staking Launchpad](https://holesky.launchpad.ethereum.org/), [Hoodi Staking Launchpad](https://hoodi.launchpad.ethereum.org/), or [Ephemery Staking Launchpad](https://launchpad.ephemery.dev/).
 
-You can check your validator status by searching your Ethereum address on the [Holesky explorer](https://holesky.beaconcha.in/), [Hoodi explorer](https://hoodi.cloud.blockscout.com/), or [Ephemery explorer](https://beaconchain.ephemery.dev/). It may take up to multiple days for your validator to be activated and start proposing blocks.
+You can check your validator status by searching your Ethereum address on the [Holesky explorer](https://holesky.beaconcha.in/), [Hoodi explorer](https://hoodi.etherscan.io/), or [Ephemery explorer](https://explorer.ephemery.dev/). It may take up to multiple days for your validator to be activated and start proposing blocks.
 
 <!--links-->