nit updates

Author: gabedos

content/en/containers/guide/container-discovery-management.md

@@ -271,11 +271,15 @@ The `cel_workload_exclude` configuration is structured as a list of rule sets jo
 
 The `products` field accepts `metrics`, `logs`, and `global` (exclude container from all listed products).
 
-If the configuration contains typos or structural errors, the Agent process gracefully crashes to prevent collecting unintended telemetry which could impact billing. Additionally, the CEL compiler performs basic type checking to ensure valid operations on the container attributes.
+<div class="alert alert-danger">
+If the configuration contains structural errors or CEL syntax issues, the Agent process gracefully **crashes** to prevent collecting unintended telemetry which could impact billing.
+</div>
 
 In the example below, metrics and logs are excluded for any `nginx` container running in the `staging` namespace. Additionally, logs are excluded for any container running the `redis` image, **or** any container within a pod that has the annotation `low_priority: "true"`.
 
 ```yaml
+# datadog.yaml
+
 cel_workload_exclude:
 - products: [metrics, logs]
   rules:
@@ -288,7 +292,7 @@ cel_workload_exclude:
       - container.pod.annotations["low_priority"] == "true"
 ```
 
-The CEL-backed workload exclusion can also be configured by providing a JSON-formatted environment value to `DD_CEL_WORKLOAD_EXCLUDE`.
+The CEL-backed workload exclusion can also be configured by providing a **JSON**-formatted environment value to `DD_CEL_WORKLOAD_EXCLUDE`.
 
 {{% collapse-content title="Setting environment variables" level="h4" expanded=false id="setting-environment-variables" %}}
 
@@ -372,7 +376,7 @@ In **Agent v7.45+** you can set annotations on your Kubernetes pods to control A
 | `ad.datadoghq.com/<CONTAINER_NAME>.logs_exclude`    | Excludes log collection from the container with `<CONTAINER_NAME>` in the pod    |
 | `ad.datadoghq.com/<CONTAINER_NAME>.metrics_exclude` | Excludes metric collection from the container with `<CONTAINER_NAME>` in the pod |
 
-The `ad.datadoghq.com/exclude` annotation set on the application pod takes the highest priority. This means that even if a container matches inclusion through `DD_CONTAINER_INCLUDE`, the Agent still ignores monitoring for that container. The same applies for the respective filtering configurations specific for metrics and logs.
+The `ad.datadoghq.com/exclude` annotation set on the application pod takes the highest priority. This means that even if a container matches inclusion through `DD_CONTAINER_INCLUDE` or ``, the Agent still ignores monitoring for that container. The same applies for the respective filtering configurations specific for metrics and logs.
 
 When applying annotation-based exclusions, the Agent checks for all relevant exclusion annotations on the container. For example, when configuring logs for an NGINX container, the Agent will look for `ad.datadoghq.com/exclude`, `ad.datadoghq.com/logs_exclude`, `ad.datadoghq.com/nginx.exclude`, or `ad.datadoghq.com/nginx.logs_exclude` annotations to be `true` on the pod. The same applies for metrics.