diff --git a/akka-docs/src/main/paradox/additional/deploy.md b/akka-docs/src/main/paradox/additional/deploy.md
index dc456a2dda..842a696598 100644
--- a/akka-docs/src/main/paradox/additional/deploy.md
+++ b/akka-docs/src/main/paradox/additional/deploy.md
@@ -7,8 +7,6 @@ be put into `WEB-INF/lib`
  * As an application packaged with [sbt-native-packager](https://github.com/sbt/sbt-native-packager)
  
 ## Lightbend Enterprise Suite
- 
-An Akka application can also be packaged and deployed using [Lightbend Enterprise Suite](https://conductr.lightbend.com/docs/2.1.x/DevQuickStart).
 
 Lightbend Enterprise Suite is a solution for managing Lightbend Reactive Platform applications across a cluster of machines.
 It is reactive from the ground up thus enabling operations to provide the resiliency required to unleash the full benefits 
diff --git a/akka-docs/src/main/paradox/cluster-usage.md b/akka-docs/src/main/paradox/cluster-usage.md
index 7224197105..01c5abb0cd 100644
--- a/akka-docs/src/main/paradox/cluster-usage.md
+++ b/akka-docs/src/main/paradox/cluster-usage.md
@@ -134,7 +134,6 @@ This can also be defined as Java system properties when starting the JVM using t
 Such configuration is typically created dynamically by external tools, see for example:
 
 * [Deploying clustered Akka applications on Kubernetes](http://developer.lightbend.com/guides/k8-akka-cluster/)
-* [ConductR](https://conductr.lightbend.com/docs/2.1.x/AkkaAndPlay#Akka-Clustering)
 * [ConstructR](https://github.com/hseeberger/constructr)
 
 The seed nodes can be started in any order and it is not necessary to have all