Update uptime.mdx

Author: vmadhusudanan

docs/guides/uptime.mdx

@@ -21,6 +21,6 @@ Collected here are a set of best practices that help maximize your uptime - acro
 
 7. **Caching on client SDKs**: Initializing Statsig client SDKs requires them to connect to Statsig and download config. Client SDKs can cache and reuse config (for the same user) if they are offline. You can also choose to bootstrap your client from your own server (and remove the round trip to Statsig) by using [client SDK bootstrapping](https://docs.statsig.com/server/nodejsServerSDK#bootstrap).
 
-8. **Caching on server SDKs**: Initializing Statsig server SDKs requires them to connect to Statsig and download config. If connectivity to Statsig fails, initialization fails (falling back to default values). Remove this dependency when connectivity fails by providing this config locally. Read more about [dataAdapter](https://docs.statsig.com/server/nodejsServerSDK)
+8. **Caching on server SDKs**: Initializing Statsig server SDKs requires them to connect to Statsig and download config. If connectivity to Statsig fails, initialization fails (falling back to default values). Remove this dependency when connectivity fails by providing this config locally. Read more about [dataAdapter](https://docs.statsig.com/server/concepts/data_store#dataadapter-or-datastore)
 
 9. **Test for failure conditions** explicitly (e.g. no Statsig client or server connectivity). Also understand and embrace the variety of capabilities we’ve built to support different kinds of [testing](https://docs.statsig.com/guides/testing).