permacomputing

commit 82f8b98f9570c797c2b332f202cfa6aa4da7a510
parent 86ceb3d5fffa4ca6f43173a5c1061a44aba49c50
Author: ugrnm <ugrnm@web>
Date:   Fri, 15 Dec 2023 16:32:17 +0100

empty web commit

Diffstat:
M
getting_started.mdwn
 | 
8
++++----

1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/getting_started.mdwn b/getting_started.mdwn
@@ -31,10 +31,10 @@ if you document it a bit. Successes *and* failures. It does not have to be
 extensive, but it can be a much more effective way to demonstrate how to
 activate critical practices in relation to computer tech. You can do that on
 your own website if you have one, you can make zines, something individual or
-something with others, and of course you could use this wiki! More generally
-publishing does not need to be only about the projects you are involved with
-directly, maybe it is about helping others writing a manual, a cookbook, a
-sampler, something relatable and accessible.
+something with others, and of course [[you could use this wiki|contribute]]! 
+More generally publishing does not need to be only about the projects you are 
+involved with directly, maybe it is about helping others writing a manual, a 
+cookbook, a sampler, something relatable and accessible.
 
 * **Participating**: Some permacomputing activities can make sense as
 individual practices or be related to lifestyle choices and experiments, but