aligns remote with local

docs/public-networks/how-to/use-configuration-file/defaults.md

@@ -10,18 +10,14 @@ Besu is [highly-configurable](index.md#configuration-order-of-precedence), yet i
 
 This page provides a high level overview of the opinionated default configurations of vanilla Besu. By applying these defaults, a node is optimized for staking. These defaults may be used alongside a [pre-configured profile](profile.md) to support common use cases.
 
-
-For example, using the [staking profile](profile.md#staker-profile) with the boilerplate config directs Besu to use mainnet — instantiating a staking-optimized node ready to be run alongside a [validator](https://ethereum.org/en/developers/docs/nodes-and-clients/node-architecture/#validators) and [consensus client](https://ethereum.org/en/developers/docs/nodes-and-clients/node-architecture/#consensus-client).
-
-:::
+For example, using the [staking profile](profile.md#staker-profile) with the boilerplate config directs Besu to use Mainnet, creating a staking-optimized node ready to run with a [validator](https://ethereum.org/en/developers/docs/nodes-and-clients/node-architecture/#validators) and [consensus client](https://ethereum.org/en/developers/docs/nodes-and-clients/node-architecture/#consensus-client)
 
 ## Configuration
 
 |Command|Default|Notes|
 |---------------------------|--------------------|------------------------------------------|
 |[`config-file`](../../reference/cli/options/#config-file)|None|Vanilla Besu assumes no configuration file|
 
-
 ## Storage
 
 |Command|Default|Notes|