Remove RHCOS Layering TP

Author: Michael Burke

modules/coreos-layering-configuring.adoc

@@ -21,7 +21,7 @@ When you configure a custom layered image, {product-title} no longer automatical
 +
 [NOTE]
 ====
-You should use the same base {op-system} image that is installed on the rest of your cluster. Use the `oc adm release info --image-for rhel-coreos-8` command to obtain the base image being used in your cluster.
+You should use the same base {op-system} image that is installed on the rest of your cluster. Use the `oc adm release info --image-for rhel-coreos` command to obtain the base image being used in your cluster.
 ====
 +
 For example, the following Containerfile creates a custom layered image from an {product-title} 4.13 image and a Hotfix package:

post_installation_configuration/coreos-layering.adoc

@@ -26,12 +26,9 @@ To apply a custom layered image, you create a Containerfile that references an {
 
 [NOTE]
 ====
-Use the same base {op-system} image installed on the rest of your cluster. Use the `oc adm release info --image-for rhel-coreos-8` command to obtain the base image used in your cluster.
+Use the same base {op-system} image installed on the rest of your cluster. Use the `oc adm release info --image-for rhel-coreos` command to obtain the base image used in your cluster.
 ====
 
-:FeatureName: Image layering
-include::snippets/technology-preview.adoc[]
-
 {op-system} image layering allows you to use the following types of images to create custom layered images:
 
 * *{product-title} Hotfixes*. You can work with Customer Experience and Engagement (CEE) to obtain and apply link:https://access.redhat.com/solutions/2996001[Hotfix packages] on top of your {op-system} image. In some instances, you might want a bug fix or enhancement before it is included in an official {product-title} release. {op-system} image layering allows you to easily add the Hotfix before it is officially released and remove the Hotfix when the underlying {op-system} image incorporates the fix.