From d48712ce8b699feae0d6af64512ef0b6761fa4dc Mon Sep 17 00:00:00 2001
From: James <j@j-w.co>
Date: Wed, 8 Dec 2021 17:12:11 +1100
Subject: [PATCH] Update README.md

---
 README.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index c420268..00e8c7b 100644
--- a/README.md
+++ b/README.md
@@ -10,10 +10,12 @@ Or place ```/path/to/laydient.py``` in the Post-processing scripts section in Pr
 it searches for ```LAYER_CHANGE``` in the input gcode, counts them, then generates a gradient with that number of steps. Then it searches again and inserts toolchanges into the gcode at the appropriate layers. Finally, it outputs the code as ```input-filename_gradient.gcode``` into the source directory.
 
 ### toolchanges
-This script inserts the following:
-``` G10
+This script inserts the following gcode for each tool change:
+```
+G10
 T#
-G11 ```
+G11
+```
 
 This retracts the filament, swaps the tool, then unretracts. The rest of the toolchange/purge is up to your firmware.