Merge pull request #244 from anoma/bengt/v0.30

fixed stuff

packages/docs/pages/introduction.mdx

@@ -15,15 +15,15 @@ Here are some useful tips for reading this book:
 
 - Comments start with `#`:
 
-`# this is a comment make sure you read them!`
+`# this is a comment. Make sure you read them!`
 
 - Sample outputs start with an arrow:
 
 `➜ this is an example command line output useful for comparing`
 
 - User-defined inputs are in angle brackets:
 
-`$ this is a command you should run <with your own input>`
+`this is a command you should run "<with your own input>"`
 
 ## About this documentation
 

packages/docs/pages/introduction/install/source.mdx

@@ -3,15 +3,15 @@ import { Callout } from 'nextra-theme-docs'
 # Install from source
 
 <Callout type="warning">
-Please note that, although installing from source is the recommended route for installing namada, it can prove to be difficult, and is not recommended for beginners. For a first time installation, the installation process can take up to an hour. Building binaries from source can also take a long time, depending on your machine.
+Please note that, although installing from source is the recommended route for installing namada, it can prove to be difficult, and is not recommended for beginners. For a first time installation, the installation process can take up to an hour. Building binaries from source can also take a long time, depending on the machine.
 </Callout>
 
 ## Pre-requisites
 
-Make sure you have the correct [pre-requisites](./source/pre-requisites.mdx) downloaded and installed.
+Ensure the correct [pre-requisites](./source/pre-requisites.mdx) have been downloaded and installed.
 
 ## Installing Namada
-Now that you have all the required dependencies installed, you can clone the source code from the [Namada repository](https://github.com/anoma/namada) and build it with:
+Once all the required dependencies have been installed, the next step is to clone the source code from the [Namada repository](https://github.com/anoma/namada) and build it with:
 
 ```shell copy
 git clone https://github.com/anoma/namada.git

packages/docs/pages/networks/testnets/genesis-validator-apply.mdx

@@ -6,7 +6,7 @@ Before a testnet launches, you can apply to be a genesis validator.
 
 ### Set up
 
-Follow [this guide](../../operators/validators/validator-setup.mdx#pre-genesis) on how to generate your "pre-genesis" validator files.
+Follow [this guide](../../operators/validators/validator-setup.mdx#pre-genesis) on how to generate "pre-genesis" validator files.
 
 <Callout>
 For the shielded expedition, the `balances.toml` file has been published at the [namada-shieled-expedition repository](https://github.com/anoma/namada-shielded-expedition).

packages/docs/pages/operators/networks/genesis-flow/participants.mdx

@@ -196,7 +196,11 @@ Validator account address: tnam1q8lsztqqhpjxdwzw88mqqc2mun7dvpxvas3v2dxk
 
 #### Bond to a pre-genesis validator account
 If your public key has been allocated `NAM` (`NAAN` for the shielded expedition), you can bond to a genesis validator as a pre-genesis transaction.
-Please follow the below steps:
+<Callout type="info">
+This step is intended for pre-genesis participants who have been allocated `NAM` (`NAAN` for the shielded expedition) and want to bond to a genesis validator that is not their own. If you want to bond to your own genesis validator, please follow the steps in [Generate a pre-genesis validator account](#generate-a-pre-genesis-validator-account) and use the `--self-bond` arguments.
+</Callout>
+
+The bond can be achieved by running:
 
 ```bash copy
 namadac utils genesis-bond \
@@ -206,7 +210,7 @@ namadac utils genesis-bond \
     --path "<filename-for-your-tx.toml>"
 ```
 
-After this step is completed, sign the transaction 
+After this step is completed, it is required to sign the transaction.
 
 
 ### Signing transactions

packages/docs/pages/operators/networks/local-network.mdx

@@ -77,6 +77,6 @@ The ledger can be run through the familiar command:
 After the local network has fulfilled its purpose, it can be cleaned up by running the following commands found in the cleanup function of the script:
 
 ```shell copy
-    kilalll namadan
+    killall namadan
     # delete the base_dir/chain_id directory
 ```

packages/docs/pages/users/public-goods-stewards/_meta.json

@@ -1,5 +1,5 @@
 {
   "electing": "Becoming a Steward",
   "voting": "Voting for Stewards and PGF proposals",
-  "proposing": "PGF proposals (Stewards only)"
+  "proposing": "PGF proposals"
 }

packages/docs/pages/users/public-goods-stewards/proposing.mdx

@@ -4,7 +4,7 @@ import { Callout } from 'nextra-theme-docs'
 
 ## Formatting the `proposal.json`
 
-Below is an example of a `PGFProposal` that a steward could submit. Note that only stewards will be able to submit these proposals.
+Below is an example of a `PGFProposal` that a governance participant could submit.
 ```json
 {
     "proposal" :{
@@ -51,7 +51,7 @@ Save this file as `PGF_proposal.json` to some memorable path on your machine.
 
 ## Submitting the proposal
 
-In order to submit the proposal, the steward can use the following command:
+In order to submit the proposal, the governance participant can use the following command:
 
 ```shell copy
 namada client init-proposal \