Fix doc spelling errors after updates in vale rules (Infra)

docs/.custom_wordlist.txt

@@ -1,12 +1,51 @@
+# Leave a blank line at the end of this file to support concatenation
+Baz
+bluetooth
+bool
+boolean
+cachable
+CAgent
+compilable
+ctypes
 debhelper
+dmidecode
+dpkg
+env
 ethernet
+fi
+froz
 gen_control
+github
+jenga
+jq
 json
+JUnit
+libre
+loopback
 Makefile
+multipath
 mylauncher
 nlink_info_kind
 nlink_type
 noperstate
+noreturn
 plainbox
+PPAs
+prepending
+regexes
+repo
 subprocess
+syscall
+systemd
+TAgent
+teardown
+templated
+testplan
+TServer
 unary
+validator
+venv
+vfork
+wodim
+xlsx
+xz

docs/reference/snaps.rst

@@ -73,4 +73,4 @@ If you want the most up-to-date possible build of Checkbox you can use the
 ``edge`` channel. These builds are updated daily and contain the latest changes to
 the framework. We do not advise to use this channel in production, it is tested
 via CI and it is built from the latest commit in the ``main`` branch of the
-`Checkbox Repository on github <https://github.com/canonical/checkbox>`_.
+`Checkbox Repository on GitHub <https://github.com/canonical/checkbox>`_.

docs/tutorial/custom_frontend.rst

@@ -13,7 +13,7 @@ created.
 Prerequisites
 =============
 
-To complete this tutorial you will need snapcraft. Refer to the following to
+To complete this tutorial you will need Snapcraft. Refer to the following to
 install it: `Set up Snapcraft <https://documentation.ubuntu.com/snapcraft/stable/how-to/set-up-snapcraft/>`_
 
 Additionally, you will need the provider we created during the previous
@@ -26,7 +26,7 @@ Starting a new Checkbox Frontend snap
 =====================================
 
 To begin our new snap we start from creating a new project directory. Usually
-cusom frontends are named `checkbox_name_of_the_project`, so start by creating
+custom frontends are named `checkbox_name_of_the_project`, so start by creating
 a `checkbox_tutorial` directory. Prepare the following tree structure,
 creating a new ``providers`` directory and a ``snap`` directory inside of it,
 then copy the ``2024.com.tutorial:tutorial`` directory we created via
@@ -148,10 +148,10 @@ new snap and connect them.
   Here we have to use ``--dangerous`` because we built the snap locally.
   Once in the store this will no longer be necessary.
 
-Building the snap on Github
+Building the snap on GitHub
 ===========================
 
-We reccommend creating the following workflow in your repository to build and
+We recommend creating the following workflow in your repository to build and
 publish your snap. This tutorial will not go into much detail about how you
 should gate the promotion between edge, beta and stable but we advise you to
 take inspiration from the Checkbox process detailed in :ref:`canary-explanation`.