Rename to tools.nes

Let's continue with the good ol' tradition of being terrible at naming
things.

I have also renamed another project which was referenced here, so update
all references as well.

Signed-off-by: Miquel Sabaté Solà <[email protected]>

CONTRIBUTING.md

@@ -5,7 +5,7 @@ desired binaries/tests.
 ## Issue reporting
 
 I'm using Github in order to host the code. Thus, in order to report issues you
-can do it on its [issue tracker](https://github.com/mssola/ntools/issues). A
+can do it on its [issue tracker](https://github.com/mssola/tools.nes/issues). A
 couple of notes on reports:
 
 - Check that the issue has not already been reported or fixed in the `main`

README.md

@@ -1,5 +1,6 @@
-Utilities for NES/Famicom development. Note that this repository is under heavy
-development and it's **not** currently usable.
+Tools I have created to help with NES/Famicom development.
+
+**Note**: this is under heavy development and it's not currently usable.
 
 ## `nasm`
 
@@ -18,9 +19,9 @@ it like so:
 $ nasm -o awesome.nes awesome.s
 ```
 
-Last but not least, you can actually tell `nasm` to redirect the output to
-stdout instead with the `--stdout` flag. This is useful when debugging the
-binary format with another CLI tool. For example:
+Moreover, you can actually tell `nasm` to redirect the output to stdout instead
+with the `--stdout` flag. This is useful when debugging the binary format with
+another CLI tool. For example:
 
 ```
 $ nasm --stdout awesome.s | hexdump -C
@@ -48,10 +49,10 @@ for reference.
 
 ## `readrom`
 
-The `readrom` reads a given ROM file and shows all the information that can be
-gathered from it. For now this only applies to information on the header, but in
-the future we might want to add disassembling user-specified segments, for
-example.
+The `readrom` program reads a given ROM file and shows all the information that
+can be gathered from it. For now this only applies to information on the header,
+but in the future we might want to add disassembling user-specified segments,
+for example.
 
 ## License
 

tests/src/chr-ram.s

@@ -1,5 +1,5 @@
-;;; From https://github.com/mssola/NES which will be open sourced soon (pinky
-;;; promess!).
+;;; From https://github.com/mssola/code.nes which will be open sourced soon
+;;; (pinky promess!).
 
 .segment "HEADER"
     .byte 'N', 'E', 'S', $1A

tests/src/sprite.s

@@ -1,5 +1,5 @@
-;;; NOTE: taken from https://github.com/mssola/NES; which I will open source
-;;; sooner rather than later.
+;;; NOTE: taken from https://github.com/mssola/code.nes; which I will open
+;;; source sooner rather than later.
 ;;;
 ;; Show a sprite to the screen! This example also contains fully detailed
 ;; explanations on each section on how an NES game is initialized and stored.