diff --git a/internal/pipe/docker/manifest.go b/internal/pipe/docker/manifest.go
index b5e08329cc2..0e5fe62cf04 100644
--- a/internal/pipe/docker/manifest.go
+++ b/internal/pipe/docker/manifest.go
@@ -15,7 +15,7 @@ import (
 	"github.com/goreleaser/goreleaser/pkg/context"
 )
 
-// ManifestPipe is beta implementation of for the docker manifest feature,
+// ManifestPipe is an implementation for the docker manifest feature,
 // allowing to publish multi-arch docker images.
 type ManifestPipe struct{}
 
diff --git a/www/docs/customization/docker_manifest.md b/www/docs/customization/docker_manifest.md
index f88df0e49f7..353415960b2 100644
--- a/www/docs/customization/docker_manifest.md
+++ b/www/docs/customization/docker_manifest.md
@@ -10,10 +10,6 @@ Notice that if you have something in the `docker_manifests` section in your
 config file, GoReleaser will add the manifest's to the release notes
 instead of the Docker images names.
 
-!!! warning
-    Please note that this is a beta feature, and it may change or be removed
-    at any time.
-
 !!! warning
     Notice that the images used in the manifest **need to be pushed** for this to work.
     This is a limitation of how `docker manifest create` works.
@@ -81,11 +77,11 @@ docker_manifests:
 We basically build and push our images as usual, but we also add a new
 section to our config defining which images are part of which manifests.
 
-GoReleaser will create and publish the manifest in its publish phase.
+GoReleaser will create and publish the manifest in its publishing phase.
 
 !!! warning
     Unfortunately, the manifest tool needs the images to be pushed to create
-    the manifest, that's why we both create and push it in the publish phase.
+    the manifest, that's why we both create and push it in the publishing phase.
 
 ## Example config