sightly modification of documentation

docs/modules/administration/pages/helm-migration.adoc

@@ -4,10 +4,10 @@ Tailor has been developed for OpenShift 3.11. Back in the days, Helm 2 required
 
 While Tailor also works in an OpenShift 4 cluster, OpenShift has integrated Helm into its product, and Helm has a huge and growing community. Therefore, it is recommended to use Helm instead of Tailor in an OpenShift 4 cluster.
 
-This document will describe how to migrate from Tailor to Helm for OpenDevStack installation.
-
 Tailor is based on OpenShift templates, which define the Kubernetes resources to apply. Helm uses a different templating language / engine, but in the end the templates also describe Kubernetes resources. Therefore, migration effort is relatively low as one only needs to change the syntax of the definition, not the definition itself. Further, there are differences between the CLI of the two tools and not all features of Tailor are available in Helm and vice-versa. Once migration to Helm is complete, it is also recommended to look at the best practices in the Helm community and adopt these.
 
+This document will describe how to adopt resources deployed using Tailor into a Helm release for OpenDevStack installation.
+
 == Templates preparation
 
 There are basically two options how to approach this: you can either adopt your existing OpenShift resources to chart templates, or you can start a clean installation.