Build errors migtools#3

Signed-off-by: A.Arnold <[email protected]>

Author: anarnold97

docs/cli-guide/snippets

@@ -10,7 +10,7 @@ You can now run the {ProductFullName} {CLINameTitle} against multiple applicatio
 
 This feature is currently a Developer Preview feature.
 
-include::snippets/developer-preview-admonition.adoc[]
+include::templates/developer-preview-admonition.adoc[]
 
 .Procedure
 

docs/eclipse-code-ready-studio-guide/snippets

@@ -159,7 +159,7 @@ Issues are sorted into four categories by default. Information on these categori
 === Insights
 
 :FeatureName: Insights
-include::snippets/technology-preview-admonition.adoc[]
+include::templates/technology-preview-admonition.adoc[]
 
 Previously, a violation generated by a rule with zero effort was listed as an issue in the static report. This is now listed as an insight instead. Issues are generated by general rules, whereas string tags are generated by tagging rules. String tags indicate the presence of a technology but do not show the code location. With the introduction of Insights, you can see the technology used in the application along with its usage in the code.
 

docs/getting-started-guide/snippets

@@ -0,0 +1,10 @@
+// When including this file, ensure that {FeatureName} is set immediately before the include. Otherwise it will result in an incorrect replacement.
+// use :FeatureName:
+
+[IMPORTANT]
+====
+[subs="attributes+"]
+{FeatureName} is a Developer Preview feature only. Developer Preview features are not supported by Red Hat in any way and are not functionally complete or production-ready. Do not use Developer Preview features for production or business-critical workloads. Developer Preview features provide early access to upcoming product features in advance of their possible inclusion in a Red Hat product offering, enabling customers to test functionality and provide feedback during the development process. These features might not have any documentation, are subject to change or removal at any time, and testing is limited. Red Hat might provide ways to submit feedback on Developer Preview features without an associated SLA.
+====
+// Undefine {FeatureName} attribute, so that any mistakes are easily spotted
+:!FeatureName: