General spelling audit and tidyup

docs/.custom_wordlist.txt

@@ -8,8 +8,16 @@ apport
 appserver
 appservers
 auditable
+autobuild
+autobuilder
+Autobuilders
+autobuilding
+Autobuilding
 backend
 backends
+backgrounding
+backport
+backports
 BOF
 BOFs
 bootable
@@ -20,11 +28,14 @@ Bzr
 Casper
 CET
 changelog
+changelogs
 Charmcraft
 checksums
+chroot
 chroots
 codebases
 cjk
+cron
 cryptographic
 cryptographically
 CVE
@@ -35,7 +46,9 @@ Debian
 DEP
 DEPs
 dev
+devs
 devel
+DIF
 distro
 dvipng
 edubuntu
@@ -58,13 +71,20 @@ GPL
 GPLs
 gyre
 Heimes
+hostname
+hppa
+HPPA
 html
+http
 https
+ia
+IA
 IEEE
 Intersphinx
 ISO
 ISOs
 Jira
+KDE
 kubuntu
 Kubuntu
 kustom
@@ -78,28 +98,39 @@ localhost
 Lubuntu
 macOS
 manpage
+Matic
 meetingology
 mentorship
 metapackage
+mir
 MIR
 MIRs
 modaliases
 modularity
+MOTU
+MOTUs
 Multipass
 NACK
 neurotype
 ODA
+oem
+OFTC
+oneiric
 organized
 otf
 plantuml
+powerpc
 ppc64el
 Pygments
 QEMU
+quantal
 Repo
+RFP
 Rockcraft
 rst
 rulebook
 RULEs
+SCM
 SLO
 SLOs
 submitters
@@ -108,19 +139,26 @@ texlive
 TOC
 toctree
 TODOs
+toolchain
+toolchains
 txt
+ubumirror
 ubuntu
 Ubuntu
+UDD
 uploader
 utils
 vendored
 vendoring
 Vendoring
 VMs
+WCAG
+WNPP
 wordlist
 workspaces
-WCAG
+Xenial
 xetex
-XMLRPC
+XFCE
 xindy
+XMLRPC
 Xubuntu

docs/staging/MIR/mir-exceptions.md

@@ -27,7 +27,7 @@ This is the subject of a
 [discussion with the Technical Board](https://lists.ubuntu.com/archives/technical-board/2020-January/002478.html).
 See [OEM Archive](https://wiki.ubuntu.com/OEMArchive) for further details.
 
-See {ref}`mir-exception-oem`.
+See {ref}`mir-exceptions-oem`.
 
 ## Re-reviews
 

docs/staging/MIR/mir-file-a-bug.md

@@ -8,7 +8,7 @@ team member (for an extra review).
 The MIR bug **reporter** is expected to:
 
 1. Thoroughly go through TODO/RULE entries in
-   {ref}`Ubuntu Main Inclusion RULEs and TODOs <main-inclusion-requirements>`,
+   {ref}`Ubuntu Main Inclusion RULEs and TODOs <mir-requirements>`,
    check that the package meets all the points there.
    If the package has non-trivial problems, it is not eligible for main
    inclusion, and needs to be fixed first.
@@ -20,7 +20,7 @@ The MIR bug **reporter** is expected to:
 1. File a bug report about the package, titled "`[MIR] sourcepackagename`".
 
    1. Use the template from
-      {ref}`Ubuntu Main Inclusion RULEs and TODOs <main-inclusion-requirements>`.
+      {ref}`Ubuntu Main Inclusion RULEs and TODOs <mir-requirements>`.
 
    1. For each rule include a positive or negative statement as confirmation
       that you checked each requirement carefully.

docs/staging/MIR/mir-service-level-objectives.md

@@ -17,7 +17,7 @@ quality, warnings and the many other things we check for, you can help increase
 efficiency. So please take all the statements we ask for seriously and try to
 fulfill them.
 
-### MIR review SLO
+## MIR review SLO
 
 While we aim for more when possible, our goal is to assign (in the weekly meeting)
 one review per active MIR member per week, to come back with the result before
@@ -39,7 +39,7 @@ requester to look for alternative solutions.
 
 Please consider this in your estimations when you plan a contribution.
 
-### Security review SLO
+## Security review SLO
 
 Security team MIRs are laborious and require lead time. Make MIR requests as
 early in a release cycle as possible, ideally well before Feature Freeze. For

docs/staging/new-packages.md

@@ -38,7 +38,7 @@ that meet the requirements of the
 to be requested within Debian's
 [Work-Needing and Prospective Packages](http://www.debian.org/devel/wnpp/)
 (WNPP) process by filing a Request for Package (RFP) bug on the WNPP package in
-Debian's bugtracker.
+Debian's bug tracker.
 
 If you file a `needs-packaging` bug, please link it to the Debian WNPP bug as
 well.

docs/staging/package-archive.md

@@ -64,12 +64,12 @@ archive.
 
 Notifications of uploads are sent to a mailing list.  A different list is used for each Ubuntu release:
 
- * [[http://lists.ubuntu.com/mailman/listinfo/hardy-changes/|8.04 (hardy)]]
- * [[http://lists.ubuntu.com/mailman/listinfo/lucid-changes|10.04 (lucid)]] 
- * [[http://lists.ubuntu.com/mailman/listinfo/natty-changes|11.04 (natty)]] 
- * [[http://lists.ubuntu.com/mailman/listinfo/oneiric-changes|11.10 (oneiric)]]
- * [[http://lists.ubuntu.com/mailman/listinfo/precise-changes|12.04 (precise)]]
- * [[http://lists.ubuntu.com/mailman/listinfo/quantal-changes|12.10 (quantal)]]
+* [8.04 (hardy)](http://lists.ubuntu.com/mailman/listinfo/hardy-changes/)
+* [10.04 (lucid)](http://lists.ubuntu.com/mailman/listinfo/lucid-changes)
+* [11.04 (natty)](http://lists.ubuntu.com/mailman/listinfo/natty-changes)
+* [11.10 (oneiric)](http://lists.ubuntu.com/mailman/listinfo/oneiric-changes)
+* [12.04 (precise)](http://lists.ubuntu.com/mailman/listinfo/precise-changes)
+* [12.10 (quantal)](http://lists.ubuntu.com/mailman/listinfo/quantal-changes)
 
 ```{admonition} Question
 :class: important
@@ -78,7 +78,7 @@ to create it in a way that makes it better maintainable (otherwise it will get
 this out of date again).
 ```
 
-Changelogs for all packages are available at
+You can find changelogs for all packages at
 http://changelogs.ubuntu.com/changelogs/ (this is the source used by
 `update-manager` and Synaptic).
 
@@ -122,8 +122,8 @@ To request a backport, follow the
 The archive is periodically checked for various inconsistencies, such as
 incorrect dependency relationships between packages.
 
-* https://ubuntu-archive-team.ubuntu.com/proposed-migration/questing_uninst.txt
-  -- packages which are uninstallable due to unsatisfiable dependencies.
+* [Packages that are uninstallable](https://ubuntu-archive-team.ubuntu.com/proposed-migration/questing_uninst.txt)
+  -- due to dependencies that cannot be satisfied.
 * [Ubuntu Development/NBS](https://wiki.ubuntu.com/UbuntuDevelopment/NBS) -
   binary packages that are no longer built by any source package.
   These packages are not automatically removed from the archive, since
@@ -294,10 +294,10 @@ issue new releases or updates out of sync with official Ubuntu releases.
 
 * `armel` (official from Ubuntu 9.10 to Ubuntu 11.10; [discontinued as of Ubuntu 13.04](https://lists.ubuntu.com/archives/ubuntu-devel/2012-November/036106.html))
 
-* `hppa` ([HPPAPortStatus](https://wiki.ubuntu.com/HPPAPortStatus), https://launchpad.net/~ubuntu-hppa)
+* `hppa` ([HPPA Port Status](https://wiki.ubuntu.com/HPPAPortStatus), https://launchpad.net/~ubuntu-hppa)
   ([discontinued as of Ubuntu 9.10](https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-May/000571.html))
 
-* `ia64` ([IA64PortStatus](https://wiki.ubuntu.com/IA64PortStatus), https://launchpad.net/~ubuntu-ia64)
+* `ia64` ([IA64 Port Status](https://wiki.ubuntu.com/IA64PortStatus), https://launchpad.net/~ubuntu-ia64)
   ([discontinued as of Ubuntu 10.10](https://lists.ubuntu.com/archives/technical-board/2010-August/000441.html))
 
 * `lpia` ([discontinued as of Ubuntu 10.04](https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-November/000643.html))
@@ -331,11 +331,11 @@ designate as primary those architectures which have very high download rates.
 
 * `armhf` (from Ubuntu 12.04)
 
-* `hppa` ([HPPAPortStatus](https://wiki.ubuntu.com/HPPAPortStatus),
+* `hppa` ([HPPA Port Status](https://wiki.ubuntu.com/HPPAPortStatus),
   https://launchpad.net/~ubuntu-hppa)
   ([discontinued as of Ubuntu 9.10](https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-May/000571.html))
 
-* `ia64` ([IA64PortStatus](https://wiki.ubuntu.com/IA64PortStatus),
+* `ia64` ([IA64 Port Status](https://wiki.ubuntu.com/IA64PortStatus),
   https://launchpad.net/~ubuntu-ia64)
   ([discontinued as of Ubuntu 10.10](https://lists.ubuntu.com/archives/technical-board/2010-August/000441.html))
 
@@ -372,7 +372,7 @@ All images here are officially supported by the Ubuntu project.
 
 ### `cdimage.ubuntu.com`
 
-[cdimage.ubuntu.com](http://cdimage.ubuntu.com/) hosts less frequently
+[`cdimage.ubuntu.com`](http://cdimage.ubuntu.com/) hosts less frequently
 downloaded images. It is not widely mirrored due to its very large size. Some
 images here are officially supported by the Ubuntu project and some are not; if
 an image is on `cdimage.ubuntu.com`, it simply means that it won't fit on

docs/staging/push-mirroring.md

@@ -63,7 +63,7 @@ Canonical will be originating from the IP address: `91.189.88.154` and
 releases - so please ensure that your firewalls allow this.
 
 For authenticity; these keys are signed by
-[Haw Loeung](https://launchpad.net/~hloeung) with the key ID `0xD10ACEB3227B53FC`.
+[`Haw Loeung`](https://launchpad.net/~hloeung) with the key ID `0xD10ACEB3227B53FC`.
 
 If you are not being pushed by Canonical, please contact the mirror
 administrator of the mirror you're being pushed from for their keys and be sure

docs/staging/sponsorship-process.md

@@ -20,10 +20,10 @@ packages, please see the
 
 To make use of Ubuntu merge proposals, follow these steps:
 
-* [[http://packaging.ubuntu.com/html/getting-set-up.html|set up the tools]]
-* [[http://packaging.ubuntu.com/html/udd-intro.html|get the source]]
-* [[http://packaging.ubuntu.com/html/fixing-a-bug.html#work-on-a-fix|work on the package]]
-* [[DistributedDevelopment/Documentation/SeekingSponsorship|seek sponsorship]]
+* [set up the tools](http://packaging.ubuntu.com/html/getting-set-up.html)
+* [get the source](http://packaging.ubuntu.com/html/udd-intro.html)
+* [work on the package](http://packaging.ubuntu.com/html/fixing-a-bug.html#work-on-a-fix)
+* [seek sponsorship](https://wiki.ubuntu.com/DistributedDevelopment/Documentation/SeekingSponsorship)
 
 ```{admonition} Incorrect redirects
 :class: important