Skip to content

Commit b419789

Browse files
fix broken local links
1 parent 8c002df commit b419789

File tree

6 files changed

+12
-12
lines changed

6 files changed

+12
-12
lines changed

docs/pos/get-started/becoming-a-validator.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -98,13 +98,13 @@ The following technical node operations are **done automatically by the nodes:**
9898
* If more than 2/3 of the active validators reach consensus on the checkpoint, the checkpoint is submitted to the Ethereum mainnet.
9999
* Sync changes to Polygon staking contracts on Ethereum:
100100
* Continuing from the checkpoint submission step, since this is an external network call, the checkpoint transaction on Ethereum may or may not be confirmed, or may be pending due to Ethereum congestion issues.
101-
* In this case, there is an `ack/no-ack` process that is followed to ensure that the next checkpoint contains a snapshot of the previous Bor blocks as well. For example, if checkpoint 1 is for Bor blocks 1-256, and it failed for some reason, the next checkpoint 2 will be for Bor blocks 1-512. See also [Heimdall architecture: Checkpoint](/pos/architecture/heimdall/checkpoints).
101+
* In this case, there is an `ack/no-ack` process that is followed to ensure that the next checkpoint contains a snapshot of the previous Bor blocks as well. For example, if checkpoint 1 is for Bor blocks 1-256, and it failed for some reason, the next checkpoint 2 will be for Bor blocks 1-512. See also [Heimdall architecture: Checkpoint](../architecture/heimdall/checkpoints.md).
102102
* State sync from the Ethereum mainnet to Bor:
103103
* Contract state can be moved between Ethereum and Polygon, specifically through Bor:
104104
* A DApp contract on Ethereum calls a function on a special Polygon contract on Ethereum.
105105
* The corresponding event is relayed to Heimdall and then Bor.
106106
* A state-sync transaction gets called on a Polygon smart contract and the DApp can get the value on Bor via a function call on Bor itself.
107-
* A similar mechanism is in place for sending state from Polygon to Ethereum. See also [State Sync Mechanism](/pos/how-to/bridging/l1-l2-communication/state-transfer).
107+
* A similar mechanism is in place for sending state from Polygon to Ethereum. See also [State Sync Mechanism](../how-to/bridging/l1-l2-communication/state-transfer.md).
108108

109109
### Operations
110110

@@ -176,14 +176,14 @@ The following step-by-step guides will take you through the process of running a
176176

177177
### Join the network as a validator
178178

179-
* [Start and run the nodes with Ansible](/pos/how-to/validator/validator-ansible).
180-
* [Start and run the nodes with binaries](/pos/how-to/validator/validator-binaries).
181-
* [Stake as a validator](/pos/how-to/operate-validator-node/validator-staking-operations).
179+
* [Start and run the nodes with Ansible](../how-to/validator/validator-ansible.md).
180+
* [Start and run the nodes with binaries](../how-to/validator/validator-binaries.md).
181+
* [Stake as a validator](../how-to/operate-validator-node/validator-staking-operations.md).
182182

183183
### Maintain your validator nodes
184184

185-
* [Change the signer address](/pos/how-to/operate-validator-node/change-signer-address).
186-
* [Change the commission](/pos/how-to/operate-validator-node/validator-commission-operations).
185+
* [Change the signer address](../how-to/operate-validator-node/change-signer-address.md).
186+
* [Change the commission](../how-to/operate-validator-node/validator-commission-operations.md).
187187

188188
### Community assistance
189189

docs/pos/how-to/snapshots.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ When setting up a new sentry, validator, or full node server, it is recommended
1111

1212
## Client snapshots
1313

14-
To begin, ensure that your node environment meets the **prerequisites** outlined [here](/pos/how-to/full-node/full-node-binaries). Before starting any services, execute the shell script provided below. This script will download and extract the snapshot data, which allows for faster bootstrapping. In our example, we will be using an Ubuntu Linux m5d.4xlarge machine with an 8TB block device attached.
14+
To begin, ensure that your node environment meets the **prerequisites** outlined [here](../how-to/full-node/full-node-binaries.md). Before starting any services, execute the shell script provided below. This script will download and extract the snapshot data, which allows for faster bootstrapping. In our example, we will be using an Ubuntu Linux m5d.4xlarge machine with an 8TB block device attached.
1515
To transfer the correct chaindata to your disk, follow these steps:
1616

1717
- All one has to do is specify the network ("mainnet" or "mumbai") and client type ("heimdall" or "bor" or "erigon") of your desired snapshot and run the following command:

docs/pos/how-to/validator/prerequisites.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ sudo dpkg -i rabbitmq-server_3.10.8-1_all.deb
9494
Below are some additional information to the official documentation which might help while setting up a new node.
9595

9696

97-
This document gives some additional details for setting up a new node based on [full node deployment](/pos/how-to/full-node/full-node-binaries) guide.
97+
This document gives some additional details for setting up a new node based on [full node deployment](../../how-to/full-node/full-node-binaries.md) guide.
9898

9999
- VPN setup is required before proceeding with any of these steps.
100100
- If you are using Macbook, it has native Python 2.7 available which **needs to be replaced by with anything Python 3.x**.

docs/pos/reference/rewards.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ To leverage Polygon's economics, you should either become a validator or a deleg
44

55
To be a validator, you need to **run a full validator** node and stake MATIC.
66

7-
Also check the [Validator Responsibilities](/pos/design/validator/responsibilities) page.
7+
Also check the [Validator Responsibilities](../get-started/becoming-a-validator.md#validator-responsibilities) page.
88

99
To be a delegator, you only need to **delegate MATIC to a validator**
1010

docs/tools/wallets/walletkit.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
!!! caution "Content disclaimer"
22
Please view the third-party content disclaimer [here](https://github.com/0xPolygon/polygon-docs/blob/main/CONTENT_DISCLAIMER.md).
33

4-
![WalletKit](/img/tools/wallet/walletkit/walletkit-overview.png)
4+
![WalletKit](../../img/tools/wallet/walletkit/walletkit-overview.png)
55

66
[WalletKit](https://walletkit.com) is an all-in-one platform for adding smart, gasless wallets to your app. WalletKit offers pre-built components for onboarding users with email and social logins, which can be integrated in under 15 minutes using their React SDK or the wagmi connector. Alternatively, build completely bespoke experiences for your users using WalletKit's Wallets API.
77

mkdocs.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -595,7 +595,7 @@ plugins:
595595
- open-in-new-tab
596596

597597
validation:
598-
absolute_links: ignore
598+
absolute_links: warn
599599

600600
extra_javascript:
601601
- _site_essentials/js/mathjax.js

0 commit comments

Comments
 (0)