diff --git a/modules/get-started/pages/config-rpk-profile.adoc b/modules/get-started/pages/config-rpk-profile.adoc
index 7a355bdbc..adeeb475e 100644
--- a/modules/get-started/pages/config-rpk-profile.adoc
+++ b/modules/get-started/pages/config-rpk-profile.adoc
@@ -19,7 +19,7 @@ An rpk profile contains a reusable configuration for a Redpanda cluster. When ru
 
 You can create different profiles for different Redpanda clusters. For example, your local cluster, development cluster, and production cluster can each have their own profile, with all of their information managed locally by rpk. You set a unique name for each profile.
 
-A profile saves rpk-specific command properties. For details, see xref:get-started:intro-to-rpk.adoc#specify-command-properties[Specify command properties].
+A profile saves rpk-specific command properties. For details, see xref:get-started:intro-to-rpk.adoc#specify-configuration-properties[Specify command properties].
 
 All `rpk` commands can read configuration values from a profile. You pass a profile to an `rpk` command by setting the `--profile` flag. For example, the command `rpk topic produce dev-topic --profile dev` gets its configuration from the profile named `dev`.