From a8159195bfaef3c64df75d3b1e6a68d49d392be9 Mon Sep 17 00:00:00 2001
From: Robert Helgesson <robert@rycee.net>
Date: Thu, 30 Jan 2025 23:22:29 +0100
Subject: [PATCH] flake-module: fix naming

---
 docs/manual/nix-flakes/flake-parts.md | 3 +--
 flake-module.nix                      | 4 ++--
 2 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/docs/manual/nix-flakes/flake-parts.md b/docs/manual/nix-flakes/flake-parts.md
index 1c6d60d33..b314bef3c 100644
--- a/docs/manual/nix-flakes/flake-parts.md
+++ b/docs/manual/nix-flakes/flake-parts.md
@@ -1,7 +1,7 @@
 # flake-parts module {#sec-flakes-flake-parts-module}
 
 When using [flake-parts](https://flake.parts)
-you may wish to import home-manager's flake module,
+you may wish to import Home Manager's flake module,
 `flakeModules.home-manager`.
 
 ``` nix
@@ -37,4 +37,3 @@ modules.
 If you are only defining `homeModules` and/or `homeConfigurations` once in a
 single module, flake-parts should work fine without importing
 `flakeModules.home-manager`.
-
diff --git a/flake-module.nix b/flake-module.nix
index 466698c4b..cf421f9b1 100644
--- a/flake-module.nix
+++ b/flake-module.nix
@@ -7,7 +7,7 @@ in {
         type = types.lazyAttrsOf types.raw;
         default = { };
         description = ''
-          Instantiated Home-Manager configurations.
+          Instantiated Home Manager configurations.
 
           `homeConfigurations` is for specific installations. If you want to expose
           reusable configurations, add them to `homeModules` in the form of modules, so
@@ -22,7 +22,7 @@ in {
           imports = [ v ];
         });
         description = ''
-          Home-Manager modules.
+          Home Manager modules.
 
           You may use this for reusable pieces of configuration, service modules, etc.
         '';