From 26b7d4ee8ed39aaaa651c8582677fc7c91d9d0c1 Mon Sep 17 00:00:00 2001 From: Martin Wickham Date: Sat, 26 Nov 2022 15:03:13 -0600 Subject: [PATCH] Clarify wording in readme --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6f9825d..e2ce4ce 100644 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ If you would like to contribute project files for other development environments ## Modifying the template -You can modify the template to add your own changes across all days. To do so, modify template/template.zig and then run `zig build generate`. The `$` character in the template will be replaced by the two-digit day number (e.g. 04 or 17). This step will only overwrite files which have not been modified, so you will not lose work if you update the template after implementing several days. After updating the template and generating, you should check in template/hashes.bin in addition to the updated template and source files. This will ensure that the newly generated files are not considered modified if you update the template again. +You can modify the template to add your own changes across all days. To do so, modify template/template.zig and then run `zig build generate`. The `$` character in the template will be replaced by the two-digit day number (e.g. 04 or 17). This step will only overwrite files which have not been modified, so you will not lose work if you update the template after implementing several days. After updating the template and generating, you should commit the changes to template/hashes.bin in addition to the updated template and source files. This will ensure that the newly generated files are not considered modified if you update the template again. ## Setting up ZLS