Update Prod with Latest Changes (#2376)

* Bump @octokit/rest from 18.6.7 to 18.6.8 (#2369)

Bumps [@octokit/rest](https://github.com/octokit/rest.js) from 18.6.7 to 18.6.8.
- [Release notes](https://github.com/octokit/rest.js/releases)
- [Commits](octokit/rest.js@v18.6.7...v18.6.8)

---
updated-dependencies:
- dependency-name: "@octokit/rest"
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump katex from 0.13.11 to 0.13.12 (#2370)

Bumps [katex](https://github.com/KaTeX/KaTeX) from 0.13.11 to 0.13.12.
- [Release notes](https://github.com/KaTeX/KaTeX/releases)
- [Changelog](https://github.com/KaTeX/KaTeX/blob/master/CHANGELOG.md)
- [Commits](KaTeX/KaTeX@v0.13.11...v0.13.12)

---
updated-dependencies:
- dependency-name: katex
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* update dotscanner listing to include Kusama and a tracking attribute (#2372)

* Update learn-accounts.md (#2358)

* Update learn-accounts.md

Added placeholder for content on Soft vs Hard Derivation paths

* Update learn-accounts.md

Added preliminary information. Might benefit from an infographic or a video explaining derivation paths. Please review and suggest content edits/updates

* Update docs/learn-accounts.md

Co-authored-by: Bill Laboon <[email protected]>

* Update docs/learn-accounts.md

Co-authored-by: Bill Laboon <[email protected]>

* Update docs/learn-accounts.md

Co-authored-by: Bill Laboon <[email protected]>

* Update docs/learn-accounts.md

Co-authored-by: Bill Laboon <[email protected]>

* Update docs/learn-accounts.md

Co-authored-by: Bill Laboon <[email protected]>

Co-authored-by: Bill Laboon <[email protected]>

* Update sidebars.js (#2374)

Correcting Typo

* Modify Secure Validator Setup (#2361)

* umodify secure validator setup

* update links + edits

* edits

* edits

* Update maintain-guides-how-to-use-polkadot-validator-setup.md

* Add Conditional Rendering for chain flag (#2367)

* add conditional rendering for chain flag

* Update maintain-sync.md

* Update Pages to address Stales (#2371)

* resolves #2321

* resolves #1844

* resolves #1733

* update simple payouts and prettier (#2363)

Co-authored-by: Danny Salman <[email protected]>

* Bump @octokit/rest from 18.6.8 to 18.7.0 (#2378)

Bumps [@octokit/rest](https://github.com/octokit/rest.js) from 18.6.8 to 18.7.0.
- [Release notes](https://github.com/octokit/rest.js/releases)
- [Commits](octokit/rest.js@v18.6.8...v18.7.0)

---
updated-dependencies:
- dependency-name: "@octokit/rest"
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump katex from 0.13.12 to 0.13.13 (#2377)

Bumps [katex](https://github.com/KaTeX/KaTeX) from 0.13.12 to 0.13.13.
- [Release notes](https://github.com/KaTeX/KaTeX/releases)
- [Changelog](https://github.com/KaTeX/KaTeX/blob/master/CHANGELOG.md)
- [Commits](KaTeX/KaTeX@v0.13.12...v0.13.13)

---
updated-dependencies:
- dependency-name: katex
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Update maintain-guides-how-to-chill.md (#2375)

* Update maintain-guides-how-to-chill.md

Summarize the contents in paritytech/substrate#8920

#2173

* Added content on Chill other

* Update maintain-guides-how-to-chill.md

Added suggestions from Danny

* Update maintain-guides-how-to-chill.md

minor correction

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Dee Evans <[email protected]>
Co-authored-by: Radha <[email protected]>
Co-authored-by: Bill Laboon <[email protected]>

docs/build-cumulus.md

@@ -3,7 +3,9 @@ id: build-cumulus
 title: Cumulus
 sidebar_label: Cumulus
 ---
+
 <!-- page being updated -->
+
 > "Cumulus clouds are shaped sort of like dots; together they form a system that is intricate,
 > beautiful and functional."
 

docs/build-hackathon.md

@@ -5,7 +5,8 @@ sidebar_label: Hackathon
 ---
 
 As one of our objectives at Web3 Foundation is promoting the [Web3 technology stack][], we would
-like to support any individual or team who wants to organize a hackathon that encourages more developers to understand Polkadot and Substrate in your region or online.
+like to support any individual or team who wants to organize a hackathon that encourages more
+developers to understand Polkadot and Substrate in your region or online.
 
 We are not only providing technical resources for you, but we can have someone from our team give a
 hands-on workshop/presentation about the technology to help participants get started hacking on it
@@ -35,7 +36,9 @@ more quickly.
 ## How do hackathons differ from workshops?
 
 A hackathon is aimed at participants who want to deliver their prototype and demonstrate their ideas
-to reality in a short period (few hours - one day). Workshops are aimed at familiarizing developers with the underlying knowledge and tooling about the resources currently available for certain technologies and how they can make use of it.
+to reality in a short period (few hours - one day). Workshops are aimed at familiarizing developers
+with the underlying knowledge and tooling about the resources currently available for certain
+technologies and how they can make use of it.
 
 ## How can you run a hackathon in your city?
 

docs/build-node-management.md

@@ -107,8 +107,8 @@ Web3 Foundation maintains [Polkadot Deployer](https://github.com/w3f/polkadot-de
 allows you to create local or remote cloud deployments of Polkadot nodes. See the README for
 instructions.
 
-Validators, see the [secure setup guide](maintain-guides-how-to-use-polkadot-validator.md) for
-information specific to deploying validator nodes.
+Validators, see the [validator setup guide](maintain-guides-how-to-use-polkadot-validator-setup.md) 
+for information specific to deploying validator nodes.
 
 ## Monitoring and Telemetry
 

docs/build-parachains-rococo.md

@@ -5,23 +5,27 @@ sidebar_label: Rococo Parachain Test Network
 ---
 
 [Rococo](https://github.com/paritytech/cumulus#rococo-crown) is a Polkadot testnet built for testing
-parachains. Rococo utilizes Cumulus and HRMP (Horizontal Relay-routed Message Passing) in order to
-send transfers and messages between parachains and the Relay Chain. Every message is sent to the
-Relay Chain, then from the Relay Chain to the desired parachain. Rococo currently runs four test
-system parachains (Statemint, Tick, Trick, and Track), as well as several externally developed
+parachains. Unlike other testnets, Rococo allows parachains to interact with the [Relay Chain](glossary.md##relay-chain) 
+rather than running in isolation. Rococo utilizes [Cumulus](build-cumulus.md) and HRMP (Horizontal Relay-routed Message 
+Passing), which is also known as [XCMP-lite](learn-crosschain.md##xcmp-lite(hrmp)), in order to send transfers and messages 
+between parachains and the Relay Chain.
+
+Messages are sent to the Relay Chain -> then from the Relay Chain to the desired parachain. Rococo 
+currently runs three test system parachains: Tick, Trick, and Track, as well as several externally developed 
 parachains.
 
 ## What Parachains are on Rococo Now?
 
-You can see the list of included parachains
-[here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-rpc.polkadot.io#/parachains). A list of
-proposed parachains is available
-[here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-rpc.polkadot.io#/parachains/proposals).
+You can view the list of included parachains on
+[Polkadot-JS Apps](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-rpc.polkadot.io#/parachains), 
+and a list of
+[proposed parachains](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-rpc.polkadot.io#/parachains/proposals).
 
 ## Obtaining ROC
 
-ROC are available in the [Rococo Faucet](https://app.element.io/#/room/#rococo-faucet:matrix.org)
-channel on Matrix. To receive ROC tokens, use the command:
+ROC is the native testnet token on the Rococo testnet, and are available in the 
+[Rococo Faucet](https://app.element.io/#/room/#rococo-faucet:matrix.org) channel on Matrix. 
+To receive ROC tokens, send the following command on the channel:
 
 ```
 !drip YOUR_ROCOCO_ADDRESS
@@ -34,14 +38,15 @@ parachains.
 
 If you are interested in running and launching your own parathread or parachain, Parity Technologies
 has created a [cumulus parachain workshop](https://substrate.dev/cumulus-workshop/) to show you how.
+
 Get stuck or need support along the way? Join the
 [Rococo matrix chat channel](https://matrix.to/#/#rococo:matrix.parity.io) and connect with other
 builders there.
 
 ## How to connect to a Parachain
 
 If you would like to connect to a parachain via [Polkadot-JS Apps](https://polkadot.js.org/apps/),
-you may do so by clicking on the network selection at the top left hand corner of the navigation and
+you may do so by clicking on the network selection at the top-left hand corner of the navigation and
 selecting any parachain of choice. For the purpose of these following examples, we will be using the
 Rococo testnet "Custom Node" underneath "Development", following the
 [parachain workshop](https://substrate.dev/cumulus-workshop/).
@@ -85,11 +90,11 @@ another parachain.
 
 ### Lateral Transfers
 
-This type of transfer is only possible with at least two different registered parachains. In true
+Lateral transfers are only possible with at least two different registered parachains. In true
 XCMP, lateral transfers would allow for messages to be sent directly from one parachain to another.
 However, this is not yet implemented, so the Relay Chain is helping us deliver messages for the time
 being. Lateral transfers work through the depository model, which means that in order to transfer
-tokens from chain 200 to chain 300, there must already be tokens owned by chain 200 deposited on
+tokens from chain 200 to chain 300, tokens must already be owned by chain 200 deposited on
 chain 300. Lateral transfers are called HRMP, Horizontal Relay-Chain Message Passing.
 
 Before we can actually send funds from one parachain to another, we must ensure that the chain's

docs/build-pdk.md

@@ -3,7 +3,9 @@ id: build-pdk
 title: Parachain Development Kits (PDKs)
 sidebar_label: Parachain Development Kits (PDKs)
 ---
+
 <!-- process of being updated -->
+
 Parachain development kits (PDKs) are a set of tools that make it easy for developers to create
 Polkadot compatible [parachains](learn-parachains.md).
 

docs/build-protocol-info.md

@@ -5,6 +5,7 @@ sidebar_label: Polkadot Protocol
 ---
 
 <!-- page in the process of being updated -->
+
 This page serves as a high-level introduction to the Polkadot protocol with terminology that may be
 specific to Polkadot, notable differences to other chains that you may have worked with, and
 practical information for dealing with the chain.
@@ -224,8 +225,8 @@ transaction data using the
 
 ## Runtime Upgrades
 
-Polkadot allows [runtime upgrades](learn-runtime-upgrades.md) without a hard fork. The runtime 
-is a Wasm binary stored on-chain and can be updated using your chain’s governance mechanism.
+Polkadot allows [runtime upgrades](learn-runtime-upgrades.md) without a hard fork. The runtime is a
+Wasm binary stored on-chain and can be updated using your chain’s governance mechanism.
 
 ## Smart Contracts
 

docs/build-tools-index.md

@@ -3,7 +3,9 @@ id: build-tools-index
 title: Tool Index
 sidebar_label: Tool Index
 ---
+
 <!-- Page being reformatted -->
+
 Here we provide a list of tools available for your development needs. They are sorted by context. If
 you're actively maintaining a tool that might be useful to other Polkadot, Kusama or Substrate
 developers, feel free to [add it in](contributing).
@@ -17,7 +19,7 @@ developers, feel free to [add it in](contributing).
   chains. [Repo](https://github.com/polkascan/polkascan-os).
 - [Subscan](https://subscan.io) - Blockchain explorer for Substrate chains.
   [Repo](https://github.com/itering/subscan-essentials).
-- [DotScanner](https://dotscanner.com) - Polkadot Blockchain explorer.
+- [DotScanner](https://dotscanner.com?utm_source=polkadot_wiki) - Polkadot & Kusama Blockchain explorer.
 
 ## Wallets
 

docs/build-transaction-construction.md

@@ -3,7 +3,9 @@ id: build-transaction-construction
 title: Transaction Construction and Signing
 sidebar_label: Transaction Construction
 ---
+
 <!-- no updates -->
+
 This page will discuss the transaction format in Polkadot and how to create, sign, and broadcast
 transactions. Like the other pages in this guide, this page demonstrates some of the available
 tools. **Always refer to each tool's documentation when integrating.**

docs/claims.md

@@ -51,7 +51,9 @@ patches.
 You will need a Polkadot account to claim your DOT. Please follow the instructions on the [account
 generation][] page for generating a new Polkadot account.
 
-You can use the [claims guide](https://claims.polkadot.network/) to claim DOT that were purchased in the form of DOT Allocation Indicators on Ethereum before June 30, 2020. These steps are broken down in the remaining sections of this page.
+You can use the [claims guide](https://claims.polkadot.network/) to claim DOT that were purchased in
+the form of DOT Allocation Indicators on Ethereum before June 30, 2020. These steps are broken down
+in the remaining sections of this page.
 
 #### Claiming your DOT with MyCrypto
 

docs/contributing.md

@@ -7,33 +7,35 @@ sidebar_label: Contributing
 The wiki was started and is maintained by the Web3 Foundation. It is an open source project and aims
 to be the most extensive resource of knowledge on Polkadot and the Polkadot ecosystem. A large part
 of the material currently focuses on Polkadot directly but it is not opposed to covering
-informational material for community projects. 
+informational material for community projects.
 
 **Please do not try to pull request any marketing material as this will be rejected.**
 
-Nonetheless, pull requests, discussions, and contributions from the community are encouraged. 
-Active community members who demonstrate a record of good contributions may be given write access 
-to the repository.
+Nonetheless, pull requests, discussions, and contributions from the community are encouraged. Active
+community members who demonstrate a record of good contributions may be given write access to the
+repository.
 
 Otherwise, Web3 Foundation holds the administrative position and final say on the content that is
 included. Specifically, the Technical Education team at the foundation are most directly involved.
 
-> Check out the [How to Contribute to the Polkadot Wiki](https://www.youtube.com/watch?v=6i55KOcy7B0)
-> video for steps on contributions.
+> Check out the
+> [How to Contribute to the Polkadot Wiki](https://www.youtube.com/watch?v=6i55KOcy7B0) video for
+> steps on contributions.
 
 ## How to Contribute
 
-You can contribute to the wiki on the [w3f/polkadot-wiki GitHub repository](https://github.com/w3f/polkadot-wiki). 
-Every page is a [MarkDown](https://guides.github.com/features/mastering-markdown/) file, which is an
-easy to learn syntax extension to plain text that makes creating links, rendering images, 
-and nice-looking formatting simple. 
+You can contribute to the wiki on the
+[w3f/polkadot-wiki GitHub repository](https://github.com/w3f/polkadot-wiki). Every page is a
+[MarkDown](https://guides.github.com/features/mastering-markdown/) file, which is an easy to learn
+syntax extension to plain text that makes creating links, rendering images, and nice-looking
+formatting simple.
 
-Each page has an "Edit this page" link at the bottom of the content. By clicking it you
-are taken to the GitHub sign-in page, where you can either log in or create an account.
+Each page has an "Edit this page" link at the bottom of the content. By clicking it you are taken to
+the GitHub sign-in page, where you can either log in or create an account.
 
-Once logged in, you'll be taken to the GitHub built-in text editor where you can make your edits 
-directly. When you've completed your changes, you can add any specific details on what was changed 
-and commit to a **new branch** to create a new Pull Request to the repository. From there one of the 
+Once logged in, you'll be taken to the GitHub built-in text editor where you can make your edits
+directly. When you've completed your changes, you can add any specific details on what was changed
+and commit to a **new branch** to create a new Pull Request to the repository. From there one of the
 maintainers will review your changes, and either merge them or request changes.
 
 ![](assets/contributing.png) ![](assets/creating-pull-request.png)
@@ -66,4 +68,5 @@ There are a few basic ground-rules for contributors:
 
 ## Heritage
 
-This document is based on the [Level contribution guidelines](https://github.com/Level/community/blob/master/CONTRIBUTING.md).
+This document is based on the
+[Level contribution guidelines](https://github.com/Level/community/blob/master/CONTRIBUTING.md).

docs/ens.md

@@ -4,14 +4,13 @@ title: Adding accounts to an ENS domain
 sidebar_label: Using ENS with DOT/KSM accounts
 ---
 
-ENS (Ethereum Name Service) is a distributed and open system of smart contracts on the 
-Ethereum blockchain which allows users to claim domain names like `bruno.eth`. 
-
-The ENS is a domain that is equivalent to a DNS (Domain Name System) domain. 
-Instead, it offers a decentralized and secure way to translate text via smart contracts.
-Supporting wallets can then allow senders to input ENS domains instead of long and unwieldy 
-addresses. This prevents phishing, fraud, typos, and adds a
-layer of usability on top of the regular wallet user experience.
+ENS (Ethereum Name Service) is a distributed and open system of smart contracts on the Ethereum
+blockchain which allows users to claim domain names like `bruno.eth`.
+
+The ENS is a domain that is equivalent to a DNS (Domain Name System) domain. Instead, it offers a
+decentralized and secure way to translate text via smart contracts. Supporting wallets can then
+allow senders to input ENS domains instead of long and unwieldy addresses. This prevents phishing,
+fraud, typos, and adds a layer of usability on top of the regular wallet user experience.
 
 > Note: You will need an ENS name and an Ethereum account with some ether in it to follow along with
 > this guide. To register an ENS name, visit the [ENS App](https://app.ens.domains) or any number of

docs/kusama-adverserial-cheatsheet.md

@@ -3,7 +3,9 @@ id: kusama-adversarial-cheatsheet
 title: Adversarial Cheatsheet
 sidebar_label: Adversarial Cheatsheet
 ---
+
 <!-- no updates -->
+
 Expect things to break on Kusama. To help you break some things, take a look at the following threat
 model.
 

docs/kusama-coc.md

@@ -38,8 +38,8 @@ questions.
 - Knowingly distributing false information about Kusama or other projects.
 - Harassing other individuals or projects.
 
-That said, please note that Kusama is an edgy and meme-friendly network, and community member actions
-shouldn't be taken too seriously - try to assume jest before malice.
+That said, please note that Kusama is an edgy and meme-friendly network, and community member
+actions shouldn't be taken too seriously - try to assume jest before malice.
 
 ## What To Do If You Witness or Are Subject To Unacceptable Behavior
 

docs/kusama-community.md

@@ -3,7 +3,9 @@ id: kusama-community
 title: Kusama Community
 sidebar_label: Community
 ---
+
 <!-- no changes -->
+
 The following is a list of official chats, forums, and social channels for the Kusama community.
 Keep in mind that no admin or moderator will ever DM you for any reason whatsoever without prior
 public contact and anyone doing so is likely trying to scam you.

docs/kusama-endpoints.md

@@ -8,7 +8,8 @@ When interacting with the [Kusama network][] via [Polkadot-JS Apps][] or other U
 methods, you'd ideally be running your own node ([text guide](maintain-sync.md),
 [video guide](https://www.youtube.com/watch?v=31DdfcxbAVs)). Granted, that's not something everyone
 wants to do, so convenience trumps ideals in most cases. To facilitate this convenience, Kusama has
-several public endpoints you can use for your apps.
+several public endpoints you can use for your apps provided by infrastructure and
+API services providers in the ecosystem.
 
 ## Parity Archive Node
 
@@ -30,27 +31,3 @@ or in Polkadot-JS Apps by clicking the top-left corner of the screen and selecti
 option:
 
 <img src={require('./assets/endpoints/kusama_endpoint_parity.png').default} width="40%" />
-
-## Web3 Foundation Archive Node
-
-The Web3 Foundation maintains an archive node at endpoint `wss://cc3-5.kusama.network/`.
-
-To connect to this node, use the endpoint in your JavaScript apps like so:
-
-```javascript
-const{ ApiPromise, WsProvider } = require('@polkadot/api')
-
-(async () => {
-    const provider = new WsProvider('wss://cc3-5.kusama.network/')
-    const api = await ApiPromise.create({ provider })
-    // ...
-```
-
-Connect to it in Polkadot Apps UI by clicking the top-left corner of the screen and selecting the
-appropriate option:
-
-<img src={require('./assets/endpoints/kusama_endpoint_web3.png').default} width="40%" />
-
-[kusama network]: https://kusama.network
-[parity]: https://parity.io
-[polkadot-js apps]: https://polkadot.js.org/apps

docs/kusama-ledger.md

@@ -3,7 +3,9 @@ id: kusama-ledger
 title: Using Ledger Devices
 sidebar_label: Ledger Devices
 ---
+
 <!-- page being updated -->
+
 > Note: Because of required WebUSB support, Ledger wallets currently only work on Chromium-based
 > browsers like Brave and Chrome.