Apply suggestions from review

Author: JakeSCahill

modules/troubleshoot/partials/debug-bundle/configure.adoc

@@ -1,3 +1,5 @@
+NOTE: These configuration options apply only when you trigger a debug bundle remotely. For example using Redpanda Console, `rpk debug remote-bundle`, or the Admin API. They do not apply to the `rpk debug bundle` command.
+
 [[remove]]
 == Automatically remove debug bundles
 

modules/troubleshoot/partials/debug-bundle/generate-rpk.adoc

@@ -168,8 +168,6 @@ ifndef::env-kubernetes[]
 rm /var/lib/redpanda/<bundle-name>.zip
 endif::[]
 ----
-+
-TIP: To avoid manually deleting debug bundles, you can configure the xref:reference:properties/cluster-properties.adoc#debug_bundle_auto_removal_seconds[`debug_bundle_auto_removal_seconds`] property to automatically remove them after a period of time. See xref:{link-configure-bundles}#remove[Automatically remove debug bundles].
 
 When you've finished troubleshooting, remove the debug bundle from your host machine:
 
@@ -182,7 +180,21 @@ rm -r debug-bundle
 
 The xref:reference:rpk/rpk-debug/rpk-debug-remote-bundle.adoc[`rpk debug remote-bundle`] command allows you to remotely generate a consolidated debug bundle from all brokers in your cluster. This command is useful when you do not want to log into each broker's node individually using `rpk debug bundle`.
 
-. Create an xref:get-started:config-rpk-profile.adoc[`rpk` profile] to connect to your cluster. Include all brokers you want to collect data from in the `admin.hosts` configuration. For example:
+. Create an xref:get-started:config-rpk-profile.adoc[`rpk` profile] to connect to your cluster. Include all brokers you want to collect data from in the `admin.hosts` configuration.
++
+[,bash]
+----
+rpk profile create <profile-name> --set admin.hosts=<brokers>
+----
+
+. Check the configured addresses in your profile:
++
+[,bash]
+----
+rpk profile print
+----
++
+Example output:
 +
 .`profile.yml`
 ```yaml