[Protocol Upgrade] Docs and v0.1.29 release (#1771)

- Protocol Upgrade Documentation
- `v0.1.29` release artifacts

---

Co-authored-by: Bryan White <[email protected]>

Author: Olshansk

.gitignore

@@ -127,3 +127,6 @@ localnet_testing_msg_import_morse_accounts.json
 
 # Gov Param Update transaction templates
 *_params_*.json
+
+# Used for telegram announcements
+release_prep_announcement.txt

docusaurus/docs/1_operate/4_faq/3_validator_faq.md

@@ -161,7 +161,7 @@ Your Full Node must be fully synchronized before creating a Validator.
 **Monitor and follow**:
 
 - Upgrade notifications in [Pocket Network's Discord](https://discord.com/invite/pocket-network)
-- The [latest recommended version](../../4_develop/upgrades/4_upgrade_list.md) documentation
+- The [latest recommended version](../../4_develop/upgrades/6_upgrade_list.md) documentation
 
 ## What security practices should I follow?
 
@@ -174,7 +174,8 @@ Your Full Node must be fully synchronized before creating a Validator.
 
 ## What keys are important for Validators?
 
-  _BE ABSOLUTELY SURE YOU HAVE THESE BACKED UP!!!_
-  - You will need your validator address key (the address you staked from)
-  - Your `priv_validator_key.json` - found in `/pocketd/config`
-  - Your `node_key.json` - found in `/pocketd/config`
+_BE ABSOLUTELY SURE YOU HAVE THESE BACKED UP!!!_
+
+- You will need your validator address key (the address you staked from)
+- Your `priv_validator_key.json` - found in `/pocketd/config`
+- Your `node_key.json` - found in `/pocketd/config`

docusaurus/docs/2_explore/2_account_management/1_pocketd_cli.md

@@ -220,7 +220,7 @@ This section is intended **only for core protocol developers**.
 
 It is also only intended for for dev releases of the `pocketd` CLI.
 
-If you are publishing an official protocol upgrade accompanies by a CLI update, visit the [release procedure docs](../../4_develop//upgrades/2_release_procedure.md).
+If you are publishing an official protocol upgrade accompanies by a CLI update, visit the [release procedure docs](../../4_develop/upgrades/2_upgrade_preparation.md).
 
 :::
 

docusaurus/docs/4_develop/upgrades/6_module_auth.md renamed to docusaurus/docs/3_protocol/governance/6_module_auth.md

@@ -1,12 +1,12 @@
 ---
-title: Protocol Upgrades Overview
+title: Upgrade Overview
 sidebar_position: 1
 ---
 
 :::important Managing Protocol Upgrades
 This is a _high-level meta-overview_ of protocol upgrades.
 
-**❗ If you need to trigger a protocol upgrade, see the [Protocol Upgrade Release Procedure](2_release_procedure.md) section ❗**
+**❗ If you need to trigger a protocol upgrade, see the [Protocol Upgrade Release Procedure](./2_upgrade_preparation.md) section ❗**
 :::
 
 Pocket Network evolves through protocol upgrades that keep the network secure, efficient, and up-to-date. These upgrades are coordinated by the DAO (offchain governance) and executed by validators (onchain).
@@ -36,7 +36,7 @@ A protocol upgrade changes the onchain software to:
 ## Where to Find Upgrade Info
 
 - [GitHub Releases](https://github.com/pokt-network/poktroll/releases): All software updates and release notes
-- [Upgrade List](4_upgrade_list.md): Details on each upgrade, breaking changes, and manual steps
+- [Upgrade List](6_upgrade_list.md): Details on each upgrade, breaking changes, and manual steps
 
 :::info Not All Releases Are Upgrades
 Not every [GitHub release](https://github.com/pokt-network/poktroll/releases) triggers a protocol upgrade.