diff --git a/modules/deploy/pages/deployment-option/self-hosted/manual/sizing.adoc b/modules/deploy/pages/deployment-option/self-hosted/manual/sizing.adoc
index 6581c1912c..39286d811b 100644
--- a/modules/deploy/pages/deployment-option/self-hosted/manual/sizing.adoc
+++ b/modules/deploy/pages/deployment-option/self-hosted/manual/sizing.adoc
@@ -43,25 +43,20 @@ The following example uses https://iperf.fr/[iPerf3^] to test the network bandwi
 
 [,bash]
 ----
-redpanda1:~$ sudo apt -y update; sudo apt -y install iperf3
-redpanda1:~$ iperf3 -s
+redpanda1:~ sudo apt -y update; sudo apt -y install iperf3
+redpanda1:~ iperf3 -s
 -----------------------------------------------------------
 Server listening on 5201
 -----------------------------------------------------------
-redpanda2:~$ sudo apt update; sudo apt install iperf3
-redpanda2:~$ iperf3 -c redpanda1 -p 5201 -t 300
+redpanda2:~ sudo apt update; sudo apt install iperf3
+redpanda2:~ iperf3 -c redpanda1 -p 5201 -t 300
 Connecting to host redpanda1, port 5201
 [ ID] Interval Transfer Bitrate Retr Cwnd
-[ 5] 0.00-1.00 sec 1.11 GBytes 9.57 Gbits/sec 0 1.64
-MBytes
-[ 5] 1.00-2.00 sec 1.11 GBytes 9.53 Gbits/sec 0 1.64
-MBytes
-[ 5] 2.00-3.00 sec 1.11 GBytes 9.53 Gbits/sec 0 1.64
-MBytes
-[ 5] 3.00-4.00 sec 1.11 GBytes 9.53 Gbits/sec 0 1.72
-MBytes
-[ 5] 4.00-5.00 sec 1.11 GBytes 9.53 Gbits/sec 0 1.72
-MBytes
+[ 5] 0.00-1.00 sec 1.11 GBytes 9.57 Gbits/sec 0 1.64 MBytes
+[ 5] 1.00-2.00 sec 1.11 GBytes 9.53 Gbits/sec 0 1.64 MBytes
+[ 5] 2.00-3.00 sec 1.11 GBytes 9.53 Gbits/sec 0 1.64 MBytes
+[ 5] 3.00-4.00 sec 1.11 GBytes 9.53 Gbits/sec 0 1.72 MBytes
+[ 5] 4.00-5.00 sec 1.11 GBytes 9.53 Gbits/sec 0 1.72 MBytes
 ...
 ----
 
@@ -77,7 +72,7 @@ Redpanda is basically a distributed transaction log with well-understood access
 
 Your best storage solution for your workload depends on your performance and data retention requirements.
 
-If high throughput and low latency is most important, then use locally attached NVMe SSD disks. This is also a good option in the cloud. Just remember that in the cloud, local disks are ephemeral, so data is wiped when an instance is restarted. An alternative in the cloud is to use SSD-backed object storage to persist data between instance restarts. Most cloud providers have options for guaranteeing throughput and provisioned IOPS performance of network-attached storage, although network-attached storage almost always exhibits slightly higher tail latencies than direct-attached storage.
+If high throughput and low latency is most important, then use locally attached NVMe SSD disks. This is also a good option in the cloud. Just remember that in the cloud, local disks are ephemeral, so data is wiped when an instance is restarted. An alternative in the cloud is to use SSD-backed network-attached storage to persist data between instance restarts. Most cloud providers have options for guaranteeing throughput and provisioned IOPS performance of network-attached storage, although network-attached storage almost always exhibits slightly higher tail latencies than direct-attached storage.
 
 For example, AWS io2 volumes offer up to 64,000 IOPS and 1,000 MB/sec throughput with single-digit millisecond latency. This is an expensive option, so if you can trade performance for cost, then AWS gp3 volumes are a good alternative. GCP has comparable options with high-end Extreme persistent disks and the lesser SSD persistent disks. Likewise, Azure has Ultra, Premium, and Standard persistent disk options for choosing the right balance of performance versus cost.
 
@@ -87,9 +82,9 @@ NOTE: Ensure that the fio job runs against the chosen block device. By default,
 
 [,bash]
 ----
-$ sudo apt -y update; sudo apt -y install fio
-$ cd /var/lib/redpanda/data
-$ sudo cat > fio-seq-write.job << EOF
+sudo apt -y update; sudo apt -y install fio
+cd /var/lib/redpanda/data
+sudo tee fio-seq-write.job >/dev/null << EOF
 [global]
 name=fio-seq-write
 filename=fio-seq-write
@@ -105,7 +100,7 @@ size=10G
 ioengine=libaio
 iodepth=16
 EOF
-$ sudo fio fio-seq-write.job
+sudo fio fio-seq-write.job
 ----
 
 Key performance metrics: