diff --git a/hugo/content/en/getting_started/containers/autodiscovery.md b/hugo/content/en/getting_started/containers/autodiscovery.md
index 2d1d084d4bc..fd0a7f14050 100644
--- a/hugo/content/en/getting_started/containers/autodiscovery.md
+++ b/hugo/content/en/getting_started/containers/autodiscovery.md
@@ -103,7 +103,7 @@ annotations:
 
 In the example above, the `tags.datadoghq.com` labels set the `env`, `service`, and even `version` as tags for all logs and metrics emitted for the pod's `redis` container. These standard labels are part of [Unified Service Tagging][1]. As a best practice, Datadog recommends using unified service tagging when configuring tags and environment variables.
 
-The check configuration annotation key follows the format `ad.datadoghq.com/<container-name>.checks`.
+The check configuration annotation keys follow the format `ad.datadoghq.com/<container-name>.check_names`, `ad.datadoghq.com/<container-name>.init_configs`, and `ad.datadoghq.com/<container-name>.instances`.
 
 `check_names` includes the names of the check to run, and `init_configs` contains some configuration parameters, such as minimum collection interval. Each item in `instances` represents the configuration to run for one instance of a check. **Note**: In this example, `%%host%%` is a template variable that is dynamically populated with your container's IP.