diff --git a/docs/guides/improve-processes-with-optimize.md b/docs/guides/improve-processes-with-optimize.md
index 597077a4966..44af0f35004 100644
--- a/docs/guides/improve-processes-with-optimize.md
+++ b/docs/guides/improve-processes-with-optimize.md
@@ -15,7 +15,7 @@ Optimize offers business intelligence tooling for Camunda customers. By leveragi
 
 With Optimize, review heatmap displays for instances which took longer than average to discover long-running flow nodes. As a result, reap actionable insights and rapidly identify the constraints of your system.
 
-See an in-depth overview of Optimize’s capabilities [here](https://docs.camunda.org/optimize/latest/).
+For an in-depth overview of Optimize’s capabilities, visit our [Optimize documentation](../components/optimize/what-is-optimize.md).
 
 ## Set up
 
diff --git a/docs/guides/migrating-from-camunda-platform-7.md b/docs/guides/migrating-from-camunda-platform-7.md
index d59d5ceec6f..6b19b271bad 100644
--- a/docs/guides/migrating-from-camunda-platform-7.md
+++ b/docs/guides/migrating-from-camunda-platform-7.md
@@ -59,12 +59,10 @@ Most expressions can be converted (see [this community extension](https://github
 
 #### Different connector infrastructure
 
-Camunda Platform 7 provides several [connectors](https://docs.camunda.org/manual/latest/reference/connect/). These connectors are not supported in Camunda Platform 8, as Camunda Platform 8 will create a much more powerful connector infrastructure.
+Camunda Platform 7 provides several [connectors](https://docs.camunda.org/manual/latest/reference/connect/). Camunda Platform 8 now also offers multiple [connectors](../components/modeler/web-modeler/connectors/available-connectors/index.md) as well.
 
 To migrate existing connectors, create a small bridging layer to invoke these connectors via a custom [job workers](/components/concepts/job-workers.md).
 
-
-
 ### Process solutions using Spring Boot
 
 With Camunda Platform 7, a frequently used architecture to build a process solution (also known as process applications) is composed out of:
@@ -247,9 +245,9 @@ In essence, this tooling implements details described in the next sections.
 Camunda Platform 8 has a different API than Camunda Platform 7. As a result, you have to migrate some of your code, especially code that does the following:
 
 * Uses the Client API (e.g. to start process instances)
-* Implements [service tasks](https://docs.camunda.org/manual/latest/reference/bpmn20/tasks/service-task/), which can be:
+* Implements [service tasks](../components/modeler/bpmn/service-tasks/service-tasks.md), which can be:
   * [Java code attached to a service task](https://docs.camunda.org/manual/latest/user-guide/process-engine/delegation-code/) and called by the engine directly (in-VM).
-  * [External tasks](https://docs.camunda.org/manual/latest/user-guide/process-engine/external-tasks/), where workers subscribe to the engine.
+  * [External tasks](../components/best-practices/development/invoking-services-from-the-process-c7.md#external-tasks), where workers subscribe to the engine.
 
 
 <!--