Merge branch 'docs/cleanup-4.8' into master

docs/concepts/workflows/external-workflow-integration.adoc

@@ -18,7 +18,7 @@ Therefore, the natural way for midPoint to interact with workflow processes is t
 In most scenarios the workflow engine will drive the whole process and midPoint will be only one of the systems that are acting in the workflow.
 Workflow engines have support for various types of integration how they can interact with other systems.
 In case of midPoint, the most suitable integration point is the xref:/midpoint/reference/interfaces/rest/[REST API] that expose all necessary functions.
-Of course the workflow engine can use other types of integration like xref:/midpoint/reference/master/interfaces/midpoint-client-java/[midPoint client library] or even provide data that midPoint will synchronize using a standardized connector.
+Of course the workflow engine can use other types of integration like xref:/midpoint/reference/interfaces/midpoint-client-java/[midPoint client library] or even provide data that midPoint will synchronize using a standardized connector.
 
 More elaborate integration might require to initiate the workflow from midPoint and then let the workflow engine take over. Also, tighter integration between both might be required to allow you see pending operation in midPoint and know they are waiting for next steps being done externally.
 For this scenarios we have designed a planned feature for xref:/midpoint/features/planned/external-workflow-integration/[external workflow integration plugin].

docs/concepts/workflows/index.adoc

@@ -97,7 +97,7 @@ Workflows engines are very potent tools for implementing company-wide processes.
 == MidPoint approach
 
 Even though there was a time when people were expecting wide ranges of workflow engine capabilities from IdM and IGA solution, this demand was removed by deploying standalone workflows engines.
-MidPoint can be integrated with such engine using their native capabilities or with xref:/midpoint/reference/support-4.8/concepts/workflows/external-workflow-integration/[exteral workflow integration] support.
+MidPoint can be integrated with such engine using their native capabilities or with xref:/midpoint/reference/concepts/workflows/external-workflow-integration/[exteral workflow integration] support.
 
 Nevertheless, midPoint offers its own unique approach to workflows that enables you handling most scenarios with efficiency.
 It uses several features that can be easily combined.
@@ -143,7 +143,7 @@ See xref:/midpoint/reference/cases/approval/policy-based-approvals/[approvals do
 The last two types of workflows are covering form based actions and workflow engines.
 MidPoint doesn't support the full workflow engine functionality, because it follows the design rule of focusing on single purpose and master it rather than being universal bloated tool for everything.
 In addition to that, the workflow engine functionality that would require integration with other systems and applications beyond standard IGA integration that midPoint offers.
-But midPoint offers an option to be xref:/midpoint/reference/support-4.8/concepts/workflows/external-workflow-integration/[integrated with external workflows engines].
+But midPoint offers an option to be xref:/midpoint/reference/concepts/workflows/external-workflow-integration/[integrated with external workflows engines].
 
 For the same reasons midPoint currently don't offer form based custom actions described above.
 We are considering them very close to the full workflow engines capabilities.