cleanup: fix typos

Signed-off-by: Julia Vassiliki <julia.vassiliki@unsw.edu.au>

Author: midnightveil

DEVELOPER.md

@@ -149,7 +149,7 @@ By default `dev_build.py` will use the the Microkit tool directory from source (
 However, in some cases it is desirable to test the Microkit tool built into the SDK.
 In this case pass `--tool-from-sdk` to use the tool that is built into the SDK.
 
-Finally, by default the `dev_build.py` script relies on the default Makefile dependecy resolution.
+Finally, by default the `dev_build.py` script relies on the default Makefile dependency resolution.
 However, in some cases it is useful to force a rebuild while doing SDK development.
 For example, the `Makefile` can't know about the state of the Microkit tool source code.
 To support this a `--rebuild` option is provided.

docs/manual.md

@@ -61,7 +61,7 @@ Rather than a single `main` entry point, a program has four distinct entry point
 On ARM and RISC-V, the individual programs are combined to produce a single bootable *system image*.
 The format of the image is suitable for loading by the target board's bootloader.
 
-On x86-64, there are two ELF images invovled. One for the seL4 kernel, and one for the initialiser that
+On x86-64, there are two ELF images involved. One for the seL4 kernel, and one for the initialiser that
 setups up the Microkit system. These are loaded by a Multiboot 2 compliant bootloader.
 
 The Microkit tool, which is provided as part of the SDK, is used to generate the system image(s).
@@ -1412,7 +1412,7 @@ Microkit will produce a raw binary file by default, so when using U-Boot run the
 
 Support is available for the Radxa Rock3b platform which is based on the Rockchip rk3568 SoC.
 
-Since the platform relies on some closed-source binary blobs for first stage bootloader and then ARM's TrustZone A, we need to compile the U-Boot including these images. Detailed instructions on how to do that are avalilable [here](https://docs.sel4.systems/Hardware/rock3b.html).
+Since the platform relies on some closed-source binary blobs for first stage bootloader and then ARM's TrustZone A, we need to compile the U-Boot including these images. Detailed instructions on how to do that are available [here](https://docs.sel4.systems/Hardware/rock3b.html).
 
 Once the proper U-Boot image is in place, you can simply load the `loader.img` on the board and run it like that (this is assuming you have the TFTP server set up):
 

loader/src/riscv/cpus.c

@@ -20,7 +20,7 @@
  * seL4 on but an additional S-mode only monitor core, this is the case on certain
  * CPUs such as the SiFive U74. The problematic part is that the monitor core has
  * a hart ID of zero and hart IDs are not guaranteed to be contiguous.
- * This is why we must explitly list all the hart IDs that we want to boot on.
+ * This is why we must explicitly list all the hart IDs that we want to boot on.
  * To figure this out for your platform, the best way is to look at the Device Tree,
  * each CPU will have a 'reg' field where the value is the hart ID.
  */

tool/microkit/src/main.rs

@@ -871,7 +871,7 @@ fn main() -> Result<(), String> {
                 }
 
                 // Patch the list of untypeds we used to simulate object allocation into the initialiser.
-                // At runtime the intialiser will validate what we simulated against what the kernel gives it. If they deviate
+                // At runtime the initialiser will validate what we simulated against what the kernel gives it. If they deviate
                 // we will have problems! For example, if we simulated with more memory than what's actually available, the initialiser
                 // can crash.
                 capdl_initialiser.add_expected_untypeds(&kernel_boot_info.untyped_objects);

tool/microkit/src/sdf.rs

@@ -1006,7 +1006,7 @@ impl ProtectionDomain {
                         return Err(value_error(
                             xml_sdf,
                             node,
-                            "seL4 has not been built as a hypervisor, virtual machiens are disabled".to_string()
+                            "seL4 has not been built as a hypervisor, virtual machines are disabled".to_string()
                         ));
                     }
                     if virtual_machine.is_some() {