Fix spelling mistakes to pass spellcheck.

doc/.custom_wordlist.txt

@@ -0,0 +1,77 @@
+Autoinstall
+Autoinstalls
+Btrfs
+DHCP
+EFI
+Esc
+ESP
+ESPs
+GPT
+GUID
+GiB
+GiB
+Libera
+LPAR
+LTS
+LUKS
+LV
+LVM
+LinuxONE
+MiB
+NIC
+Netplan
+NoCloud
+OEM
+OpenSSH
+Petitboot
+PgDown
+PgUp
+POST
+PPA
+PReP
+SSD
+Seagate
+Subiquity
+UEFI
+URI
+Zdev
+amd
+autoinstall
+autoinstaller
+autoinstalls
+bootable
+bootloader
+bootloaders
+codecs
+config
+curtin
+debconf
+el
+geoip
+globbing
+hostname
+iSCSI
+init
+md
+oem
+passwd
+ppc
+pre
+preseed
+preseeded
+preseeding
+preseeds
+pw
+realname
+rootfs
+rsyslog
+subvolume
+subvolumes
+superset
+traceback
+tty
+ubuntu
+udev
+unformatted
+VLAN
+webhook

doc/.wordlist.txt

@@ -1,37 +1,38 @@
-addons
+
 API
 APIs
-balancer
-Charmhub
 CLI
-dropdown
+Charmhub
 Diátaxis
 EBS
 EKS
-favicon
 Grafana
 IAM
-installable
 JSON
+Jira
 Juju
-Kubernetes
 Kubeflow
+Kubernetes
 Makefile
 MyST
-namespace
-namespaces
 NodePort
-observability
 OLM
 Permalink
+RTD
 ReadMe
+UI
+VM
+YAML
+addons
+balancer
+dropdown
+favicon
+installable
+namespace
+namespaces
+observability
 reST
 reStructuredText
-RTD
 subdirectories
-subtree
 subfolders
-UI
-Jira
-VM
-YAML
+subtree

doc/explanation/configure-storage.rst

@@ -81,9 +81,9 @@ Logical Volume Manager (LVM)
 .. image:: figures/configure-storage-lvm.png
    :alt:
 
-The LVM is a system of managing logical volumes, or filesystems, that is much
+The LVM is a system of managing logical volumes, or file systems, that is much
 more advanced and flexible than the traditional method of partitioning a disk
-into one or more segments and formatting that partition with a filesystem. It
+into one or more segments and formatting that partition with a file system. It
 can be used to combine several disks into one larger pool of storage but it
 offers advantages even in a single disk system, such as snapshots and easy
 resizing of logical volumes.
@@ -113,7 +113,7 @@ but this can be changed later.
 
 On amd64 and arm64 systems, multiple disks can be selected as boot devices,
 which means a system can be configured so that it will continue to boot after
-a failure of any one drive (assuming the root filesystem is placed on a RAID).
+a failure of any one drive (assuming the root file system is placed on a RAID).
 The bootloader will be installed to each of these drives, and the operating
 system configured to install new versions of GRUB to each drive as it is
 updated.
@@ -151,8 +151,8 @@ operating system. One of the ESPs must be mounted at ``/boot/efi``.
 Supported arm64 servers boot using UEFI, and are configured the same way as an
 UEFI-booting amd64 system.
 
-ppc64el systems also load their bootloader (Petitboot, a small linux kernel)
-from a "PReP" partition with a special flag, so in most ways they are similar
+ppc64el systems also load their bootloader (Petitboot, a small Linux kernel)
+from a PReP (PowerPC Reference Platform) partition with a special flag, so in most ways they are similar
 to a UEFI system. The installer only supports one PReP partition at this time.
 
 Limitations and workarounds
@@ -173,4 +173,4 @@ with desired parameters, and then select these partitions or devices as mount
 points in the installer. Any changes you make while the installer is running
 but before altering the storage configuration will reflected in the installer.
 
-The installer cannot yet configure iSCSI mounts or btrfs subvolumes.
+The installer cannot yet configure iSCSI mounts or Btrfs subvolumes.

doc/explanation/operate-server-installer.rst

@@ -10,15 +10,15 @@ step-by-step guide through the screens of the installer, you can use our
 Get the installer
 =================
 
-Installer images are made (approximately) daily and are available from
-https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/. These are not
+Installer images are created (approximately) daily and are available from the
+`Ubuntu release <https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/>`_ page. These are not
 tested as extensively as the images from release day, but they contain the
-latest packages and installer, so fewer updates will be required during or
+latest packages and installer, so fewer updates are required during or
 after installation.
 
-You can download the server installer for amd64 from
-https://ubuntu.com/download/server and other architectures from
-http://cdimage.ubuntu.com/releases/20.04/release/.
+You can download the server installer for amd64 from the
+`Ubuntu Server <https://ubuntu.com/download/server>`_ page and other architectures from the
+`release directory <http://cdimage.ubuntu.com/releases/20.04/release/>`_.
 
 Installer UI navigation
 =======================
@@ -30,8 +30,8 @@ and :kbd:`space` or :kbd:`Enter` keys and a little typing.
 :kbd:`Home` / :kbd:`End` / :kbd:`Page Up` / :kbd:`Page Down` can be used to
 navigate through long lists more quickly in the usual way.
 
-Running the installer over serial
-=================================
+Running the installer over serial port
+======================================
 
 By default, the installer runs on the first virtual terminal, ``tty1``. This
 is what is displayed on any connected monitor by default. However, servers do
@@ -42,10 +42,10 @@ the serial port. To do this, the kernel command line needs to
 specified on it -- a common value is ``console=ttyS0`` but this is not
 something that can be generically documented.
 
-When running on serial, the installer starts in a basic mode that uses only
+When running on serial port, the installer starts in a basic mode that uses only
 the ASCII character set and black and white colours. If you are connecting from
-a terminal emulator such as gnome-terminal that supports Unicode and rich
-colours you can switch to "rich mode" which uses Unicode, colours and supports
+a terminal emulator, such as gnome-terminal, that supports Unicode and rich
+colours, you can switch to "rich mode" which uses Unicode and colours, and supports
 many languages.
 
 .. _connect-via-ssh:
@@ -88,7 +88,7 @@ There are some global keys you can press at any time:
 ====================================  =============================================
 Key                                   Action
 ====================================  =============================================
-:kbd:`ESC`                            Go back
+:kbd:`Esc`                            Go back
 :kbd:`F1`                             Open help menu
 :kbd:`Control` + :kbd:`Z`, :kbd:`F2`  Switch to shell
 :kbd:`Control` + :kbd:`L`, :kbd:`F3`  Redraw screen

doc/howto/autoinstall-quickstart-s390x.rst

@@ -26,8 +26,8 @@ Mount the ISO
     mkdir -p ~/iso
     sudo mount -r ~/Downloads/ubuntu-|ubuntu-latest-version|-live-server-s390x.iso ~/iso
 
-Write your autoinstall config
-=============================
+Write your autoinstall configuration
+====================================
 
 Create a cloud-init configuration:
 
@@ -46,10 +46,10 @@ Create a cloud-init configuration:
     EOF
     touch meta-data
 
-The crypted password is ``ubuntu``.
+The encrypted password is ``ubuntu``.
 
-Serve the cloud-init config over HTTP
-=====================================
+Serve the cloud-init configuration over HTTP
+============================================
 
 Leave this running in one terminal window:
 

doc/howto/autoinstall-quickstart.rst

@@ -17,7 +17,7 @@ Providing the autoinstall data over the network
 ===============================================
 
 This method is the one that generalises most easily to doing an entirely
-network-based install, where a machine netboots and then is automatically
+network-based installation where a machine boots over a network and then is automatically
 installed.
 
 Download the ISO
@@ -37,10 +37,10 @@ Where you should change `<release-number>` to match the number of the LTS or
 release you have downloaded (e.g., `22.04.3` for Jammy or `23.04` for the Lunar
 interim release).
 
-Write your autoinstall config
------------------------------
+Write your autoinstall configuration
+------------------------------------
 
-This means creating cloud-init config as follows:
+This means creating cloud-init configuration as follows:
 
 .. code-block:: bash
 
@@ -57,10 +57,10 @@ This means creating cloud-init config as follows:
     EOF
     touch meta-data
 
-The crypted password is just "ubuntu".
+The encrypted password is ``ubuntu``.
 
-Serve the cloud-init config over HTTP
--------------------------------------
+Serve the cloud-init configuration over HTTP
+--------------------------------------------
 
 Leave this running in one terminal window:
 
@@ -76,8 +76,8 @@ Create a target disk
 
     truncate -s 10G image.img
 
-Run the install!
-----------------
+Run the installation
+--------------------
 
 As before, you will need to change `<release-number>` in the following command
 to match the release ISO you downloaded.
@@ -91,8 +91,8 @@ to match the release ISO you downloaded.
         -initrd /mnt/casper/initrd \
         -append 'autoinstall ds=nocloud-net;s=http://_gateway:3003/'
 
-This will boot, download the config from the server (set up in the previous
-step) and run the install. The installer reboots at the end but the
+This will boot, download the configuration from the server (set up in the previous
+step) and run the installation. The installer reboots at the end but the
 ``-no-reboot`` flag to ``kvm`` means that ``kvm`` will exit when this happens.
 It should take about 5 minutes.
 
@@ -107,8 +107,8 @@ Boot the installed system
 This will boot into the freshly installed system and you should be able to log
 in as ``ubuntu/ubuntu``.
 
-Using another volume to provide the autoinstall config
-======================================================
+Using another volume to provide the autoinstall configuration
+=============================================================
 
 This is the method to use when you want to create media that you can just plug
 into a system to have it be installed.
@@ -137,7 +137,7 @@ Create your user-data and meta-data files
     EOF
     touch meta-data
 
-The crypted password is just ``ubuntu``.
+The encrypted password is ``ubuntu``.
 
 Create an ISO to use as a cloud-init data source
 ------------------------------------------------
@@ -154,8 +154,8 @@ Create a target disk
 
     truncate -s 10G image.img
 
-Run the install!
-----------------
+Run the installation
+--------------------
 
 As before, you will need to change `<release-number>` in the following command
 to match the release ISO you downloaded.
@@ -167,8 +167,8 @@ to match the release ISO you downloaded.
         -drive file=~/seed.iso,format=raw,cache=none,if=virtio \
         -cdrom ~/Downloads/ubuntu-<release-number>-live-server-amd64.iso
 
-This will boot and run the install. Unless you interrupt boot to add
-'autoinstall' to the kernel command line, the installer will prompt for
+This boots the system and runs the installation. Unless you interrupt boot to add
+``autoinstall`` to the kernel command line, the installer prompts for
 confirmation before touching the disk.
 
 The installer reboots at the end but the ``-no-reboot`` flag to ``kvm`` means

doc/howto/report-bugs.rst

@@ -3,7 +3,7 @@
 How to report a problem
 ***********************
 
-We always hope, of course, that every install with the server installer
+We always hope, of course, that every installation with the server installer
 succeeds. But reality doesn't always work that way and there will sometimes be
 failures of various kinds. This section explains the most useful way to report
 any failures so that we can fix the bugs causing them, and we'll keep the topic
@@ -22,7 +22,7 @@ Crash reports
 A failure will result in a crash report being generated which bundles up all
 the information we need to fully diagnose a failure. These live in
 ``/var/crash`` in the installer environment, and for Ubuntu 19.10 and newer
-this is persisted to the install media by default (if there is space). 
+this is persisted to the installation media by default (if there is space).
 
 When an error occurs you are presented with a dialog that allows you to upload
 the report to the error tracker and offers options for continuing. Uploads to