Run formatter

docs/site/guides/migrations/disk-id.md

@@ -1,6 +1,8 @@
 # Migrate disko config from `clanModules.disk-id`
 
-If you previously bootstrapped a machine's disk using `clanModules.disk-id`, you should now migrate to a standalone, self-contained disko configuration. This ensures long-term stability and avoids reliance on dynamic values from Clan.
+If you previously bootstrapped a machine's disk using `clanModules.disk-id`, you
+should now migrate to a standalone, self-contained disko configuration. This
+ensures long-term stability and avoids reliance on dynamic values from Clan.
 
 If your `disko.nix` currently looks something like this:
 
@@ -49,8 +51,8 @@ Run the following command to retrieve the generated disk ID for your machine:
 clan vars list <machineName>
 ```
 
-Which should print the generated `disk-id/diskId` value in clear text
-You should see output like:
+Which should print the generated `disk-id/diskId` value in clear text You should
+see output like:
 
 ```shellSession
 disk-id/diskId: fcef30a749f8451d8f60c46e1ead726f
@@ -68,7 +70,8 @@ We are going to make three changes:
 
 - Remove `let in, imports, {lib,clan-core,config, ...}:` to isolate the file.
 - Replace `suffix` with the actual disk-id
-- Move `disko.devices.disk.main.device` from `flake.nix` or `configuration.nix` into this file.
+- Move `disko.devices.disk.main.device` from `flake.nix` or `configuration.nix`
+  into this file.
 
 ```{.nix title="disko.nix" hl_lines="7-9 11-14"}
 {
@@ -93,6 +96,8 @@ We are going to make three changes:
 }
 ```
 
-These steps are only needed for existing configurations that depend on the `diskId` module.
+These steps are only needed for existing configurations that depend on the
+`diskId` module.
 
-For newer machines clan offers simple *disk templates* via its [templates cli](../../reference/cli/templates.md)
+For newer machines clan offers simple *disk templates* via its
+[templates cli](../../reference/cli/templates.md)