Apply suggestions from code review

Co-authored-by: Kat Batuigas <36839689+kbatuigas@users.noreply.github.com>

Author: paulohtb6

modules/reference/pages/rpk/rpk-debug/rpk-debug-remote-bundle-download.adoc

@@ -29,7 +29,7 @@ rpk debug remote-bundle download [flags]
 
 |-o, --output |string |The file path where the debug file will be written (default `./<timestamp>-remote-bundle.zip`).
 
-|--upload-url |string |If provided, where to upload the bundle in addition to creating a copy on disk.
+|--upload-url |string |Upload URL provided by Redpanda Support. When specified, uploads the bundle to Redpanda in addition to creating a local copy. For details, see xref:troubleshoot:debug-bundle/generate/kubernetes.adoc#debug-bundle[].
 
 |--config |string |Redpanda or `rpk` config file; default search paths are `/var/lib/redpanda/.config/rpk/rpk.yaml`, `$PWD/redpanda.yaml`, and `/etc/redpanda/redpanda.yaml`.
 

modules/reference/pages/rpk/rpk-debug/rpk-debug-remote-bundle-start.adoc

@@ -41,7 +41,7 @@ rpk debug remote-bundle start [flags]
 
 |--metrics-samples |int |Number of metrics samples to take (at the interval of `--metrics-interval` flag). Must be >= `2` (default `2`).
 
-|-n, --namespace |string |(K8s only) The namespace to use to collect the resources from.
+|-n, --namespace |string |(K8s only) The namespace to use to collect data from the resources.
 
 |--no-confirm |- |Disable confirmation prompt.
 

modules/reference/pages/rpk/rpk-redpanda/rpk-redpanda-admin-brokers-decommission-status.adoc

@@ -35,7 +35,7 @@ kafka/test2/3 3          5             2752632301      140975805      2611656496
 kafka/test2/4 3          6             2975443783      181581219      2793862564
 ----
 
-If a partition cannot be moved for some reason, the command reports the problematic partition in the 'REALLOCATION FAILURE DETAILS' or 'ALLOCATION FAILURES' section and decommission fails. Typical scenarios for failure include:
+If a partition cannot be moved for some reason, the command reports the problematic partition in the 'REALLOCATION FAILURE DETAILS' or 'ALLOCATION FAILURES' section, and decommission fails. Typical scenarios for failure include:
 
 * Insufficient broker storage space to allocate a partition
 * Brokers that cannot satisfy rack constraints