From cdd241d8ffafa03b539f54c12d8da92dabd64e50 Mon Sep 17 00:00:00 2001 From: pinpox Date: Mon, 25 Aug 2025 11:56:29 +0200 Subject: [PATCH] Replace funky utf-8 singlequotes with decent ones --- README.md | 2 +- docs/site/guides/clanServices.md | 6 +++--- lib/jsonschema/default.nix | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 6a7e71e3b..fb5e9466b 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ Our mission is simple: to democratize computing by providing tools that empower ## Features of Clan -- **Full-Stack System Deployment:** Utilize Clan’s toolkit alongside Nix's reliability to build and manage systems effortlessly. +- **Full-Stack System Deployment:** Utilize Clan's toolkit alongside Nix's reliability to build and manage systems effortlessly. - **Overlay Networks:** Secure, private communication channels between devices. - **Virtual Machine Integration:** Seamless operation of VM applications within the main operating system. - **Robust Backup Management:** Long-term, self-hosted data preservation. diff --git a/docs/site/guides/clanServices.md b/docs/site/guides/clanServices.md index e4be22157..960b56a36 100644 --- a/docs/site/guides/clanServices.md +++ b/docs/site/guides/clanServices.md @@ -1,6 +1,6 @@ # Using `clanServices` -Clan’s `clanServices` system is a composable way to define and deploy services across machines. +Clan's `clanServices` system is a composable way to define and deploy services across machines. This guide shows how to **instantiate** a `clanService`, explains how service definitions are structured in your inventory, and how to pick or create services from modules exposed by flakes. @@ -130,7 +130,7 @@ inventory.instances = { ## Picking a clanService -You can use services exposed by Clan’s core module library, `clan-core`. +You can use services exposed by Clan's core module library, `clan-core`. 🔗 See: [List of Available Services in clan-core](../reference/clanServices/index.md) @@ -152,7 +152,7 @@ You might expose your service module from your flake — this makes it easy for --- -## What’s Next? +## What's Next? * [Author your own clanService →](../guides/services/community.md) * [Migrate from clanModules →](../guides/migrations/migrate-inventory-services.md) diff --git a/lib/jsonschema/default.nix b/lib/jsonschema/default.nix index 1385b3ad2..2b4aab9a3 100644 --- a/lib/jsonschema/default.nix +++ b/lib/jsonschema/default.nix @@ -328,7 +328,7 @@ rec { # To get the type of a Deferred modules we need to know the interface of the place where it is evaluated. # i.e. in case of a clan.service this is the interface of the service which dynamically changes depending on the service # We assign "type" = [] - # This means any value is valid — or like TypeScript’s unknown. + # This means any value is valid — or like TypeScript's unknown. # We can assign the type later, when we know the exact interface. # tsType = "unknown" is a type that we preload for json2ts, such that it gets the correct type in typescript (option.type.name == "deferredModule")