morning peer revue

.vitepress/theme/custom.css

@@ -11,11 +11,3 @@
   border-radius: 10em;
 }
 
-.VPFeatures .icon {
-  background-color: #d9d9f2;
-}
-
-.dark .VPFeatures .icon {
-  background-color: #2b2f36;
-}
-

roadmap.md

@@ -1,13 +1,13 @@
 # Roadmap
 
 This project is still very young but the main steps are already identified.
-The roadmap may move if priorities are evolving/
+The roadmap may move if priorities are evolving.
 
 ## v0.1 
 
-Static webapp for NixiN with the following features
+**This version targets builds for simple mono-server configuration that can contain multiple webapps**.
 
-*This version targets builds for simple mono-server configuration that can contain multiple webapps*.
+Static webapp for NixiN with the following features
 
 - networking options with wireguard configuration options
 - nixpkgs modules selection for common webapps
@@ -21,3 +21,13 @@ Static webapp for NixiN with the following features
 - nixpkgs selection
 - templates for custom configuration.nix
 - Download or copy/paste generated configuration.nix
+
+
+## v0.2
+
+
+## v0.3
+
+## In future
+
+

technical-principles.md

@@ -6,8 +6,8 @@
 ## Do not reinvent the wheel
 
 ## There is only one timezone
-Experience has showned that using multiple timezones for the servers of an infrastructure is a receipe for disaster. 
-Also, using the timezone of one contry for an international project is a source of confusion and headackes. 
+Experience has shown that using multiple time-zones for the servers of an infrastructure is a recipe for disaster. 
+Also, using the timezone of one country for an international project is a source of confusion and headaches. 
 Especially when that timezone is subject to daylight saving changes that are causing the clock to jump 1 hour forward or backward twice a year.
 The only sensible choice is to set the servers time to UTC and to transalte the timestamps to the user's timezone when displaying them. 
 
@@ -25,10 +25,10 @@ Currently only the forgejo action runners used for CI/CD are hosted on NixOS ser
 ## Prioritize security
 
 ## No premature performance optimization
-Use best practices to write efficient code but do not write overly complicated solutions based on a-priori thinking of performanc e issue.
+Use best practices to write efficient code but do not write overly complicated solutions based on a-priori thinking of performance issue.
 Only optimize what has been tested to be an issue.
 
 ## Do fast prototypes and releases cycles.
-Even though we think that Rust would be a better language for developing the tools of the project we are starting the first version using Go because it is faster to develop with it and easier to find contributors with this langages.
+Even though we think that Rust would be a better language for developing the tools of the project we are starting the first version using Go because it is faster to develop with it and easier to find contributors with this languages.