diff --git a/documentation/docs/next-env.d.ts b/documentation/docs/next-env.d.ts
index 4f11a03dc6..a4a7b3f5cf 100644
--- a/documentation/docs/next-env.d.ts
+++ b/documentation/docs/next-env.d.ts
@@ -2,4 +2,4 @@
 /// <reference types="next/image-types/global" />
 
 // NOTE: This file should not be edited
-// see https://nextjs.org/docs/basic-features/typescript for more information.
+// see https://nextjs.org/docs/pages/building-your-application/configuring/typescript for more information.
diff --git a/documentation/docs/pages/developers/clients.mdx b/documentation/docs/pages/developers/clients.mdx
index 7879a96049..b507ecf7be 100644
--- a/documentation/docs/pages/developers/clients.mdx
+++ b/documentation/docs/pages/developers/clients.mdx
@@ -2,7 +2,7 @@
 At present, there are three Nym clients. These are built as standalone binaries when building our codebase, but are most easily accessed through one of our SDKs:
 
 - the websocket (native) client - most easily accessed via the [Rust SDK](./rust) and [Go/C++ FFI](./rust/ffi).
-- the SOCKS5 client - most easily accessed via the [Rust SDK](./rust) and [Go/C++ FFI](./rust/ffi).
+- the SOCKS5 client - most easily accessed via the [Rust SDK](./rust).
 - the wasm (webassembly) client - most easily via the [Typescript SDK](./typescript).
 
 > For information about the role that clients play within the Nym system and their role when communicating with the Mixnet, see the [Client network docs](../network/architecture/mixnet/clients).