diff --git a/README.md b/README.md
index 526cec5..e0fd0cf 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
 
 This repository contains a patch for Commodore 64 Elite that drastically improves the quality of the graphics. It does this by removing flicker from the ship-drawing routines.
 
-You can clearly see the difference in the following clip. The patched version is on the left, and the original version is on the right:
+You can see the difference it makes in the following clip. The patched version is on the left, and the original version is on the right:
 
 https://user-images.githubusercontent.com/2428251/187879166-74e973e3-aa49-40e3-b629-45d68843c4c9.mp4
 
@@ -38,7 +38,7 @@ The game disks in this repository are very similar to those released on [Ian Bel
 
 The commentary is copyright © Mark Moxon. Any misunderstandings or mistakes in the documentation are entirely my fault.
 
-Huge thanks are due to the original authors for not only creating such an important piece of my childhood, but also for releasing the source code for us to play with. Also, a big thumbs up to Kroc Camen for his epic [Elite Harmless](https://github.com/Kroc/elite-harmless) project, which was a really useful reference when exploring the C64 binaries, and to the gurus in this [Lemon64 forum thread](https://www.lemon64.com/forum/viewtopic.php?t=67762&start=90) for their sage advice.
+Huge thanks are due to the original authors for not only creating such an important piece of my childhood, but also for releasing the source code for us to play with. Also, a big thumbs up to Kroc Camen for his epic [Elite Harmless](https://github.com/Kroc/elite-harmless) project, which is a really useful reference for anyone exploring the C64 binaries. Finally, thanks to the gurus in this [Lemon64 forum thread](https://www.lemon64.com/forum/viewtopic.php?t=67762&start=90) for their sage advice.
 
 You can find more information about my own Elite project in the [fully documented source code for Elite on the BBC Micro](https://www.bbcelite.com).
 
@@ -56,15 +56,15 @@ My hope is that the educational and non-profit intentions of this repository wil
 
 ## Playing flicker-free Commodore 64 Elite
 
-The flicker-free version of Commodore 64 Elite is available in two versions: PAL and NTSC. These are both based on the GMA86 release of Elite from 1986.
+To play the flicker-free version of Commodore 64 Elite, you need to download a disk image and load it into an emulator or a real machine. Just like the original game, the flicker-free version is available in two distinct flavours: PAL and NTSC.
 
-To play the patched game in an emulator or on a real machine, you can download disk images for both versions from the [flicker-free-disks](flicker-free-disks) folder, or just click the following links:
+* [Download flicker-free Commodore 64 Elite (PAL) as a .d64 disk image](https://github.com/markmoxon/c64-elite-flicker-free/raw/master/flicker-free-disks/c64-elite-flicker-free-pal.d64) - this is the best version to use for emulators and most European machines
 
-* [Download flicker-free Commodore 64 Elite (PAL) as a .d64 disk image](https://github.com/markmoxon/c64-elite-flicker-free/raw/master/flicker-free-disks/c64-elite-flicker-free-pal.d64)
+* [Download flicker-free Commodore 64 Elite (NTSC) as a .d64 disk image](https://github.com/markmoxon/c64-elite-flicker-free/raw/master/flicker-free-disks/c64-elite-flicker-free-ntsc.d64) - this is the best version to use for most machines from the Americas
 
-* [Download flicker-free Commodore 64 Elite (NTSC) as a .d64 disk image](https://github.com/markmoxon/c64-elite-flicker-free/raw/master/flicker-free-disks/c64-elite-flicker-free-ntsc.d64)
+[See here](http://unusedino.de/ec64/technical/misc/vic656x/pal-ntsc.html) for a brief technical summary on the differences between PAL and NTSC on the Commodore 64.
 
-These have been tested in the VICE emulator and a number of online emulators, but they should also work on a real machine. If you don't know which one to use, try the PAL version first, as that seems to be the default setting for most emulators.
+These images have been tested in the [VICE emulator](https://vice-emu.sourceforge.io) and in a number of online emulators, such as [C64 online](https://c64online.com/c64-online-emulator/) and [Virtual Consoles](https://virtualconsoles.com/online-emulators/c64/). They should also work on real machines. If you don't know which one to use, try the PAL version first, as that seems to be the default setting for most emulators. Both disk images are based on the GMA86 releases of Elite from 1986.
 
 Saved commander files should work in exactly the same way as in the original GMA86 version; the only changes in the patch are graphical, and they don't affect gameplay in any way.
 
@@ -72,11 +72,11 @@ Saved commander files should work in exactly the same way as in the original GMA
 
 ### A better algorithm
 
-The 1986 releases of the BBC Master and Apple II versions of Elite saw a marked improvement in the ship-drawing algorithm that seriously reduced flicker without slowing down the game.
+The 1986 releases of Elite on the BBC Master and Apple II show a marked improvement in the quality of the wireframe graphics when compared to earlier versions. This is down to an improved algorithm that seriously reduces flicker without slowing down the game.
 
-In the original 1984 and 1985 versions of Elite, such as those for the BBC Micro, Acorn Electron and Commodore 64, ships were animated on-screen by first erasing them entirely, and then redrawing them in their new positions. The improved algorithm in the BBC Master and Apple II versions is similar, but instead of erasing the entire ship and then redrawing a whole new ship, it erases one line of the old ship and immediately redraws one line of the new ship, repeating the process until the whole ship gets redrawn, one line at a time. This interleaving of the line-drawing process results in much smoother ship graphics, and without adding any extra steps, so it doesn't affect the game speed.
+In the original 1984 and 1985 versions of Elite, such as those for the BBC Micro, Acorn Electron and Commodore 64, ships are animated on-screen by first erasing them entirely, and then redrawing them in their new positions. The improved algorithm in the BBC Master and Apple II versions is similar, but instead of erasing the entire ship and then redrawing a whole new ship, it erases one line of the old ship and immediately redraws one line of the new ship, repeating this process until the whole ship gets redrawn, one line at a time. This interleaving of the line-drawing process results in much smoother ship graphics, and without adding any extra steps, so it doesn't affect the game speed.
 
-Note that this doesn't apply to Elite on Z80-based computers, such as the ZX Spectrum and Amstrad CPC. These were complete rewrites that have totally different drawing routines, and they don't appear to suffer from flicker.
+Note that this doesn't apply to Elite on Z80-based computers, such as the ZX Spectrum and Amstrad CPC. These were complete rewrites that have totally different drawing routines, and they didn't inherit the flicker of the original 6502 versions.
 
 For more information on the flicker-free algorithm, see these deep dives on [flicker-free ship drawing](https://www.bbcelite.com/deep_dives/flicker-free_ship_drawing.html) and [backporting the flicker-free algorithm](https://www.bbcelite.com/deep_dives/backporting_the_flicker-free_algorithm.html) in my BBC Micro Elite project.
 
@@ -88,21 +88,28 @@ https://user-images.githubusercontent.com/2428251/187880030-1ea634fa-5588-4724-9
 
 In order to patch Commodore 64 Elite to use the new flicker-free algorithm, we have to do the following:
 
-* Use c1451 to extract the game binaries from the original Commodore 64 .g64 disk images
+* Extract the game binaries from the original Commodore 64 .g64 disk image (using c1541 from the VICE emulator)
 
-* Use BeebAsm to assemble the additional code that's required for flicker-free ships (we use BeebAsm as the extra code is taken from the BBC Master version of Elite)
+* Assemble the additional code that's required for flicker-free ships (using BeebAsm as the extra code is taken from the BBC Master version of Elite)
 
-* Use Python to inject this new code into the game binaries and disable any copy protection on the original disk
+* Inject this new code into the game binaries and disable any copy protection code (using Python)
 
-* Use c1451 to create a new disk image containing the modified flicker-free binaries
+* Create a new disk image containing the modified flicker-free binaries (using c1541 once again)
 
-To find out more about the above steps, check out the following files, which contain lots of comments about how the process works:
+To find out more about the above steps, take a look at the following files, which contain lots of comments about how the process works:
 
-* The [build.sh](build.sh) script controls the build. Read this for an overview of the patching process, as described above.
+* The [`build.sh`](build.sh) script controls the build. Read this for an overview of the patching process.
 
-* The [elite-flicker-free.asm](src/elite-flicker-free.asm) file assembles and saves out a number of code binaries. These contain larger blocks of code that implement the flicker-free algorithm, which are saved as binary files that are ready to be injected into the game binary to implement the patch.
+* The [`elite-flicker-free.asm`](src/elite-flicker-free.asm) file is assembled by BeebAsm and produces a number of binary files. These contain the bulk of the code that implements the flicker-free algorithm. These code blocks are saved as binary files that are ready to be injected into the game binary to implement the patch.
 
-* The [elite-modify.py](src/elite-modify.py) script modifies the game binary and applies the patch. It does this by loading the binary into memory, decrypting it, patching it by injecting the output from BeebAsm, making a number of other modifications to the code, encrypting the modified code, and saving out the encrypted and modified version. It also disables any copy protection on the original disk.
+* The [`elite-modify.py`](src/elite-modify.py) script modifies the game binary and applies the patch. It does this by:
+
+  * Loading the main binary into memory
+  * Decrypting it
+  * Patching it by injecting the output from BeebAsm and making a number of other modifications to the code
+  * Encrypting the modified code
+  * Saving out the encrypted and modified binary
+  * Disabling any copy protection from the original disk
 
 The commentary in these files is best read alongside the code changes, which are described in detail in the article on [backporting the flicker-free algorithm](https://www.bbcelite.com/deep_dives/backporting_the_flicker-free_algorithm.html).
 
@@ -124,7 +131,7 @@ Given these, let's look at how to patch Commodore 64 Elite to get those flicker-
 
 ### Applying the patch
 
-The patching process is implemented by a bash script called `build.sh` in the root folder of the repository. If any of BeebAsm, Python or c1541 are not on your path, then you can either fix this, or you can edit the `$beebasm`, `$python` or `$c1541` variables in the first three lines of `build.sh` to point to their locations.
+The patching process is implemented by a bash script called [`build.sh`](build.sh) in the root folder of the repository. If any of BeebAsm, Python or c1541 are not on your path, then you can either fix this, or you can edit the `$beebasm`, `$python` or `$c1541` variables in the first three lines of `build.sh` to point to their locations.
 
 You also need to change directory to the repository folder (i.e. the same folder as `build.sh`), and make sure the `build.sh` script is executable, with the following:
 
@@ -139,9 +146,9 @@ All being well, doing the following:
 ./build.sh
 ```
 
-will produce two disk images in the `compiled-game-disks` folder. These disk images contain the patched game, one for PAL and one for NTSC, which you can then load into an emulator or real machine.
+will produce two disk images in the [`compiled-game-disks`](compiled-game-disks) folder. These disk images contain the patched game, one for PAL and one for NTSC, which you can then load into an emulator or real machine.
 
-The build process also verifies the results against binaries that are known to be correct, and BeebAsm log files and interim binaries are saved in the `work` folder. These are useful for debugging purposes.
+The build process also verifies the results against binaries that are known to be correct, which helps with debugging. Any BeebAsm log files and interim binaries are saved in the `work` folder during compilation, which can be useful if you want to investigate the modified binary files from each of the build steps.
 
 ---