docs: fix several typos

Fixes #10000

Fixes #10001

Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
(cherry picked from commit 4c32616)

cmd/talosctl/cmd/talos/bootstrap.go

@@ -28,9 +28,9 @@ var bootstrapCmd = &cobra.Command{
 	Use:   "bootstrap",
 	Short: "Bootstrap the etcd cluster on the specified node.",
 	Long: `When Talos cluster is created etcd service on control plane nodes enter the join loop waiting
-to join etcd peers from other control plane nodes. One node should be picked as the boostrap node.
-When boostrap command is issued, the node aborts join process and bootstraps etcd cluster as a single node cluster.
-Other control plane nodes will join etcd cluster once Kubernetes is boostrapped on the bootstrap node.
+to join etcd peers from other control plane nodes. One node should be picked as the bootstrap node.
+When bootstrap command is issued, the node aborts join process and bootstraps etcd cluster as a single node cluster.
+Other control plane nodes will join etcd cluster once Kubernetes is bootstrapped on the bootstrap node.
 
 This command should not be used when "init" type node are used.
 

website/content/v1.9/introduction/getting-started.md

@@ -151,14 +151,14 @@ error applying new configuration: rpc error: code = InvalidArgument desc = confi
     * specified install disk does not exist: "/dev/sda"
 ```
 
-You can verify which disks your nodes have by using the `talosctl disks --insecure` command.
+You can verify which disks your nodes have by using the `talosctl get disks --insecure` command.
 
 > Insecure mode is needed at this point as the PKI infrastructure has not yet been set up.
 
-For example, the `talosctl disks` command below shows that the system has a `vda` drive, not an `sda`:
+For example, the `talosctl get disks` command below shows that the system has a `vda` drive, not an `sda`:
 
 ```sh
-$ talosctl -n 192.168.0.2 disks --insecure
+$ talosctl -n 192.168.0.2 get disks --insecure
 DEV        MODEL   SERIAL   TYPE   UUID   WWID  MODALIAS                    NAME   SIZE    BUS_PATH
 /dev/vda   -       -        HDD    -      -      virtio:d00000002v00001AF4   -      69 GB   /pci0000:00/0000:00:06.0/virtio2/
 ```

website/content/v1.9/reference/cli.md

@@ -47,9 +47,9 @@ Bootstrap the etcd cluster on the specified node.
 ### Synopsis
 
 When Talos cluster is created etcd service on control plane nodes enter the join loop waiting
-to join etcd peers from other control plane nodes. One node should be picked as the boostrap node.
-When boostrap command is issued, the node aborts join process and bootstraps etcd cluster as a single node cluster.
-Other control plane nodes will join etcd cluster once Kubernetes is boostrapped on the bootstrap node.
+to join etcd peers from other control plane nodes. One node should be picked as the bootstrap node.
+When bootstrap command is issued, the node aborts join process and bootstraps etcd cluster as a single node cluster.
+Other control plane nodes will join etcd cluster once Kubernetes is bootstrapped on the bootstrap node.
 
 This command should not be used when "init" type node are used.
 

website/content/v1.9/talos-guides/install/virtualized-platforms/proxmox.md

@@ -193,7 +193,7 @@ This will create several files in the `_out` directory: `controlplane.yaml`, `wo
 > You can check for disks running the following command:
 >
 > ```bash
-> talosctl disks --insecure --nodes $CONTROL_PLANE_IP
+> talosctl get disks --insecure --nodes $CONTROL_PLANE_IP
 > ```
 >
 > Update `controlplane.yaml` and `worker.yaml` config files to point to the correct disk location.