From 16e36ef77b37ba2b11653308a9934b79eebbe9dd Mon Sep 17 00:00:00 2001
From: IanLalonde <46567178+IanLalonde@users.noreply.github.com>
Date: Tue, 9 Apr 2019 16:13:41 -0400
Subject: [PATCH] Update README.md

---
 gcodeextractor/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcodeextractor/README.md b/gcodeextractor/README.md
index af689da..fd1054c 100644
--- a/gcodeextractor/README.md
+++ b/gcodeextractor/README.md
@@ -41,7 +41,7 @@ We then create a sequence of coordinates for the tool to follow to cover all the
 
 The last file is GcodeBuilder.py, it transforms the sequence of point into a standard gcode file. It does so by changing the coordinates in pixels, into coordinates in mm according to the dimensions of the pcb. If the coordinates are (-1,-1), this means the sequence has finished a path and the tool should not be working until it gets to the next coordinates. The gcode file also starts with a header and ends with a footer to add some configurations and a homing.
 
-### tests
+### Tests
 
 For path.py's function, we tested the three functions with small matrix of 0's and 1's and wrote the expected results manually to compare if the functions returned what we expected. We also tested if the algorithms would still work if it had to write or read out of bound of the image, which is verified in the algorithms.