docs: rename all references from 'buildClan' to 'lib.clan'

docs/site/guides/getting-started/add-machines.md

@@ -8,7 +8,7 @@ Clan currently offers the following methods to configure machines:
 
 !!! Success "Recommended for advanced Nix users"
 
-    - flake.nix (i.e. via `buildClan`)
+    - flake.nix (i.e. via `clan-core.lib.clan`)
         - `machine` argument
         - `inventory` argument
 
@@ -30,7 +30,7 @@ In the `flake.nix` file:
 === "**normal flake template**"
 
     ```nix title="flake.nix" hl_lines="3"
-    buildClan {
+    clan-core.lib.clan {
         # Set a unique name
         meta.name = "Lobsters";
         # Necessary for importing external Clan services
@@ -60,7 +60,7 @@ Adding or configuring a new machine requires two simple steps:
 
 ???+ Note "Cloud Machines"
     NixOS can cause strange issues when booting in certain cloud environments.
-    
+
     - If on Linode: Make sure that the system uses Direct Disk boot kernel (found in the configuration pannel)
 
 ### Step 1. Identify Target Disk-ID

docs/site/guides/getting-started/deploy.md

@@ -175,7 +175,7 @@ During an update, the CLI will SSH into the build host and run `nixos-rebuild` f
 
 
 ```{.nix hl_lines="5" .no-copy}
-buildClan {
+clan {
     # ...
     machines = {
         "jon" = {
@@ -191,7 +191,7 @@ To exclude machines from being updated when running `clan machines update` witho
 one can set the `clan.deployment.requireExplicitUpdate` option to true:
 
 ```{.nix hl_lines="5" .no-copy}
-buildClan {
+clan {
     # ...
     machines = {
         "jon" = {

docs/site/guides/getting-started/secrets.md

@@ -82,7 +82,7 @@ are loaded when using Clan:
   outputs =
     { self, clan-core, ... }:
     let
-      clan = clan-core.clanLib.buildClan {
+      clan = clan-core.clanLib.clan {
         inherit self;
 
         meta.name = "myclan";