diff --git a/docs/networks/node-ops/access-onchain-data/access-nodes/access-node-setup.mdx b/docs/networks/node-ops/access-onchain-data/access-nodes/access-node-setup.md similarity index 98% rename from docs/networks/node-ops/access-onchain-data/access-nodes/access-node-setup.mdx rename to docs/networks/node-ops/access-onchain-data/access-nodes/access-node-setup.md index 255bc83b50..1ac0b5dfb9 100644 --- a/docs/networks/node-ops/access-onchain-data/access-nodes/access-node-setup.mdx +++ b/docs/networks/node-ops/access-onchain-data/access-nodes/access-node-setup.md @@ -253,7 +253,7 @@ Account staking info: ### Epoch Setup Event -Alternatively, if you can monitor events, look for [the epoch setup event](../../../staking/05-epoch-scripts-events.md#epochsetup) that gets emitted by the epoch contract. That event is emitted at the end of epoch N's staking auction and contains a list of node IDs that are confirmed for the next epoch. +Alternatively, if you can monitor events, look for [the epoch setup event](../../../staking/05-epoch-scripts-events.md#flowepochepochsetup) that gets emitted by the epoch contract. That event is emitted at the end of epoch N's staking auction and contains a list of node IDs that are confirmed for the next epoch. ## Step 4 - Start Your Node diff --git a/docs/networks/node-ops/index.md b/docs/networks/node-ops/index.md index bdace7cc11..95aadc1171 100644 --- a/docs/networks/node-ops/index.md +++ b/docs/networks/node-ops/index.md @@ -75,7 +75,7 @@ Launch an access node using QuickNode :::info -To run a self-hosted access node, follow this [guide](./access-onchain-data/access-nodes/access-node-setup.mdx) +To run a self-hosted access node, follow this [guide](./access-onchain-data/access-nodes/access-node-setup.md) ::: diff --git a/docs/networks/node-ops/node-operation/faq.md b/docs/networks/node-ops/node-operation/faq.md index b82afebfa1..227745328a 100644 --- a/docs/networks/node-ops/node-operation/faq.md +++ b/docs/networks/node-ops/node-operation/faq.md @@ -9,7 +9,7 @@ sidebar_position: 1 Anyone can run an [observer node](../access-onchain-data/light-nodes/observer-node.md). -Anyone can run an Access Node after registering and staking. See [Access Node Setup](../access-onchain-data/access-nodes/access-node-setup.mdx) for detailed instructions. +Anyone can run an Access Node after registering and staking. See [Access Node Setup](../access-onchain-data/access-nodes/access-node-setup.md) for detailed instructions. For the other node roles, individuals can go through an application process that involves asking about their background and experience contributing to decentralized projects. To pursue an application, please visit [the Flow website here to apply](https://www.onflow.org/node-validators). @@ -19,7 +19,7 @@ In the long-term, anyone can run a node validator on Flow. ### How do I generate keys? -Please follow the instructions provided here: [Generate Your Node Keys](./node-bootstrap.md#generating-your-node-keys) +Please follow the instructions provided here: [Generate Your Node Keys](./node-bootstrap.md#generate-your-node-keys) ### How do I check on the status of my node? diff --git a/docs/networks/node-ops/node-operation/guides/genesis-bootstrap.md b/docs/networks/node-ops/node-operation/guides/genesis-bootstrap.md index 02e194bd84..c7b724aad0 100644 --- a/docs/networks/node-ops/node-operation/guides/genesis-bootstrap.md +++ b/docs/networks/node-ops/node-operation/guides/genesis-bootstrap.md @@ -57,7 +57,7 @@ Start the bootstrapping process by generating your Staking Key and Networking Ke This command generates two keys, a Staking Key and a Network Key, and stores them both in a `.node-info` file. Both these keys are needed during runtime and must be present as a file to start your flow node. -For more details around all the keys that are needed to run nodes and their usage, see the [Node Keys](../node-bootstrap.md#generating-your-node-keys) overview. +For more details around all the keys that are needed to run nodes and their usage, see the [Node Keys](../node-bootstrap.md#generate-your-node-keys) overview. The bootstrapping process will create a file structure similar to the following diff --git a/docs/networks/node-ops/node-operation/node-bootstrap.md b/docs/networks/node-ops/node-operation/node-bootstrap.md index 31298912bc..6ba1fff507 100644 --- a/docs/networks/node-ops/node-operation/node-bootstrap.md +++ b/docs/networks/node-ops/node-operation/node-bootstrap.md @@ -5,7 +5,7 @@ description: How to get started running a node on Flow sidebar_position: 8 --- -This guide is for getting a new node staked and running on Flow other than a permissionless Access node. For running a permissionless Access node see [Access node setup](../access-onchain-data/access-nodes/access-node-setup.mdx). For sporking documentation for existing node operators, see [Spork Process](./spork.md). +This guide is for getting a new node staked and running on Flow other than a permissionless Access node. For running a permissionless Access node see [Access node setup](../access-onchain-data/access-nodes/access-node-setup.md). For sporking documentation for existing node operators, see [Spork Process](./spork.md). ## Timing diff --git a/docs/networks/node-ops/node-operation/node-setup.md b/docs/networks/node-ops/node-operation/node-setup.md index 52f54a2649..7addeaaed0 100644 --- a/docs/networks/node-ops/node-operation/node-setup.md +++ b/docs/networks/node-ops/node-operation/node-setup.md @@ -6,7 +6,7 @@ sidebar_position: 12 --- This guide is for running a Collection, Consensus, Verification and Execution node. -If you are planning to run an Access node then refer to [access node setup](../access-onchain-data/access-nodes/access-node-setup.mdx). +If you are planning to run an Access node then refer to [access node setup](../access-onchain-data/access-nodes/access-node-setup.md). First you'll need to provision a machine or virtual machine to run your node software. Please see follow the [node-provisioning](./node-provisioning.md) guide for it.