address PR comments

Author: 2dpetkov

docs/pages/nodes/running-node/required-node-configs.mdx

@@ -86,9 +86,9 @@ metrics_enabled = "true"
 price_ttl = "10s"
 
 # Interval is the time between each price update request. The recommended interval
-# is the block time of the chain. Otherwise, 1.5 seconds (1500ms) is a good default. If this
+# is the block time of the chain. Otherwise, 0.6 seconds (600ms) is a good default. If this
 # is greater than 1 minute (1m), the app will not start.
-interval = "1500ms"
+interval = "600ms"
 ```
 
 ## Slinky Configs
@@ -99,7 +99,7 @@ Sidecar can be configured by both flags and environment variables.
 
 | Key                                   | Default      | Description                                                                                                                                       |
 |---------------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
-| `CONNECT_CONFIG_HOST`                    | `"0.0.0.0"`    | The address Slinky will serve requests from. WARNING: changing this value requires updating the oracle_address in the app.toml configuration.    |
+| `CONNECT_CONFIG_HOST`                    | `"0.0.0.0"`    | The address Slinky will serve requests from. For single-machine deployments, consider using `127.0.0.1` for enhanced security. WARNING: changing this value requires updating the oracle_address in the app.toml configuration.    |
 | `CONNECT_CONFIG_PORT`                    | `"8080"`       | The port Slinky will serve requests from. WARNING: changing this value requires updating the oracle_address in the app.toml configuration.       |
 | `CONNECT_CONFIG_METRICS_ENABLED`         | `"true"`       | Enables prometheus metrics.                                                                                                                       |
 | `CONNECT_CONFIG_METRICS_PROMETHEUSSERVERADDRESS` | `"0.0.0.0:8002"` | The address of your prometheus server instance.                                                                                                   |

docs/pages/nodes/running-node/running-a-validator.mdx

@@ -10,7 +10,7 @@ As a validator run the flags `--bridge-daemon-enabled=false` in the command you
 
 ## Slinky
 
-Starting in `v5.0.0`, running a validating full node requires the Slinky sidecar to be running in order to fetch Oracle prices. Slinky is a sidecar that pulls price data from external sources and caches them for the validator to use.
+Starting in [`v5.0.0`](https://www.mintscan.io/dydx/proposals/59), running a validating full node requires the Slinky sidecar to be running in order to fetch Oracle prices. Slinky is a sidecar that pulls price data from external sources and caches them for the validator to use.
 
 ### Running Slinky
 

docs/pages/nodes/upgrades/upgrading-sidecar.mdx

@@ -1,4 +1,4 @@
-Starting in `v5.0.0`, all validating full nodes should be running the [Sidecar](../running-node/optimize.mdx#slinky-sidecar). Non validating full nodes do not need to run the sidecar.
+Starting in [`v5.0.0`](https://www.mintscan.io/dydx/proposals/59), all validating full nodes should be running the [Sidecar](../running-node/optimize.mdx#slinky-sidecar). Non validating full nodes do not need to run the sidecar.
 
 Upgrading the Slinky binary can be done out of band of the chain's binary. If you have a load balancer, CNAME, etc., in front of your sidecar you can simply start up the new version and switch out which version traffic is being directed to during live chain validation.