Merge pull request #34 from martinconic/patch-1

Fix typo in chapter 1

Author: pedropark99

Chapters/01-zig-weird.qmd

@@ -169,10 +169,10 @@ So, everything you need to build a complex Zig project is the
 
 Now that we described this topic in more depth, let's focus
 on the second generated file (`build.zig.zon`), which is the Zig package manager configuration file,
-where you can list and manage the dependencies of your project. Yes, Zig have
+where you can list and manage the dependencies of your project. Yes, Zig has
 a package manager (like `pip` in Python, `cargo` in Rust, or `npm` in Javascript) called Zon,
 and this `build.zig.zon` file is similar to the `package.json` file
-in Javascript projects, or, the `Pipfile` in Python projects.
+in Javascript projects, or, the `Pipfile` file in Python projects, or the `Cargo.toml` file in Rust projects.
 
 
 ### Looking at the `root.zig` file {#sec-root-file}

_freeze/Chapters/01-zig-weird/execute-results/html.json

@@ -381,7 +381,7 @@ <h3 data-number="1.2.1" class="anchored" data-anchor-id="sec-project-files"><spa
 <p>Examples of build systems are CMake, GNU Make, GNU Autoconf and Ninja, which are used to build complex C and C++ projects. With these systems, you can write scripts, which are called “build scripts”. They simply are scripts that describes the necessary steps to compile/build your project.</p>
 <p>However, these are separate tools, that do not belong to C/C++ compilers, like <code>gcc</code> or <code>clang</code>. As a result, in C/C++ projects, you have not only to install and manage your C/C++ compilers, but you also have to install and manage these build systems separately.</p>
 <p>But instead of using a separate build system, in Zig, we use the Zig language itself to write build scripts. In other words, Zig contains a native build system in it. And we can use this build system to write small scripts in Zig, which describes the necessary steps to build/compile our Zig project<a href="#fn2" class="footnote-ref" id="fnref2" role="doc-noteref"><sup>2</sup></a>. So, everything you need to build a complex Zig project is the <code>zig</code> compiler, and nothing more.</p>
-<p>Now that we described this topic in more depth, let’s focus on the second generated file (<code>build.zig.zon</code>), which is the Zig package manager configuration file, where you can list and manage the dependencies of your project. Yes, Zig have a package manager (like <code>pip</code> in Python, <code>cargo</code> in Rust, or <code>npm</code> in Javascript) called Zon, and this <code>build.zig.zon</code> file is similar to the <code>package.json</code> file in Javascript projects, or, the <code>Pipfile</code> in Python projects.</p>
+<p>Now that we described this topic in more depth, let’s focus on the second generated file (<code>build.zig.zon</code>), which is the Zig package manager configuration file, where you can list and manage the dependencies of your project. Yes, Zig has a package manager (like <code>pip</code> in Python, <code>cargo</code> in Rust, or <code>npm</code> in Javascript) called Zon, and this <code>build.zig.zon</code> file is similar to the <code>package.json</code> file in Javascript projects, or, the <code>Pipfile</code> file in Python projects, or the <code>Cargo.toml</code> file in Rust projects.</p>
 </section>
 <section id="sec-root-file" class="level3" data-number="1.2.2">
 <h3 data-number="1.2.2" class="anchored" data-anchor-id="sec-root-file"><span class="header-section-number">1.2.2</span> Looking at the <code>root.zig</code> file</h3>