summaryrefslogtreecommitdiff
path: root/exercises
diff options
context:
space:
mode:
authorChris Boesch <chrboesch@noreply.codeberg.org>2025-08-24 19:26:30 +0200
committerChris Boesch <chrboesch@noreply.codeberg.org>2025-08-24 19:26:30 +0200
commite422e242157494df46b6c0ddbaaa4c2a6a3f1790 (patch)
tree3e2b717dcb956c374cc2135ccf11dae9ef4360b7 /exercises
parent4134d4fa6f2a9c0ae7a56cd6a7b2d156d62c0de1 (diff)
fixes some minor typos
Diffstat (limited to 'exercises')
-rw-r--r--exercises/106_files.zig5
-rw-r--r--exercises/107_files2.zig2
2 files changed, 4 insertions, 3 deletions
diff --git a/exercises/106_files.zig b/exercises/106_files.zig
index b224508..b38bc72 100644
--- a/exercises/106_files.zig
+++ b/exercises/106_files.zig
@@ -63,8 +63,9 @@ pub fn main() !void {
}
// to check if you actually write to the file, you can either,
// 1. open the file in your text editor, or
-// 2. print the content of the file in the console with the following command
-// >> cat ./output/zigling.txt
+// 2. print the content of the file in the console with one of these commands
+// Linux/macOS: >> cat ./output/zigling.txt
+// Windows (CMD): >> type .\output\zigling.txt
//
//
// More on Creating files
diff --git a/exercises/107_files2.zig b/exercises/107_files2.zig
index d059879..9b94101 100644
--- a/exercises/107_files2.zig
+++ b/exercises/107_files2.zig
@@ -2,7 +2,7 @@
// Prerequisite :
// - exercise/106_files.zig, or
// - create a file {project_root}/output/zigling.txt
-// with content `It's zigling time!`(18 byte total)
+// with content `It's zigling time!`(18 bytes total)
//
// Now there's no point in writing to a file if we don't read from it, am I right?
// Let's write a program to read the content of the file that we just created.