the name is Chainguard Containers (#3447)

[ X ] Check if this is a typo or other quick fix and ignore the rest :)

Author: matthewhelmke

content/chainguard/chainguard-repository/overview.md

@@ -49,14 +49,14 @@ All upstream packages are checked against public malware identifier feeds, and a
 See [Libraries Overview](/chainguard/libraries/overview/#upstream-fallback-and-controls) for more information.
 
 
-## Policies for Images
+## Policies for Chainguard Containers
 
-As with Libraries, you can also set policies for Chainguard Images to define rules governing which images can be consumed and under what conditions. Policies can be configured in the Chainguard Console or with `chainctl`, and are enforced automatically across your environment.
+As with Libraries, you can also set policies for Chainguard Containers to define rules governing which container images can be consumed and under what conditions. Policies can be configured in the Chainguard Console or with `chainctl`, and are enforced automatically across your environment.
 
 Available policies include:
 
-* **no-eol**: Prevent end-of-life images from being used.  
-* **cooldown**: Block newly published image versions for a defined period before they can be pulled, giving the security community time to detect threats. The cooldown is configurable (0 to 3650 days) with a default of 7 days. It is applied globally across all packages to prevent dependency resolution errors.
+* **no-eol**: Prevent end-of-life container images from being used.  
+* **cooldown**: Block newly published container image versions for a defined period before they can be pulled, giving the security community time to detect threats. The cooldown is configurable (0 to 3650 days) with a default of 7 days. It is applied globally across all packages to prevent dependency resolution errors.
 
 > **Note**: Chainguard recommends a 7-day cooldown when enabling upstream fallback, to block a large share of malicious packages identified shortly after publication. Shorter cooldown periods increase the risk of pulling malicious or compromised upstream packages before the broader ecosystem can detect and report them.