diff --git a/certbot/CHANGELOG.md b/certbot/CHANGELOG.md
index cae27ad1a..b05ec6c08 100644
--- a/certbot/CHANGELOG.md
+++ b/certbot/CHANGELOG.md
@@ -16,7 +16,6 @@ Certbot adheres to [Semantic Versioning](https://semver.org/).
 
 * We no longer publish our beta Windows installer as was originally announced
   [here](https://community.letsencrypt.org/t/certbot-discontinuing-windows-beta-support-in-2024/208101).
-* Switch to using docker compose v2, as Azure's images dropped v1.
 
 ### Fixed
 
diff --git a/certbot/docs/contributing.rst b/certbot/docs/contributing.rst
index d4d187e58..9fded857b 100644
--- a/certbot/docs/contributing.rst
+++ b/certbot/docs/contributing.rst
@@ -154,7 +154,7 @@ Running automated integration tests
 
 Generally it is sufficient to open a pull request and let Github and Azure Pipelines run
 integration tests for you. However, you may want to run them locally before submitting
-your pull request. You need Docker and docker-compose (v1 or v2) installed and working.
+your pull request. You need Docker installed and working.
 
 The tox environment `integration` will setup `Pebble`_, the Let's Encrypt ACME CA server
 for integration testing, then launch the Certbot integration tests.