From 8a3eb00ad8755e9adaf58ba0b85cb28e610d5e29 Mon Sep 17 00:00:00 2001
From: Michel Laterman <82832767+michel-laterman@users.noreply.github.com>
Date: Wed, 29 Jan 2025 11:58:16 -0800
Subject: [PATCH] --fleet-server-cert-key-passphrase-path ->
 --fleet-server-cert-key-passphrase (#1658)

(cherry picked from commit cabf66abb8fdc214f4fccef6b38515778c7a75ee)
---
 docs/en/ingest-management/fleet/fleet-server-secrets.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/ingest-management/fleet/fleet-server-secrets.asciidoc b/docs/en/ingest-management/fleet/fleet-server-secrets.asciidoc
index d3445df12..25a8fd95f 100644
--- a/docs/en/ingest-management/fleet/fleet-server-secrets.asciidoc
+++ b/docs/en/ingest-management/fleet/fleet-server-secrets.asciidoc
@@ -80,7 +80,7 @@ inputs:
     ssl.key_passphrase_path: /path/to/passphrase
 ----
 +
-When you are running {fleet-server} under {agent}, you can provide the passphrase path using the `--fleet-server-cert-key-passphrase-path` flag.
+When you are running {fleet-server} under {agent}, you can provide the passphrase path using the `--fleet-server-cert-key-passphrase` flag.
 See <<elastic-agent-cmd-options,{agent} command reference>> for more details.
 +
 If you are <<elastic-agent-container,running {fleet-server} under {agent} in a container>>, you can use the environment variable `FLEET_SERVER_CERT_KEY_PASSPHRASE` to specify the file path.