permacomputing

commit 099f66935aef6b6f0e472b78d0e066a21e07c178
parent 856a5eeb44ced718535ad679f0505677c85fdd7f
Author: viznut_web <viznut_web@web>
Date:   Sat, 20 Aug 2022 13:35:46 +0200

typo/grammar

Diffstat:
M
Assessments.mdwn
 | 
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Assessments.mdwn b/Assessments.mdwn
@@ -1,4 +1,4 @@
-Permacomputing is also learning to deal with existing technologies, often trying to find the least evil among bad alternatives. In [[hardware]] we can't afford being too picky because we'll want to lengthen the lifespans of already existing even pieces of hardware, but in [[software]] we usually have more choice.
+Permacomputing is also learning to deal with existing technologies, often trying to find the least evil among bad alternatives. In [[hardware]] we can't afford being too picky because we'll want to lengthen the lifespans of already existing pieces of hardware (even bad ones), but in [[software]] we usually have more choice.
 
 When assessing software and hardware, we'll want to focus on technicalities such as resource use (especially [[energy use]]), [[dependencies|dependency]] and [[documentation]] – mostly because many pieces of today's technology fail miserably in these areas.