From 49514473f1ebb75114a3de8d08ea338b59b252b8 Mon Sep 17 00:00:00 2001
From: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Date: Thu, 4 Jan 2024 10:12:14 +0100
Subject: [PATCH] swarm: remove incorrect statement about revoking secret
 access

Closes #18990

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
---
 content/engine/swarm/secrets.md | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/content/engine/swarm/secrets.md b/content/engine/swarm/secrets.md
index b6f1776ba0..120cbf2796 100644
--- a/content/engine/swarm/secrets.md
+++ b/content/engine/swarm/secrets.md
@@ -748,11 +748,6 @@ line.
     wvnh0siktqr3  mysql  replicated  1/1       mysql:latest
     ```
 
-    At this point, you could actually revoke the `mysql` service's access to the
-    `mysql_password` and `mysql_root_password` secrets because the passwords
-    have been saved in the MySQL system database. Don't do that for now, because
-    we use them later to facilitate rotating the MySQL password.
-
 5.  Now that MySQL is set up, create a WordPress service that connects to the
     MySQL service. The WordPress service has the following characteristics:
 
@@ -1041,4 +1036,4 @@ Each service uses environment variables to specify where the service should look
 for that secret data.
 
 More information on short and long syntax for secrets can be found in the
-[Compose Specification](../../compose/compose-file/09-secrets.md).
\ No newline at end of file
+[Compose Specification](../../compose/compose-file/09-secrets.md).