diff --git a/docs/Story Network (L1)/story-network/odyssey-node-setup.md b/docs/Story Network (L1)/story-network/odyssey-node-setup.md
index ee044dd..73ecb37 100644
--- a/docs/Story Network (L1)/story-network/odyssey-node-setup.md	
+++ b/docs/Story Network (L1)/story-network/odyssey-node-setup.md	
@@ -18,7 +18,7 @@ The `story` and `geth` binaries, which make up the clients required for running
 
 * **`story-geth`execution client:**
   * Release Link: [**Click here**](https://github.com/piplabs/story-geth/releases)
-  * Latest Stable Binary (v0.10.1): [**Click here**](https://github.com/piplabs/story-geth/releases/tag/v0.10.1)
+  * Latest Stable Binary (v0.11.0): [**Click here**](https://github.com/piplabs/story-geth/releases/tag/v0.11.0)
 * **`story`consensus client:**
   * Releases link: [**Click here**](https://github.com/piplabs/story/releases)
   * Latest Stable Binary (v0.13.0): [**Click here**](https://github.com/piplabs/story/releases/tag/v0.13.0)
@@ -294,4 +294,4 @@ If you would like to check the status of `story` while it is running, it is help
 
 To manage consensus client upgrades more easily, especially for hard forks, we recommend using [Cosmovisor](https://docs.cosmos.network/v0.45/run-node/cosmovisor.html), which allows you to automate the process of upgrading client binaries without having to restart your client.
 
-To get started, **your client must be upgraded to at least version 0.9.13**. [Here](https://medium.com/story-protocol/story-v0-10-0-node-upgrade-guide-42e2fbcfcb9a) is a  guide to help you with the setup of automated upgrades with Cosmovisor.
\ No newline at end of file
+To get started, **your client must be upgraded to at least version 0.9.13**. [Here](https://medium.com/story-protocol/story-v0-10-0-node-upgrade-guide-42e2fbcfcb9a) is a  guide to help you with the setup of automated upgrades with Cosmovisor.