chore: fix analysis namespace

Signed-off-by: realanna <[email protected]>

docs/content/en/docs/install/k8s.md

@@ -132,34 +132,30 @@ Some considerations for Keptn:
   So you can create `KeptnMetrics` in a centralized namespace
   (such as `keptn-lifecycle-toolkit`)
   and access those metrics in evaluations on all namespaces in the cluster.
-* The references to the resources used for analyses,
+* Analysis related resources
   ([Analysis](../yaml-crd-ref/analysis.md),
   [AnalysisDefinition](../yaml-crd-ref/analysisdefinition.md),
   and
   [AnalysisValueTemplate](../yaml-crd-ref/analysisvaluetemplate.md))
-  each support an optional `namespace` field.
+  reference each other via a `name` and, optionally, a `namespace` field.
   The `Analysis` resource references the `AnalysisDefinition` resource,
   which then references the `AnalysisValueTemplate` resources.
 
   * If the `namespace` in the reference is not set explicitly,
     the `AnalysisDefinition` and `AnalysisValueTemplate` resources
     must reside in the same namespace as the `Analysis` resource.
-    In this case, analyses resources of the same name
-    can reside in different namespaces without impacting each other.
   * If the `namespace` in the reference is set for the resources,
     the `Analysis`, `AnalysisDefinition`, and `AnalysisValueTemplate` resources
     can each reside in different namespaces.
-    In this case, each analysis resource must have a name
-    that is unique for the cluster.
 
   This provides configuration options such as the following:
 
   * You can have one namespace
-      with all of your `AnalysisDefinitions` and `AnalysisValueTemplates` resources
-      and reuse them in the different namespaces where you run the analyses.
+      with all of your `AnalysisDefinition` and `AnalysisValueTemplate` resources
+      and reuse them in the different namespaces where you run analyses.
 
   * You can have everything strictly namespaced
-      and always put the `AnalysisDefinitions`, `ValueTemplates`
+      and always put the `AnalysisDefinition`, `AnalysisValueTemplate`
       and the `Analysis` resources into the same namespace,
       without adding the explicit namespace selectors
       when creating references between those objects.