fix typo enbaled

Author: jotak

api/flowcollector/v1beta2/flowcollector_types.go

@@ -1058,7 +1058,7 @@ type FlowCollectorPrometheus struct {
 // `PrometheusQuerier` defines the desired state for querying Prometheus (client...)
 type PrometheusQuerier struct {
 	// When `enable` is `true`, the Console plugin queries flow metrics from Prometheus instead of Loki whenever possible.
-	// It is enbaled by default: set it to `false` to disable this feature.
+	// It is enabled by default: set it to `false` to disable this feature.
 	// The Console plugin can use either Loki or Prometheus as a data source for metrics (see also `spec.loki`), or both.
 	// Not all queries are transposable from Loki to Prometheus. Hence, if Loki is disabled, some features of the plugin are disabled as well,
 	// such as getting per-pod information or viewing raw flows.

bundle/manifests/flows.netobserv.io_flowcollectors.yaml

@@ -6252,7 +6252,7 @@ spec:
                       enable:
                         description: |-
                           When `enable` is `true`, the Console plugin queries flow metrics from Prometheus instead of Loki whenever possible.
-                          It is enbaled by default: set it to `false` to disable this feature.
+                          It is enabled by default: set it to `false` to disable this feature.
                           The Console plugin can use either Loki or Prometheus as a data source for metrics (see also `spec.loki`), or both.
                           Not all queries are transposable from Loki to Prometheus. Hence, if Loki is disabled, some features of the plugin are disabled as well,
                           such as getting per-pod information or viewing raw flows.

config/crd/bases/flows.netobserv.io_flowcollectors.yaml

@@ -5780,7 +5780,7 @@ spec:
                         enable:
                           description: |-
                             When `enable` is `true`, the Console plugin queries flow metrics from Prometheus instead of Loki whenever possible.
-                            It is enbaled by default: set it to `false` to disable this feature.
+                            It is enabled by default: set it to `false` to disable this feature.
                             The Console plugin can use either Loki or Prometheus as a data source for metrics (see also `spec.loki`), or both.
                             Not all queries are transposable from Loki to Prometheus. Hence, if Loki is disabled, some features of the plugin are disabled as well,
                             such as getting per-pod information or viewing raw flows.

docs/FlowCollector.md

@@ -12237,7 +12237,7 @@ Prometheus querying configuration, such as client settings, used in the Console
         <td>boolean</td>
         <td>
           When `enable` is `true`, the Console plugin queries flow metrics from Prometheus instead of Loki whenever possible.
-It is enbaled by default: set it to `false` to disable this feature.
+It is enabled by default: set it to `false` to disable this feature.
 The Console plugin can use either Loki or Prometheus as a data source for metrics (see also `spec.loki`), or both.
 Not all queries are transposable from Loki to Prometheus. Hence, if Loki is disabled, some features of the plugin are disabled as well,
 such as getting per-pod information or viewing raw flows.

helm/crds/flows.netobserv.io_flowcollectors.yaml

@@ -5784,7 +5784,7 @@ spec:
                         enable:
                           description: |-
                             When `enable` is `true`, the Console plugin queries flow metrics from Prometheus instead of Loki whenever possible.
-                            It is enbaled by default: set it to `false` to disable this feature.
+                            It is enabled by default: set it to `false` to disable this feature.
                             The Console plugin can use either Loki or Prometheus as a data source for metrics (see also `spec.loki`), or both.
                             Not all queries are transposable from Loki to Prometheus. Hence, if Loki is disabled, some features of the plugin are disabled as well,
                             such as getting per-pod information or viewing raw flows.