Deploy rust-console/gba to github.com/rust-console/gba.git:master

docs/00-introduction/03-development-setup.html

@@ -226,7 +226,7 @@ for it in your <code>examples/</code> directory and then run the demo in an emul
 and see if it does what you expect.</li>
 <li>The file extension is important! It will work if you forget it, but <code>cargo xbuild</code> takes the inclusion of the extension as a flag to also compile
 dependencies with the same sysroot, so you can include other crates in your
-build. Well, creates that work in the GBA's limited environment, but you get
+build. Well, crates that work in the GBA's limited environment, but you get
 the idea.</li>
 </ul>
 </li>

docs/00-introduction/06-help_and_resources.html

@@ -174,7 +174,9 @@ easy on your data usage.</li>
 <li><a href="https://www.coranac.com/tonc/text/">TONC</a>: While GBATEK is basically just a
 huge tech specification, TONC is an actual <em>guide</em> on how to make sense of the
 GBA's abilities and organize it into a game. It's written for C of course, but
-it's a large</li>
+as a Rust programmer you should always be practicing your ability to read C
+code anyway. It's the programming equivalent of learning Latin because all the
+old academic books are written in Latin.</li>
 <li><a href="https://www.cs.rit.edu/%7Etjh8300/CowBite/CowBiteSpec.htm">CowBite</a>: This is
 more like GBATEK, and it's less complete, but it mixes in a little more
 friendly explanation of things in between the hardware spec parts.</li>

docs/print.html

@@ -288,7 +288,7 @@ for it in your <code>examples/</code> directory and then run the demo in an emul
 and see if it does what you expect.</li>
 <li>The file extension is important! It will work if you forget it, but <code>cargo xbuild</code> takes the inclusion of the extension as a flag to also compile
 dependencies with the same sysroot, so you can include other crates in your
-build. Well, creates that work in the GBA's limited environment, but you get
+build. Well, crates that work in the GBA's limited environment, but you get
 the idea.</li>
 </ul>
 </li>
@@ -543,7 +543,9 @@ easy on your data usage.</li>
 <li><a href="https://www.coranac.com/tonc/text/">TONC</a>: While GBATEK is basically just a
 huge tech specification, TONC is an actual <em>guide</em> on how to make sense of the
 GBA's abilities and organize it into a game. It's written for C of course, but
-it's a large</li>
+as a Rust programmer you should always be practicing your ability to read C
+code anyway. It's the programming equivalent of learning Latin because all the
+old academic books are written in Latin.</li>
 <li><a href="https://www.cs.rit.edu/%7Etjh8300/CowBite/CowBiteSpec.htm">CowBite</a>: This is
 more like GBATEK, and it's less complete, but it mixes in a little more
 friendly explanation of things in between the hardware spec parts.</li>