fix: correct typos across docs and messages (#1229)

## Summary

This PR fixes typos in docs and user-facing messages.

## Detailed Changes

| File | Fixed |
|---|---|
| `scripts/create-release.nix` | `uncommited` -> `uncommitted` (4x) |
| `lib/default.nix:906` | `Depracated` -> `Deprecated` |
| `lib/tests.nix:195` | `mkOveride` -> `mkOverride` |
| `docs/interactive-vm.md:3` | `similiar` -> `similar` |
| `docs/disko-images.md:82` | `involed` -> `involved` |
| `docs/disko-images.md:110` | `scirpt` -> `script` |
| `docs/table-to-gpt.md:62` | `partiton` -> `partition` |
| `lib/make-disk-image.nix:212` | `involed` -> `involved` |
| `docs/disko-images.md:11` | `In the this example` -> `In this example`
|

No intended behavior change.

Closes #1228

Author: Mic92

docs/disko-images.md

@@ -8,7 +8,7 @@ Follow the steps below to generate disk images:
 1. **Create a NixOS configuration that includes the disko and the disk
    configuration of your choice**
 
-In the this example we create a flake containing a nixos configuration for
+In this example we create a flake containing a nixos configuration for
 `myhost`.
 
 ```nix
@@ -79,7 +79,7 @@ In the this example we create a flake containing a nixos configuration for
      They will have the same permissions but will be owned by root:root
    * --build-memory <amt>
      specify the amount of memory in MiB that gets allocated to the build VM
-     This can be useful if you want to build images with a more involed NixOS config
+     This can be useful if you want to build images with a more involved NixOS config
      The default is 1024 MiB
    ```
 
@@ -107,7 +107,7 @@ In the this example we create a flake containing a nixos configuration for
   disko.devices.disk.<drive>.imageName = "nixos-x86_64-linux-generic-btrfs"; # Set your preferred name
   ```
 
-  The image scirpt will produce `nixos-x86_64-linux-generic-btrfs.raw` instead of `<drive>.raw`.
+  The image script will produce `nixos-x86_64-linux-generic-btrfs.raw` instead of `<drive>.raw`.
 
 - For virtual drive use, define the image size in your Disko configuration:
 

docs/interactive-vm.md

@@ -1,6 +1,6 @@
 # Running Interactive VMs with `disko`
 
-disko now exports its own flavor of interactive VMs (similiar to
+disko now exports its own flavor of interactive VMs (similar to
 config.system.build.vm). Simply import the disko module and build the vm runner
 with:
 

docs/table-to-gpt.md

@@ -59,7 +59,7 @@ for example like this:
 
 ## Remediation
 
-The new GPT layout (`type = "gpt"`) uses partlabels to realize the partiton
+The new GPT layout (`type = "gpt"`) uses partlabels to realize the partition
 numbering. For this reason you have to manually set up partition labels, if you
 want to resolve this issue.
 

lib/default.nix

@@ -940,7 +940,7 @@ let
             type = lib.types.str;
             description = ''
               The script to unmount (& destroy) all devices defined by disko.devices
-              Does not ask for confirmation! Depracated in favor of _destroy
+              Does not ask for confirmation! Deprecated in favor of _destroy
             '';
             default = ''
               umount -Rv "${rootMountPoint}" || :

lib/make-disk-image.nix

@@ -209,7 +209,7 @@ in
       They will have the same permissions but will be owned by root:root
     * --build-memory <amt>
       specify the amount of memory in MiB that gets allocated to the build VM
-      This can be useful if you want to build images with a more involed NixOS config
+      This can be useful if you want to build images with a more involved NixOS config
       The default is disko.memSize which defaults to ${builtins.toString options.disko.memSize.default} MiB
     USAGE
     }

lib/tests.nix

@@ -192,7 +192,7 @@ let
                   boot.swraid.mdadmConf = "PROGRAM ${pkgs.coreutils}/bin/true";
 
                   # grub will install to these devices, we need to force those or we are offset by 1
-                  # we use mkOveride 70, so that users can override this with mkForce in case they are testing grub mirrored boots
+                  # we use mkOverride 70, so that users can override this with mkForce in case they are testing grub mirrored boots
                   boot.loader.grub.devices = lib.mkOverride 70 testConfigInstall.boot.loader.grub.devices;
 
                   assertions = [

scripts/create-release.nix

@@ -43,9 +43,9 @@ writeShellApplication {
     fi
 
     # Ensure there are no uncommitted or unpushed changes
-    uncommited_changes=$(git diff --compact-summary)
-    if [[ -n "$uncommited_changes" ]]; then
-      echo -e "There are uncommited changes, exiting:\n''${uncommited_changes}" >&2
+    uncommitted_changes=$(git diff --compact-summary)
+    if [[ -n "$uncommitted_changes" ]]; then
+      echo -e "There are uncommitted changes, exiting:\n''${uncommitted_changes}" >&2
       exit 1
     fi
     git pull https://github.com/nix-community/disko master