zig

commit 697b8f7d2f043a40e3ec830625d3a54c9da68923 (tree)
parent f36ac227b13884f42f259bc38c5b0aa012273799
Author: Maximilian <16063560+pattmax00@users.noreply.github.com>
Date:   Wed, 20 Dec 2023 05:17:15 -0600

Grammar fixes (#18320)

* Grammar fixes

Just a couple things I noticed

* Update build.zig.zon.md

Fix a/an usage for zon doc
Diffstat:
M
doc/build.zig.zon.md
 | 
2
+-
M
lib/init/build.zig.zon
 | 
4
++--

2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/build.zig.zon.md b/doc/build.zig.zon.md
@@ -51,7 +51,7 @@ This is computed from the file contents of the directory of files that is
 obtained after fetching `url` and applying the inclusion rules given by
 `paths`.
 
-This field is the source of truth; packages do not come from an `url`; they
+This field is the source of truth; packages do not come from a `url`; they
 come from a `hash`. `url` is just one of many possible mirrors for how to
 obtain a package matching this `hash`.
 
diff --git a/lib/init/build.zig.zon b/lib/init/build.zig.zon
@@ -13,7 +13,7 @@
     // Each dependency must either provide a `url` and `hash`, or a `path`.
     // `zig build --fetch` can be used to fetch all dependencies of a package, recursively.
     // Once all dependencies are fetched, `zig build` no longer requires
-    // Internet connectivity.
+    // internet connectivity.
     .dependencies = .{
         // See `zig fetch --save <url>` for a command-line interface for adding dependencies.
         //.example = .{
@@ -26,7 +26,7 @@
         //    // obtained after fetching `url` and applying the inclusion rules given by
         //    // `paths`.
         //    //
-        //    // This field is the source of truth; packages do not come from an `url`; they
+        //    // This field is the source of truth; packages do not come from a `url`; they
         //    // come from a `hash`. `url` is just one of many possible mirrors for how to
         //    // obtain a package matching this `hash`.
         //    //