fix(DOC-1675): document --overprovisioned flag and improve rpk redpanda start prose (#1618)

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Joyce Fee <102751339+Feediver1@users.noreply.github.com>
Co-authored-by: Joyce Fee <joyce@redpanda.com>

Author: 3 people

modules/reference/pages/rpk/rpk-redpanda/rpk-redpanda-start.adoc

@@ -5,23 +5,22 @@ include::reference:partial$unsupported-os-rpk.adoc[]
 
 Start Redpanda.
 
-== Setting up a mode
+== Set up a mode
 
-It's possible to setup a mode for redpanda to start. Currently we support the mode `dev-container`.
+Redpanda supports a `dev-container` mode with preset configuration for development and test environments.
 
-To set up the mode `dev-container` run:
+Run the following command to start Redpanda in `dev-container` mode:
 
 [,bash]
 ----
 rpk redpanda start --mode dev-container
 ----
 
-Mode uses well-known configuration properties for development or tests
-environments:
+This mode bundles the following flags and cluster properties:
 
 Bundled flags:
 
-* `--overprovisioned`
+* xref:reference:rpk/rpk-redpanda/rpk-redpanda-mode.adoc#development-mode[`--overprovisioned`] (disables thread affinity and other production guards; see xref:reference:rpk/rpk-redpanda/rpk-redpanda-mode.adoc#development-mode[`rpk redpanda mode`] for details)
 * `--reserve-memory 0M`
 * `--check=false`
 * `--unsafe-bypass-fsync`
@@ -35,7 +34,7 @@ Bundled cluster properties:
 * `topic_partitions_per_shard: 1000`
 * `fetch_reads_debounce_timeout: 10`
 
-After redpanda starts you can modify the cluster properties using:
+After Redpanda starts, you can modify cluster properties by running:
 
 [,bash]
 ----