From e93e3ac14cd1652bc51f01304e3948eef64c740b Mon Sep 17 00:00:00 2001
From: Sridhar Ratnakumar <3998+srid@users.noreply.github.com>
Date: Tue, 19 Dec 2023 09:03:09 -0500
Subject: [PATCH] readme: Use new doc links

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 070ef1c..018db1c 100644
--- a/README.md
+++ b/README.md
@@ -31,7 +31,7 @@ Or see `./test/flake.nix`
 
 ## A note on process working directory
 
-The `dataDir` of these services tend to take *relative* paths, which are usually relative to the project root. As such, when you run these services using `nix run`, their data files are created relative to whichever directory you are in. If you want these data files to always reside relative to the project directory, instead of using `nix run` consider wrapping the process-compose packages in script, via either [mission-control](https://flakular.in/mission-control/) module or a [justfile](https://just.systems/). The example uses the latter.
+The `dataDir` of these services tend to take *relative* paths, which are usually relative to the project root. As such, when you run these services using `nix run`, their data files are created relative to whichever directory you are in. If you want these data files to always reside relative to the project directory, instead of using `nix run` consider wrapping the process-compose packages in script, via either [mission-control](https://community.flake.parts/mission-control) module or a [justfile](https://just.systems/). The example uses the latter.
 
 ## Discussions
 
@@ -40,7 +40,7 @@ To discuss the project, please [join our Zulip](https://nixos.zulipchat.com/#nar
 ## Contributing
 
 - If you are adding a *new* service, see https://github.com/cachix/devenv/tree/main/src/modules/services for inspiration.
-- For contributing to docs, see https://flakular.in/about#contributing
+- For contributing to docs, see https://github.com/flake-parts/community.flake.parts#guidelines-for-writing-docs
 
 ## Credits