remove link to current version (#4229)

versioned_docs/version-8.4/self-managed/modeler/web-modeler/troubleshooting/troubleshoot-zeebe-connection.md

@@ -10,7 +10,7 @@ Web Modeler Self-Managed is available to [enterprise customers](../../../../refe
 
 You try to connect (i.e., to deploy) to a remote Zeebe cluster and Web Modeler reports an error.
 
-To resolve this issue, check if you can connect to Zeebe through another client, i.e., [`zbctl`](/docs/apis-tools/cli-client/index.md).
+To resolve this issue, check if you can connect to Zeebe through another client, i.e., [`zbctl`](/apis-tools/cli-client/index.md).
 If that doesn't work, resolve the general connection issue first (see [the platform deployment troubleshooting section](/self-managed/platform-deployment/troubleshooting.md), for example.)
 
 If that works, further debug your Zeebe connection with the help of the information stated below. Enabling [debug logging in `modeler-restapi`](#how-can-i-debug-log-grpc--zeebe-communication) may also help to understand the issue.
@@ -19,7 +19,7 @@ If that works, further debug your Zeebe connection with the help of the informat
 
 ### Increase the Zeebe client timeout
 
-Web Modeler uses the [Zeebe Java client](/docs/apis-tools/java-client/index.md) to connect to Zeebe.
+Web Modeler uses the [Zeebe Java client](/apis-tools/java-client/index.md) to connect to Zeebe.
 Depending on your infrastructure, the default timeouts configured may be too short.
 
 You can pass custom timeouts in milliseconds for Web Modeler's Zeebe client to `modeler-restapi` via three individual environment variables: