Update build

it/part1/setup.html

@@ -236,9 +236,9 @@ <h4 id="linux"><a class="header" href="#linux">Linux</a></h4>
 <p>Una volta installato RGBDS, aprite il terminale ed eseguite il comando <code>make --version</code> per controllare la vostra versione di Make (che probabilmente è GNU Make).</p>
 <p>Se <code>make</code> non è presente, potrebbe essere necessario installare le <code>build-essentials</code> della propria distribuzione.</p>
 <h3 id="windows"><a class="header" href="#windows">Windows</a></h3>
-<p>La triste verità è che Windows è un pessimo sistema operativo per noi sviluppatori; tuttavia, è possibile installare degli strumenti che risolvono la maggior parte dei suoi problemi.</p>
-<p>Su Windows 10, la scelta migliore è <a href="https://docs.microsoft.com/en-us/windows/wsl">WSL</a>, che permette di eseguire una distribuzione Linux all’interno di Windows.
-Installate WSL 1 o WSL 2, poi una distribuzione a vostra scelta e quindi seguite nuovamente questi passaggi per la distribuzione Linux appena installata.</p>
+<p>The modern tools we’ll be using for Game Boy development have been designed for a Unix environment, so setup on Windows is not fully straightfoward.  However, it’s possible to install an environment that will provide everything we need.</p>
+<p>On Windows 10 and Windows 11, your best bet is <a href="https://docs.microsoft.com/en-us/windows/wsl">WSL</a>, which is a method for running a Linux distribution within Windows.
+Install WSL, then a distribution of your choice (pick Ubuntu if unsure), and then follow these steps again, but for the Linux distribution you installed.</p>
 <p>In alternativa a WSL, si può usare <a href="https://www.msys2.org">MSYS2</a> o <a href="https://www.cygwin.com">Cygwin</a>; per poi consultare le istruzioni per l’installazione di Windows di [RGBDS] (https://rgbds.gbdev.io/install).
 Per quanto ne so, entrambi dovrebbero fornire una versione sufficientemente aggiornata di GNU Make.</p>
 <div class="box tip">

it/part1/toolchain.html

@@ -223,10 +223,10 @@ <h2 id="rgbasm-e-rgblink"><a class="header" href="#rgbasm-e-rgblink">RGBASM e RG
 <p>Quindi: Codice sorgente → <code>rgbasm</code> → File oggetto → <code>rgblink</code> → ROM, giusto?
 Beh, non esattamente.</p>
 <h2 id="rgbfix"><a class="header" href="#rgbfix">RGBFIX</a></h2>
-<p>RGBLINK produce sì una ROM, ma se la provassimo su un GameBoy non funzionerebbe.
-Nelle ROM deve sempre essere presente qualcosa chiamato <em>header</em>:
-questa sezione contiene <a href="https://gbdev.io/pandocs/The_Cartridge_Header.html">informazioni sulla ROM</a>, come il nome del gioco, il nome dell’autore, se sia compatibile con il GameBoy Color ed altro.
-Per il momento abbiamo impostato tutti i valori a zero nel programma per semplicità, ma ne riparleremo nella seconda parte del tutorial.</p>
+<p>RGBLINK does produce a ROM, but it’s not quite usable yet.
+See, actual ROMs have what’s called a <em>header</em>.
+It’s a special area of the ROM that contains <a href="https://gbdev.io/pandocs/The_Cartridge_Header.html">metadata about the ROM</a>; for example, the game’s name, Game Boy Color compatibility, and more.
+For simplicity, we defaulted a lot of these values to 0 for the time being; we’ll come back to them in Part Ⅱ.</p>
 <p>However, the header contains three crucial fields:</p>
 <ul>
 <li>The <a href="https://gbdev.io/pandocs/The_Cartridge_Header.html#0104-0133--nintendo-logo">Nintendo logo</a>,</li>

it/print.html

@@ -293,9 +293,9 @@ <h4 id="linux"><a class="header" href="#linux">Linux</a></h4>
 <p>Una volta installato RGBDS, aprite il terminale ed eseguite il comando <code>make --version</code> per controllare la vostra versione di Make (che probabilmente è GNU Make).</p>
 <p>Se <code>make</code> non è presente, potrebbe essere necessario installare le <code>build-essentials</code> della propria distribuzione.</p>
 <h3 id="windows"><a class="header" href="#windows">Windows</a></h3>
-<p>La triste verità è che Windows è un pessimo sistema operativo per noi sviluppatori; tuttavia, è possibile installare degli strumenti che risolvono la maggior parte dei suoi problemi.</p>
-<p>Su Windows 10, la scelta migliore è <a href="https://docs.microsoft.com/en-us/windows/wsl">WSL</a>, che permette di eseguire una distribuzione Linux all’interno di Windows.
-Installate WSL 1 o WSL 2, poi una distribuzione a vostra scelta e quindi seguite nuovamente questi passaggi per la distribuzione Linux appena installata.</p>
+<p>The modern tools we’ll be using for Game Boy development have been designed for a Unix environment, so setup on Windows is not fully straightfoward.  However, it’s possible to install an environment that will provide everything we need.</p>
+<p>On Windows 10 and Windows 11, your best bet is <a href="https://docs.microsoft.com/en-us/windows/wsl">WSL</a>, which is a method for running a Linux distribution within Windows.
+Install WSL, then a distribution of your choice (pick Ubuntu if unsure), and then follow these steps again, but for the Linux distribution you installed.</p>
 <p>In alternativa a WSL, si può usare <a href="https://www.msys2.org">MSYS2</a> o <a href="https://www.cygwin.com">Cygwin</a>; per poi consultare le istruzioni per l’installazione di Windows di [RGBDS] (https://rgbds.gbdev.io/install).
 Per quanto ne so, entrambi dovrebbero fornire una versione sufficientemente aggiornata di GNU Make.</p>
 <div class="box tip">
@@ -387,10 +387,10 @@ <h2 id="rgbasm-e-rgblink"><a class="header" href="#rgbasm-e-rgblink">RGBASM e RG
 <p>Quindi: Codice sorgente → <code>rgbasm</code> → File oggetto → <code>rgblink</code> → ROM, giusto?
 Beh, non esattamente.</p>
 <h2 id="rgbfix"><a class="header" href="#rgbfix">RGBFIX</a></h2>
-<p>RGBLINK produce sì una ROM, ma se la provassimo su un GameBoy non funzionerebbe.
-Nelle ROM deve sempre essere presente qualcosa chiamato <em>header</em>:
-questa sezione contiene <a href="https://gbdev.io/pandocs/The_Cartridge_Header.html">informazioni sulla ROM</a>, come il nome del gioco, il nome dell’autore, se sia compatibile con il GameBoy Color ed altro.
-Per il momento abbiamo impostato tutti i valori a zero nel programma per semplicità, ma ne riparleremo nella seconda parte del tutorial.</p>
+<p>RGBLINK does produce a ROM, but it’s not quite usable yet.
+See, actual ROMs have what’s called a <em>header</em>.
+It’s a special area of the ROM that contains <a href="https://gbdev.io/pandocs/The_Cartridge_Header.html">metadata about the ROM</a>; for example, the game’s name, Game Boy Color compatibility, and more.
+For simplicity, we defaulted a lot of these values to 0 for the time being; we’ll come back to them in Part Ⅱ.</p>
 <p>However, the header contains three crucial fields:</p>
 <ul>
 <li>The <a href="https://gbdev.io/pandocs/The_Cartridge_Header.html#0104-0133--nintendo-logo">Nintendo logo</a>,</li>

part1/setup.html

@@ -235,9 +235,9 @@ <h4 id="linux"><a class="header" href="#linux">Linux</a></h4>
 <p>Once RGBDS is installed, open a terminal and run <code>make --version</code> to check your Make version (which is likely GNU Make).</p>
 <p>If <code>make</code> cannot be found, you may need to install your distribution’s <code>build-essentials</code>.</p>
 <h3 id="windows"><a class="header" href="#windows">Windows</a></h3>
-<p>The sad truth is that Windows is a terrible OS for development; however, you can install environments that solve most issues.</p>
-<p>On Windows 10, your best bet is <a href="https://docs.microsoft.com/en-us/windows/wsl">WSL</a>, which sort of allows running a Linux distribution within Windows.
-Install WSL 1 or WSL 2, then a distribution of your choice, and then follow these steps again, but for the Linux distribution you installed.</p>
+<p>The modern tools we’ll be using for Game Boy development have been designed for a Unix environment, so setup on Windows is not fully straightfoward.  However, it’s possible to install an environment that will provide everything we need.</p>
+<p>On Windows 10 and Windows 11, your best bet is <a href="https://docs.microsoft.com/en-us/windows/wsl">WSL</a>, which is a method for running a Linux distribution within Windows.
+Install WSL, then a distribution of your choice (pick Ubuntu if unsure), and then follow these steps again, but for the Linux distribution you installed.</p>
 <p>If WSL is not an option, you can use <a href="https://www.msys2.org">MSYS2</a> or <a href="https://www.cygwin.com">Cygwin</a> instead; then check out <a href="https://rgbds.gbdev.io/install">RGBDS’ Windows install instructions</a>.
 As far as I’m aware, both of these provide a sufficiently up-to-date version of GNU Make.</p>
 <div class="box tip">

part1/toolchain.html

@@ -222,7 +222,7 @@ <h2 id="rgbasm-and-rgblink"><a class="header" href="#rgbasm-and-rgblink">RGBASM
 <p>So: Source code → <code>rgbasm</code> → Object files → <code>rgblink</code> → ROM, right?
 Well, not exactly.</p>
 <h2 id="rgbfix"><a class="header" href="#rgbfix">RGBFIX</a></h2>
-<p>RGBLINK does produces a ROM, but it’s not quite usable yet.
+<p>RGBLINK does produce a ROM, but it’s not quite usable yet.
 See, actual ROMs have what’s called a <em>header</em>.
 It’s a special area of the ROM that contains <a href="https://gbdev.io/pandocs/The_Cartridge_Header.html">metadata about the ROM</a>; for example, the game’s name, Game Boy Color compatibility, and more.
 For simplicity, we defaulted a lot of these values to 0 for the time being; we’ll come back to them in Part Ⅱ.</p>

print.html

@@ -293,9 +293,9 @@ <h4 id="linux"><a class="header" href="#linux">Linux</a></h4>
 <p>Once RGBDS is installed, open a terminal and run <code>make --version</code> to check your Make version (which is likely GNU Make).</p>
 <p>If <code>make</code> cannot be found, you may need to install your distribution’s <code>build-essentials</code>.</p>
 <h3 id="windows"><a class="header" href="#windows">Windows</a></h3>
-<p>The sad truth is that Windows is a terrible OS for development; however, you can install environments that solve most issues.</p>
-<p>On Windows 10, your best bet is <a href="https://docs.microsoft.com/en-us/windows/wsl">WSL</a>, which sort of allows running a Linux distribution within Windows.
-Install WSL 1 or WSL 2, then a distribution of your choice, and then follow these steps again, but for the Linux distribution you installed.</p>
+<p>The modern tools we’ll be using for Game Boy development have been designed for a Unix environment, so setup on Windows is not fully straightfoward.  However, it’s possible to install an environment that will provide everything we need.</p>
+<p>On Windows 10 and Windows 11, your best bet is <a href="https://docs.microsoft.com/en-us/windows/wsl">WSL</a>, which is a method for running a Linux distribution within Windows.
+Install WSL, then a distribution of your choice (pick Ubuntu if unsure), and then follow these steps again, but for the Linux distribution you installed.</p>
 <p>If WSL is not an option, you can use <a href="https://www.msys2.org">MSYS2</a> or <a href="https://www.cygwin.com">Cygwin</a> instead; then check out <a href="https://rgbds.gbdev.io/install">RGBDS’ Windows install instructions</a>.
 As far as I’m aware, both of these provide a sufficiently up-to-date version of GNU Make.</p>
 <div class="box tip">
@@ -387,7 +387,7 @@ <h2 id="rgbasm-and-rgblink"><a class="header" href="#rgbasm-and-rgblink">RGBASM
 <p>So: Source code → <code>rgbasm</code> → Object files → <code>rgblink</code> → ROM, right?
 Well, not exactly.</p>
 <h2 id="rgbfix"><a class="header" href="#rgbfix">RGBFIX</a></h2>
-<p>RGBLINK does produces a ROM, but it’s not quite usable yet.
+<p>RGBLINK does produce a ROM, but it’s not quite usable yet.
 See, actual ROMs have what’s called a <em>header</em>.
 It’s a special area of the ROM that contains <a href="https://gbdev.io/pandocs/The_Cartridge_Header.html">metadata about the ROM</a>; for example, the game’s name, Game Boy Color compatibility, and more.
 For simplicity, we defaulted a lot of these values to 0 for the time being; we’ll come back to them in Part Ⅱ.</p>