diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 41acf322..dfef06e3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -26,7 +26,7 @@ Lava docs serves multiple user types in different lifecycle steps. We want to create a doc resource that will fit all, but have a common denominator of style. Styleguides are guidance and not a restriction, good articles we picked for this purpose are: -- When it comes to git opeartions, we recommend https://cbea.ms/git-commit/ +- When it comes to git operations, we recommend https://cbea.ms/git-commit/ - When it is docs actual content, we recommend https://medium.com/larimaza-en/how-to-write-good-documentation-e19c70dc67f0 ## Getting started diff --git a/README.md b/README.md index 06f43a3b..c143125f 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,7 @@ Contributing to the documentation of Lava is a rewarding way to give back to the [![Netlify Status](https://api.netlify.com/api/v1/badges/58c0a448-7af0-48d3-8e29-86fc4a6f4868/deploy-status)](https://app.netlify.com/sites/sage-swan-13ac7b/deploys) ### Process -The `main` branch of this repository is automatically deployed to our docs site, and other branches and pull requests leverage Netlify deploy. Please note that unless you are a recognized contributor of this repository, each attempted PR generates a Netlify approval that will prevent your pull request from being merged. Once the request is approved and a Netlify deploy preview is generated, a Netlify deploy preview will appear in the body of your PR as `๐Ÿ˜Ž Deploy Preview`. This deploy preview will be audited by a docs maintainer before merging your pull request. +The `main` branch of this repository is automatically deployed to our docs site, and other branches and pull requests leverage Netlify deployment. Please note that unless you are a recognized contributor of this repository, each attempted PR generates a Netlify approval that will prevent your pull request from being merged. Once the request is approved and a Netlify deploy preview is generated, a Netlify deploy preview will appear in the body of your PR as `๐Ÿ˜Ž Deploy Preview`. This deploy preview will be audited by a docs maintainer before merging your pull request. ## Local Development ๐Ÿ”ง @@ -95,4 +95,4 @@ If you are using GitHub pages for hosting, this command is a convenient way to b ``` $ GIT_USER= yarn deploy -``` \ No newline at end of file +``` diff --git a/docs/chains/agoric-chain/agoric-node.md b/docs/chains/agoric-chain/agoric-node.md index 0adeb37d..2bb44bf8 100644 --- a/docs/chains/agoric-chain/agoric-node.md +++ b/docs/chains/agoric-chain/agoric-node.md @@ -1,9 +1,9 @@ --- slug: /agoric-node -title: Running a Agoric RPC Node +title: Running an Agoric RPC Node --- -# Running a Agoric RPC Node +# Running an Agoric RPC Node ## Requirements ๐Ÿ“„ @@ -11,7 +11,7 @@ title: Running a Agoric RPC Node Users may experience issues when attempting to run instructions using versions >= 18.19.0 of `Node.js`. Node versions >=18.19 introduce a breaking change to AgoricSDK, and are not currently supported. ::: -There are notable minimum hardware requirements in order to run a Agoric RPC Nodes: +There are notable minimum hardware requirements in order to run Agoric RPC Nodes: 16 GB RAM 4-Cores x86_64 CPU diff --git a/docs/chains/avalanche-chain/avalanche-node.md b/docs/chains/avalanche-chain/avalanche-node.md index 91218b37..a70b9011 100644 --- a/docs/chains/avalanche-chain/avalanche-node.md +++ b/docs/chains/avalanche-chain/avalanche-node.md @@ -18,14 +18,14 @@ Before you start, ensure that your machine meets the following [minimum requirem ## Install AvalancheGo ๐Ÿš€ -AvalancheGo is a go implementation of an Avalanche node. This software is necessary to run a Avalanche RPC node. +AvalancheGo is a go implementation of an Avalanche node. This software is necessary to run an Avalanche RPC node. AvalancheGo can be installed automatically on a local machine using a shell bash script or manually with some commands.There are detailed guides for both [automatic installation](https://docs.avax.network/nodes/build/set-up-node-with-installer) and [manual installation](https://docs.avax.network/nodes/build/run-avalanche-node-manually) available in the Avalanche docs. ### Automated Script -To do automated install using the AvalancheGo install script, input the following into a terminal: +To do an automated installation using the AvalancheGo install script, input the following into a terminal: ```bash wget -nd -m https://raw.githubusercontent.com/ava-labs/avalanche-docs/master/scripts/avalanchego-installer.sh;\ @@ -90,4 +90,4 @@ In our current state of Testnet, there is an additional stage to pass through be ## Setup your Provider on Lava Network ๐ŸŒ‹ -Once youโ€™ve been accepted - to set up your provider on the Lava Network, you can refer to the [provider setup documentation](https://docs.lavanet.xyz/provider-setup?utm_source=running-a-avalanche-rpc-node&utm_medium=docs&utm_campaign=avalanche-pre-grant) available elsewhere in our docs. This should provide you with the necessary information to configure and operate your provider node on the Lava Network. \ No newline at end of file +Once youโ€™ve been accepted - to set up your provider on the Lava Network, you can refer to the [provider setup documentation](https://docs.lavanet.xyz/provider-setup?utm_source=running-a-avalanche-rpc-node&utm_medium=docs&utm_campaign=avalanche-pre-grant) available elsewhere in our docs. This should provide you with the necessary information to configure and operate your provider node on the Lava Network. diff --git a/docs/chains/axelar-chain/axelar-node.md b/docs/chains/axelar-chain/axelar-node.md index f02cf3a4..5b7e7adb 100644 --- a/docs/chains/axelar-chain/axelar-node.md +++ b/docs/chains/axelar-chain/axelar-node.md @@ -39,7 +39,7 @@ OS: Ubuntu 18.04 or MacOS(x86) ## Install ๐Ÿ“ฅ :::caution -Some users have reported issues with the Axelarate install script. If you encounter issues, please consider making an [issue](https://github.com/axelarnetwork/axelarate-community/issues) or trying to install manually. +Some users have reported issues with the Axelarate install script. If you encounter issues, please consider making an [issue](https://github.com/axelarnetwork/axelarate-community/issues) or trying to install it manually. ::: Clone the Axelarate-Community Repo and then run the Node Setup Script. @@ -64,4 +64,4 @@ Want to reach more developers and get more rewards as a node runner? Axelar pays ## Setup your Provider on Lava Network ๐ŸŒ‹ -Once youโ€™ve been accepted - to set up your provider on the Lava Network, you can refer to the [provider setup documentation](https://docs.lavanet.xyz/provider-setup?utm_source=running-a-axelar-rpc-node&utm_medium=docs&utm_campaign=axelar-post-grant) available elsewhere in our docs. This should provide you with the necessary information to configure and operate your provider node on the Lava Network. \ No newline at end of file +Once youโ€™ve been accepted - to set up your provider on the Lava Network, you can refer to the [provider setup documentation](https://docs.lavanet.xyz/provider-setup?utm_source=running-a-axelar-rpc-node&utm_medium=docs&utm_campaign=axelar-post-grant) available elsewhere in our docs. This should provide you with the necessary information to configure and operate your provider node on the Lava Network. diff --git a/docs/chains/base-chain/base-node.md b/docs/chains/base-chain/base-node.md index a282427e..2b983836 100644 --- a/docs/chains/base-chain/base-node.md +++ b/docs/chains/base-chain/base-node.md @@ -1,13 +1,13 @@ --- slug: /base-node -title: Running an Base RPC Node +title: Running a Base RPC Node --- # Running a Base RPC Node ## Requirements ๐Ÿ“„ -Before you start, be sure to install [Docker](https://www.docker.com/get-started). Once you have docker installed, you can continue onto the next step. +Before you start, be sure to install [Docker](https://www.docker.com/get-started). Once you have docker installed, you can continue to the next step. >16 GB RAM SSD, 2 TB free space @@ -17,7 +17,7 @@ Before you start, be sure to install [Docker](https://www.docker.com/get-started ### ๐Ÿ’ฟ Setup a L1 Full Node RPC -You need a Ethereum L1 Full Node running before you can use Base. Set `OP_NODE_L1_ETH_RPC` if you're using docker-compose. +You need an Ethereum L1 Full Node running before you can use Base. Set `OP_NODE_L1_ETH_RPC` if you're using docker-compose. ### โœจ Clone the Repo @@ -42,4 +42,4 @@ In our current state of Testnet, there is an additional stage to pass through be ## Setup your Provider on Lava Network ๐ŸŒ‹ -Once youโ€™ve been accepted - to set up your provider on the Lava Network, you can refer to the [provider setup documentation](https://docs.lavanet.xyz/provider-setup?utm_source=running-a-base-rpc-node&utm_medium=docs&utm_campaign=base-pre-grant) available elsewhere in our docs. This should provide you with the necessary information to configure and operate your provider node. \ No newline at end of file +Once youโ€™ve been accepted - to set up your provider on the Lava Network, you can refer to the [provider setup documentation](https://docs.lavanet.xyz/provider-setup?utm_source=running-a-base-rpc-node&utm_medium=docs&utm_campaign=base-pre-grant) available elsewhere in our docs. This should provide you with the necessary information to configure and operate your provider node. diff --git a/docs/chains/celestia-chain/celestia-node.md b/docs/chains/celestia-chain/celestia-node.md index baf00aa6..e9c6d174 100644 --- a/docs/chains/celestia-chain/celestia-node.md +++ b/docs/chains/celestia-chain/celestia-node.md @@ -1,9 +1,9 @@ --- slug: /celestia-node -title: Running a celestia RPC Node +title: Running a Celestia RPC Node --- -# Running a celestia RPC Node +# Running a Celestia RPC Node ## Requirements ๐Ÿ“„ @@ -17,8 +17,8 @@ title: Running a celestia RPC Node ## Setup celestia consensus and DA node -Follow celestia docs for instructions on how to setup and run the nodes: -Data availabillity light node https://docs.celestia.org/nodes/light-node +Follow Celestia docs for instructions on how to setup and run the nodes: +Data availability light node https://docs.celestia.org/nodes/light-node Consensus node https://docs.celestia.org/nodes/full-consensus-node Important note: @@ -39,7 +39,7 @@ To set up your provider on the Lava Network, you can refer to the [provider setu Celestia providers must supply endpoint for both consensus and DA node: - consensus node: rest, tendermint, grpc (this is the same as every other cosmos node) -- DA node: jsonrpc (when running the light DA node the defualt port will be 26658) +- DA node: jsonrpc (when running the light DA node the default port will be 26658) example for provider configuration file @@ -74,4 +74,4 @@ endpoints: address: 0.0.0.0:2221 node-urls: - url: http://127.0.0.1:1317 -``` \ No newline at end of file +``` diff --git a/docs/chains/celo-chain/celo-node.md b/docs/chains/celo-chain/celo-node.md index b85fc9cf..7e9a7c87 100644 --- a/docs/chains/celo-chain/celo-node.md +++ b/docs/chains/celo-chain/celo-node.md @@ -1,18 +1,18 @@ --- slug: /celo-node -title: Running an Celo RPC Node +title: Running a Celo RPC Node --- # Running a Celo RPC Node ## Requirements ๐Ÿ“„ -Before you start, be sure to install [Docker](https://www.docker.com/get-started). Once you have docker installed, you can continue onto the next step. +Before you start, be sure to install [Docker](https://www.docker.com/get-started). Once you have docker installed, you can continue to the next step. ## Install Celo Docker Image ๐Ÿ“ฅ -Celo's node is built from a Docker image pulled using Docker CLI. This software is necessary to run a Celo RPC node. To get started, input the following in terminal: +Celo's node is built from a Docker image pulled using Docker CLI. This software is necessary to run a Celo RPC node. To get started, input the following in the terminal: ```bash export CELO_IMAGE=us.gcr.io/celo-org/geth:mainnet @@ -45,4 +45,4 @@ In our current state of Testnet, there is an additional stage to pass through be ## Setup your Provider on Lava Network ๐ŸŒ‹ -Once youโ€™ve been accepted - to set up your provider on the Lava Network, you can refer to the [provider setup documentation](https://docs.lavanet.xyz/provider-setup?utm_source=running-a-celo-rpc-node&utm_medium=docs&utm_campaign=celo-pre-grant) available elsewhere in our docs. This should provide you with the necessary information to configure and operate your provider node. \ No newline at end of file +Once youโ€™ve been accepted - to set up your provider on the Lava Network, you can refer to the [provider setup documentation](https://docs.lavanet.xyz/provider-setup?utm_source=running-a-celo-rpc-node&utm_medium=docs&utm_campaign=celo-pre-grant) available elsewhere in our docs. This should provide you with the necessary information to configure and operate your provider node. diff --git a/docs/chains/ethereum-chain/ethereum-node.md b/docs/chains/ethereum-chain/ethereum-node.md index f1ac6e23..b0c3a6a9 100644 --- a/docs/chains/ethereum-chain/ethereum-node.md +++ b/docs/chains/ethereum-chain/ethereum-node.md @@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem'; ## Requirements ๐Ÿ“„ -Ethereum nodes have some basic hardware requirements that must be met in order to proceed with the install process: +Ethereum nodes have some basic hardware requirements that must be met in order to proceed with the installation process: @@ -50,4 +50,4 @@ In our current state of Testnet, there is an additional stage to pass through be ## Setup your Provider on Lava Network ๐ŸŒ‹ -Once youโ€™ve been accepted - to set up your provider on the Lava Network, you can refer to the [provider setup documentation](https://docs.lavanet.xyz/provider-setup?utm_source=running-a-ethereum-rpc-node&utm_medium=docs&utm_campaign=ethereum-pre-grant) available elsewhere in our docs. This should provide you with the necessary information to configure and operate your provider node. \ No newline at end of file +Once youโ€™ve been accepted - to set up your provider on the Lava Network, you can refer to the [provider setup documentation](https://docs.lavanet.xyz/provider-setup?utm_source=running-a-ethereum-rpc-node&utm_medium=docs&utm_campaign=ethereum-pre-grant) available elsewhere in our docs. This should provide you with the necessary information to configure and operate your provider node. diff --git a/docs/chains/filecoin-chain/filecoin-node.md b/docs/chains/filecoin-chain/filecoin-node.md index 120e5509..4524f46d 100644 --- a/docs/chains/filecoin-chain/filecoin-node.md +++ b/docs/chains/filecoin-chain/filecoin-node.md @@ -23,7 +23,7 @@ The list above is specific to Debian/Ubuntu-based OSes. For a different configur ## Install Lotus Filecoin Node ๐Ÿš€ -Filecoin is a divers ecosystem with different node implementations. Each node implementation has different ways to generate and manage authentication tokens. This guide uses [Lotus Filecoin](https://lotus.filecoin.io/lotus/get-started/what-is-lotus/), which is the reference node implementation for the Filecoin network. +Filecoin is a diverse ecosystem with different node implementations. Each node implementation has different ways to generate and manage authentication tokens. This guide uses [Lotus Filecoin](https://lotus.filecoin.io/lotus/get-started/what-is-lotus/), which is the reference node implementation for the Filecoin network. ### Get Lotus To get started, input the following into the terminal: @@ -47,7 +47,7 @@ make clean calibnet # Calibration with min 32GiB sectors ``` ### Compile Lotus -Finalize the install by inputting `sudo make install` in the terminal. +Finalize the installation by inputting `sudo make install` in the terminal. You can run `lotus --version` to ensure that this process completed successfully. :::tip @@ -99,4 +99,4 @@ In our current state of Testnet, there is an additional stage to pass through be ## Setup your Provider on Lava Network ๐ŸŒ‹ -Once youโ€™ve been accepted - to set up your provider on the Lava Network, you can refer to the [provider setup documentation](https://docs.lavanet.xyz/provider-setup?utm_source=running-a-filecoin-rpc-node&utm_medium=docs&utm_campaign=filecoin-pre-grant) available elsewhere in our docs. This should provide you with the necessary information to configure and operate your provider node. \ No newline at end of file +Once youโ€™ve been accepted - to set up your provider on the Lava Network, you can refer to the [provider setup documentation](https://docs.lavanet.xyz/provider-setup?utm_source=running-a-filecoin-rpc-node&utm_medium=docs&utm_campaign=filecoin-pre-grant) available elsewhere in our docs. This should provide you with the necessary information to configure and operate your provider node. diff --git a/docs/chains/koii-chain/koii-node.md b/docs/chains/koii-chain/koii-node.md index e963dc29..50328101 100644 --- a/docs/chains/koii-chain/koii-node.md +++ b/docs/chains/koii-chain/koii-node.md @@ -78,7 +78,7 @@ koii-validator \ ### ๐Ÿงช Test Your Endpoints -There maybe additional configurations necessary to complete your setup. +There may be additional configurations necessary to complete your setup. You should consult the [Validator setup guide](https://docs.koii.network/run-a-node/k2-validators/validator-setup) for Koii and the [RPC Setup Guide](https://docs.solana.com/validator/get-started/setup-an-rpc-node) for Solana to ensure you've covered all necessary steps. diff --git a/docs/chains/near-chain/near-node.md b/docs/chains/near-chain/near-node.md index 575d62de..c53ac176 100644 --- a/docs/chains/near-chain/near-node.md +++ b/docs/chains/near-chain/near-node.md @@ -68,7 +68,7 @@ make release ``` :::caution -`make release` will cause the `nearcore` to compile. Compilation is a time-intensive process and can take ~30 minutes or longer on recommmended hardware. +`make release` will cause the `nearcore` to compile. Compilation is a time-intensive process and can take ~30 minutes or longer on recommended hardware. ::: ### Configure the release folder diff --git a/docs/developer/sdk/sdk-backend.md b/docs/developer/sdk/sdk-backend.md index aa57e3ae..28aeb875 100644 --- a/docs/developer/sdk/sdk-backend.md +++ b/docs/developer/sdk/sdk-backend.md @@ -18,7 +18,7 @@ title: Backend Use ๐Ÿ›ก๏ธ ## โ†ช๏ธ Recommended Flow -Although you can subscribe your private key from the commandline, the easiest way to get started is through Lava's Gateway. +Although you can subscribe your private key from the command line, the easiest way to get started is through Lava's Gateway. 1. Sign up to the Gateway. ๐Ÿ‘‰๐Ÿฟ[Register now](https://gateway.lavanet.xyz/?utm_source=sdk-backend-page&utm_medium=docs&utm_campaign=docs-to-gateway) if you havenโ€™t already! 2. Create a Project and Select your APIs! @@ -45,6 +45,6 @@ If you already have `lavad` installed - you can easily generate a lava address b - If you have an address that exists and no longer remember its private key, you can alwasy use `lavad keys export --unarmored-hex --unsafe` to see your privatekey printed as a string. Do not share the output with anyone! + If you have an address that exists and no longer remembers its private key, you can always use `lavad keys export --unarmored-hex --unsafe` to see your privatekey printed as a string. Do not share the output with anyone! -๐Ÿš€ Your private-key, public-key pair can be used for backend development provided you have a subscription! \ No newline at end of file +๐Ÿš€ Your private-key, public-key pair can be used for backend development provided you have a subscription! diff --git a/docs/intro/key-terms.md b/docs/intro/key-terms.md index 4439336c..993b941b 100644 --- a/docs/intro/key-terms.md +++ b/docs/intro/key-terms.md @@ -121,7 +121,7 @@ title: ๐Ÿ“ Key Terms
Badges - Special permissions required for end-users to send relays when connecting to the Lava Network from frontend applications, generated by Dapp owners using a subscription private key. + Special permissions are required for end-users to send relays when connecting to the Lava Network from frontend applications, generated by Dapp owners using a subscription private key.
diff --git a/docs/intro/specs/spec-guide.md b/docs/intro/specs/spec-guide.md index 6a79232b..037077f5 100644 --- a/docs/intro/specs/spec-guide.md +++ b/docs/intro/specs/spec-guide.md @@ -134,7 +134,7 @@ This field defines the number of blocks that should be considered safe from chai
`blocks_in_finalization_proof` -This field defines the number of blocks that should be found in a finality proof; this will vary from chain to chain. Look to other similarly architected specs fo suggested values. +This field defines the number of blocks that should be found in a finality proof; this will vary from chain to chain. Look to other similarly architected specs for suggested values.
@@ -152,7 +152,7 @@ This is the maximum amount of blocks that can pass before the data a provider se
`shares` -The default is `1`. This is a bonus multiplier for rewards at the end of each month. There should be no reason to change this unless diected otherwise. +The default is `1`. This is a bonus multiplier for rewards at the end of each month. There should be no reason to change this unless directed otherwise.
diff --git a/docs/lava-blockchain/hardware-requirements.md b/docs/lava-blockchain/hardware-requirements.md index 591c5ee8..6c36a70a 100644 --- a/docs/lava-blockchain/hardware-requirements.md +++ b/docs/lava-blockchain/hardware-requirements.md @@ -9,7 +9,7 @@ title: Hardware requirements - Shared compute instance (e.g. AWS EC2 instance) - Your personal station -**Docker** container are available at [Lava's repository on GitHub](https://github.com/lavanet/lava/tree/main/docker) +**Docker** containers are available at [Lava's repository on GitHub](https://github.com/lavanet/lava/tree/main/docker) ## Hardware requirements diff --git a/docs/provider/lavavisor/lavavisor-wrap.md b/docs/provider/lavavisor/lavavisor-wrap.md index e08cd04e..3c4f8b85 100644 --- a/docs/provider/lavavisor/lavavisor-wrap.md +++ b/docs/provider/lavavisor/lavavisor-wrap.md @@ -31,7 +31,7 @@ Please make sure you are using the right `chainId` this document was written dur ### > `lavavisor init` LavaVisor `init` command initializes the environment for LavaVisor. It is generally the first command run when using LavaVisor. -If you're using [`lavavisor pod`](#-lavavisor-pod) this command is unnecesary and can be skipped. +If you're using [`lavavisor pod`](#-lavavisor-pod) this command is unnecessary and can be skipped. **Optional Flags:** @@ -98,4 +98,4 @@ Lavavisor doesn't check if the password is correct; it will try to use it when s ```bash lavavisor wrap --cmd 'lavap rpcprovider ./config/my_rpcprovider_config.yml --geolocation 1 --log_level debug --from prod_client --chain-id lava-testnet-2 --keyring-backend os --node ""' --auto-download --node "" --chain-id lava-testnet-2 --enter-keyring-password -``` \ No newline at end of file +``` diff --git a/docs/provider/provider-improve-service.md b/docs/provider/provider-improve-service.md index e120d1f6..8692b101 100644 --- a/docs/provider/provider-improve-service.md +++ b/docs/provider/provider-improve-service.md @@ -222,7 +222,7 @@ lavap test rpcprovider ${PUBLIC_ADDRESS} ### Errors โŒ these mean the provider service connection was solid but all relays turned to be errors, might be caused by the following: -* disabled chain - the provider doesnt have access to the node, or a verification does not pass, and the chain is disabled +* disabled chain - the provider doesn't have access to the node, or verification does not pass, and the chain is disabled * unexpected errors * timeouts diff --git a/docs/provider/provider-setup.md b/docs/provider/provider-setup.md index 0367e5fe..4f9077ca 100644 --- a/docs/provider/provider-setup.md +++ b/docs/provider/provider-setup.md @@ -33,7 +33,7 @@ In this guide, we'll create a configuration file that includes multiple chains ( ## Step 1: Setup TLS As part of good security practice, Lava protocol communicates with end-to-end encryption between providers and consumers of RPC. This requires some additional configuration steps on a provider, namely, the setup of TLS certification with a certification authority. -โ—โ— If you already use a **TLS Certificate signed by a Certifiying Authority**, you can continue onto step 2. Otherwise, you may want to check out our guide on [setting up TLS for Lava Providers](/provider-tls). +โ—โ— If you already use a **TLS Certificate signed by a Certifying Authority**, you can continue onto step 2. Otherwise, you may want to check out our guide on [setting up TLS for Lava Providers](/provider-tls). ## Step 2: Run RPCProvider process diff --git a/docs/validator/validator-auto.md b/docs/validator/validator-auto.md index 316d9e8c..535c1d92 100644 --- a/docs/validator/validator-auto.md +++ b/docs/validator/validator-auto.md @@ -29,7 +29,7 @@ Running the script will: 1. Install `lavad` (using Cosmovisor) 2. Join the testnet -3. Sync to latest block +3. Sync to the latest block ```bash curl -s --location \ @@ -82,4 +82,4 @@ Get your account funded through [the faucet](faucet) # ./validator_setup.sh -e production -a run_validator -u my_user ``` -Expect to see the voting power of your node to be > 0, this will be visible in the output of the script \ No newline at end of file +Expect to see the voting power of your node to be > 0, this will be visible in the output of the script diff --git a/docs/validator/validator.md b/docs/validator/validator.md index 06479d2a..21b1d708 100644 --- a/docs/validator/validator.md +++ b/docs/validator/validator.md @@ -20,7 +20,7 @@ Validators earn LAVA from the creation of new blocks and the transaction fees, a _Note_: This does not cover Delegating LAVA to validators -:::tip Start a validators +:::tip Start a validator [](/validator-manual) -::: \ No newline at end of file +:::