Update docs/draft/howto/enable-webhook-support.md

Co-authored-by: Todd Short <[email protected]>

Author: camilamacedo86

docs/draft/howto/enable-webhook-support.md

@@ -5,7 +5,7 @@ Webhook support is enabled by default. The controller uses the `WebhookProviderC
 feature-gate unless you override it. To switch to the OpenShift Service CA provider,
 start the controller with `--feature-gates=WebhookProviderCertManager=false`.
 
-OLMv1 now supports the installation of bundles containing webhooks out of the box.
+OLMv1 supports the installation of bundles containing webhooks by default.
 Webhooks, or more concretely Admission Webhooks, are part of Kuberntes' [Dynamic Admission Control](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/)
 feature. Webhooks run as services called by the kube-apiservice in due course of processing a resource related request. They can be used to validate resources, ensure reasonable default values,
 are set, or aid in the migration to new CustomResourceDefinition schema. The communication with the webhook service is secured by TLS. In OLMv1, the TLS certificate is managed by a