minor beautification

Signed-off-by: Moritz Wiesinger <[email protected]>

Author: mowies

docs/docs/components/lifecycle-operator/keptn-apps.md

@@ -144,6 +144,6 @@ annotation/label is populated:
   This means that when only workload and version annotations/labels are provided — without
   the `keptn.sh/app` or `app.kubernetes.io/part-of` annotation — Keptn creates a `KeptnApp`
   resource for each `KeptnWorkload`.
-  Consequently, observability traces will capture individual`KeptnWorkload`
+  Consequently, observability traces will capture individual `KeptnWorkload`
   resources, but they will not represent the combined workloads that make up the complete
   deployed application.

docs/docs/guides/integrate.md

@@ -135,9 +135,9 @@ annotation/label is populated:
   and your observability output traces the individual `Keptnworkload` resources
   but not the combined workloads that constitute your deployed application.
 
-> **Note**: Keptn application discovery concatenates the values of the app.kubernetes.io/name or
-keptn.sh/workload and app.kubernetes.io/part-of or keptn.sh/app annotation to determine the
-name of the KeptnWorkload.
+> **Note**: Keptn application discovery concatenates the values of the `app.kubernetes.io/name` (or
+`keptn.sh/workload`) and `app.kubernetes.io/part-of` (or `keptn.sh/app`) annotation to determine the
+name of the `KeptnWorkload`.
 
 See
 [Keptn Applications and Keptn Workloads](../components/lifecycle-operator/keptn-apps.md)