Document discard_abci_responses and pull-mode relaying interaction in the Hermes guide

guide/src/advanced/troubleshooting/cross-comp-config.md

@@ -279,3 +279,14 @@ that it needs in order to relay on behalf of a consumer chain.
 
 ### Fix
 Set `ccv_consumer_chain = true` in `config.toml`.
+
+## Node is not Persisting ABCI Responses
+
+If Hermes is set to query CometBFT's `/block_results` RPC endpoint (which is the case when Hermes is set to use the [pull-based event source][pull-based-event-source]), you may encounter an `Internal error: node is not persisting abci responses (code: -32603)` when clearing packets. 
+
+This is likely due to the underlying CometBFT node being configured to discard ABCI responses via the `discard_abci_responses` configuration paramter being set to `true` in the Comet config. When this option is set to `true`, Hermes will not be able to clear any packets that were sent in either a `begin_block` or an `end_block`; transactions sent using `/tx_search` should still be cleared though. In addition, Hermes will not be able to relay using the pull-based event source if ABCI responses are being discarded. 
+
+### Fix
+Set the Comet node's `discard_abci_resonses = false` in the Comet configuration file. 
+
+[pull-based-event-source]: ./../../documentation/configuration/configure-hermes.md#configuring-support-for-wasm-relaying

guide/src/templates/hermes-version.md

@@ -1 +1 @@
-v1.6.0
+v1.6.0+1c1cf02

guide/src/tutorials/pre-requisites/gaiad-manager.md

@@ -43,29 +43,15 @@ Follow the instructions below to install and configure `gm`.
     Alternatively, you can create the folder `$HOME/.gm/bin` and copy the files from `gm/bin` in there.
 
 3. Activate `gm`
-* Add `source $HOME/.gm/bin/shell-support` to a file that executes when a new terminal window comes up
-  (`$HOME/.bash_profile` or `$HOME/.bashrc` or `$HOME/.zprofile`)
-* (Optional) Enable auto-completion
-
-    - On macOS:
-
-        ```bash
-        # Note: zsh is the default shell on MacOS, so no need to run this unless you explicitly use bash
-        brew install bash-completion
-        ```
-
-    - On Linux:
-
-        ```
-        apt install bash-completion || yum install bash-completion
-        ```
+> **NOTE**: The `shell-support` script allows bash-completion as well as creating a `gm` alias, so you don't need to add more entries to your PATH environment variable.
+> You can optionally enable bash-completion with `gm` by doing the following:
+> * Add `source $HOME/.gm/bin/shell-support` to a file that executes when a new terminal window comes up (`$HOME/.bash_profile` or `$HOME/.bashrc` or `$HOME/.zprofile`)
+> * You may need to install `bash-completion` if adding `shell-support` raises a `command not found: complete` error message. You can do so by executing `brew install bash-completion` on macOS, or `apt install bash-completion || yum install bash-completion` on Linux.
+> * If you don't want to use this, you can always just add `$HOME/.gm/bin` to
+your path.
 
 * Restart your terminal
 
-Note: The `shell-support` script allows bash-completion as well as creating a `gm` alias, so you don't need to add more
-entries to your PATH environment variable. If you don't want to use this, you can always just add `$HOME/.gm/bin` to
-your path.
-
 ### The configuration: `gm.toml`
 **Where**: `$HOME/.gm/gm.toml`.