OSDOCS#15902: [OLMv1][TP] Installing extensions with webhooks

Author: michaelryanpeter

modules/olmv1-installing-an-operator-in-a-specific-namespace.adoc

@@ -13,7 +13,7 @@ However, some existing cluster extensions do not support the `AllNamespaces` ins
 
 The `MultiNamespace` install mode is not supported. As a result, you cannot install the same Operator multiple times on a cluster.
 
-:FeatureName: Support for deploying a cluster extension in a specific namespace
+:FeatureName: Deploying a cluster extension in a specific namespace
 include::snippets/technology-preview.adoc[]
 
 For more information, see "Supported extensions".

modules/olmv1-supported-extensions.adoc

@@ -9,7 +9,8 @@
 
 include::snippets/olmv1-tp-extension-support.adoc[]
 
-[IMPORTANT]
-====
+:FeatureName: Deploying an extension in a specific namespace and installing an extension with webhooks
+include::snippets/technology-preview.adoc[]
+
 include::snippets/olmv1-operator-conditions-support.adoc[]
-====
+

snippets/olmv1-tp-extension-support.adoc

@@ -10,8 +10,9 @@ Currently, {olmv1-first} supports installing cluster extensions that meet all of
 
 * The extension must use the `registry+v1` bundle format introduced in {olmv0}.
 * The extension must support installation via the `AllNamespaces` install mode.
-** Support for the `SingleNamespace` and `OwnNamespace` install mode is included in {product-title} {product-version} as a Technology Preview feature.
+** You can use the `SingleNamespace` and `OwnNamespace` install modes as a Technology Preview feature in {product-title} {product-version} .
 * The extension must not use webhooks.
+** You can install extensions that use webhooks as a Technology Preview feature in {product-title} {product-version}.
 * The extension must not declare dependencies by using any of the following file-based catalog properties:
 ** `olm.gvk.required`
 ** `olm.package.required`