A missing in validator monioring setting up page
https://docs.edgewa.re/understanding-edgeware/staking/validation/setting-up-monitoring
before run test nodeup "node index.js", should run "npm install"

We haven't verified the edgeware-cli in a while so we ought to also have the flow most people use on the docs.

https://docs.edgewa.re/quickstart/set-up-a-validator#onboarding

Can someone please review pull request #74?

The first two images are broken at https://docs.edgewa.re/quickstart/create-an-edgeware-identity

https://twitter.com/HeyEdgeware/status/1322273898185003008

Do we have access to the token supply spreadsheet?
@dillchen

• empty - https://docs.edgewa.re/edgeware-runtime/economics/token-supply-chart
• yield 404 - https://edgeware-supply.now.sh/

I've just created a PR fixing (hopefully) a number of broken github links. There are also the following outstanding which I'm struggling to resolve:

• /docs/quickstart/send-a-transaction.md
  Link to testnet is broken, but I'm not sure where it should point.
  /docs/other-resources/networks.md and docs/other-resources/tools-and-ecosystem.md both seem possible, but not quite right.

• /docs/contribute-and-engage/develop/edgeware-smart-contracts/README.md
  WebAssembly (Wasm) link was broken. Updated (in the pending PR) to what I think is the correct page, but it's empty.

• image links on docs/roadmap.md are broken and I can't work out where they should point.

some typo in text/scripts written into /ete/monit/monitrc, here is correct context"
{
echo 'check process mmonit with pidfile 'pwd'/monit/logs/mmonit.pid'
echo ' start program = "'pwd'/monit/bin/mmonit"'
echo ' stop program = "'pwd'/monit/bin/mmonit stop"'
echo 'set httpd port 2812 and use address localhost'
echo ' allow localhost'
} > /etc/monit/monitrc

Summary.md is what Gitbooks uses to build the pretty frontend

Firstly, this is not a quick start concept.
Secondly, this is poorly communicated and formatted.
Thirdly, it links to a notion which links to a polkadot link.

https://docs.edgewa.re/quickstart/create-an-edgeware-identity#add-an-address-to-an-ens-domain

Add entry into gitbook and populate with results from running the simple tasks of deploying tasks on Edgeware/moonbeam like chains.

The docs for Edgeware list 2 different groups of testnet nodes. This is not very clear which ones are current (although I suspect berlinX.edgewa.re are current).

Please could you update/ clarify to reflect the most recent values?

1. On this page: https://docs.edgewa.re/understanding-edgeware/staking/validation/frequently-used-commands

Public nodes
Commonwealth Labs maintains several public nodes for testnet v0.8:
testnet1.edgewa.re
testnet2.edgewa.re
testnet3.edgewa.re
testnet4.edgewa.re
testnet5.edgewa.re
testnet6.edgewa.re
Syntax:
wss://testnet1.edgewa.re
or (if wss: fails)
ws://testnet1.edgewa.re:9944

2. On this page: https://docs.edgewa.re/understanding-edgeware/networks

wss://berlin1.edgewa.re
wss://berlin2.edgewa.re
wss://berlin3.edgewa.re
wss://berlin4.edgewa.re
wss://berlin5.edgewa.re
wss://berlin6.edgewa.re
wss://berlin7.edgewa.re
wss://berlin8.edgewa.re
wss://berlin9.edgewa.re
wss://berlin10.edgewa.re

https://docs.edgewa.re/quickstart/set-up-a-validator#examples-of-all-the-commands-are-below

https://docs.edgewa.re/quickstart/create-an-edgeware-identity#adding-identities-using-polkadot-js

To reproduce the issue either visit : https://substrate.dev/docs/en/next/conceptual/runtime/contracts/contracts_module or click the SRML Module link here : https://docs.edgewa.re/understanding-edgeware/develop/smart-contracts

We should be directing users to use rotateKeys BEFORE they execute the flow for onboarding. Otherwise, where do they get the session keys from? This is not clear.

https://docs.edgewa.re/quickstart/set-up-a-validator#onboarding