From 2bcb5a97826fb3cf05ecce77b4645d4649c9b62f Mon Sep 17 00:00:00 2001
From: lawgicau <lawgicau@gmail.com>
Date: Sat, 17 Apr 2021 10:57:56 +1000
Subject: [PATCH] Typos

---
 calibration.html | 4 ++--
 contact.html     | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/calibration.html b/calibration.html
index 3da670a..90798da 100644
--- a/calibration.html
+++ b/calibration.html
@@ -38,7 +38,7 @@
             <p>The gcode generated by this page has the following general characteristics:</p>
             <ul>
                 <li>Sliced for Marlin firmware, although in most cases will still be compatible with other firmwares.</li>
-                <li>1.75mm filament (However <b>M221 S38</b> for 2.85 mm filament and <b>M221 S34</b> for 3.0 mm filament can be appiled in the custom start gcode field as compensation)</b></li>
+                <li>1.75mm filament (However <b>M221 S38</b> for 2.85 mm filament and <b>M221 S34</b> for 3.0 mm filament can be applied in the custom start gcode field as compensation)</b></li>
                 <li>0.2mm layer height</li>
                 <li>0.4mm nozzle</li>
                 <li>Base feedrate of 60mm/sec</li>
@@ -499,7 +499,7 @@
         </div>
         <h2>Can I use this flow value in the other tests on this site?</h2>
         <p>The short answer is: not really.</p>
-        <p>The gcode generators on this site work by using javacsript to modify source gcode originally created by Simplify3D. However, when you completed the calibration test above, you sliced your own gcode, making your own baseline and then making a flow adjustment relative to that. Therefore, this test is unique from the others on this site which is why the flow rate doesn't necessarily translate.</p>
+        <p>The gcode generators on this site work by using javascript to modify source gcode originally created by Simplify3D. However, when you completed the calibration test above, you sliced your own gcode, making your own baseline and then making a flow adjustment relative to that. Therefore, this test is unique from the others on this site which is why the flow rate doesn't necessarily translate.</p>
         <p>Let's say your old flow rate was 100% and you have tested and corrected this to 96%. The gcode on this site originally had a flow rate of 90% when sliced, so applying your 96% to that gives a final result of 86.4%, not 96%. Your slicer profile settings will also be different in other ways, which further complicates matters. Therefore, there is not a straightforward correlation between your slicer and my gcode generators.</p>
         <p>The aim of the site is to discover ideal settings you can apply to your own slicer profile, not to optimise the gcode created by the generators. Keep this in mind and focus on the aim of each test, rather than the general print quality.</p>
         <p>If you are experiencing significant over or under extrusion that prevents you from using the tests properly, by using the custom start gcode function on this site you can optionally issue an <a href="https://marlinfw.org/docs/gcode/M221.html" target="_blank">M221</a> to override the values in the generatored gcode. For example, using <b>M221 S90</b> would tell the firmware to only extrude 90% of what the gcode asks for. This is an easy method for making a quick correction that will alow the tests to complete successfully.</p>        
diff --git a/contact.html b/contact.html
index d181697..77fd476 100644
--- a/contact.html
+++ b/contact.html
@@ -12,7 +12,7 @@
     <ul>
         <li>I don’t offer personal technical support, paid or otherwise, to the general public, Patrons, anyone. Please do send such requests, you will not receive a reply.</li>
         <li>Feel free to request or suggest a video, but there are several boxes that much be ticked for me to make a video. Just because a topic is important to one person, there is no guarantee it will appeal to or be helpful for a wider audience. If I receive frequent requests from a variety of people on a given topic, the chances of a video increase.</li>
-        <li>I don’t do any paid/sponsored videos. That includes manufacturers of channel relevant products making payment or unrelated spomnsored segements (VPNs, etc). Independence is key in delivering an unbiased and honest opinion. Products are often provided for free for review/testing and this is communicated in the video and the video description. Any contact offering payment or financial incentive will be ignored.</li>
+        <li>I don’t do any paid/sponsored videos. That includes manufacturers of channel relevant products making payment or unrelated sponsored segements (VPNs, etc). Independence is key in delivering an unbiased and honest opinion. Products are often provided for free for review/testing and this is communicated in the video and the video description. Any contact offering payment or financial incentive will be ignored.</li>
         <li>I am not interested in joining any partnership programs for ‘influencers’/content creators. I believe in creating the best videos I can and letting the channel grow naturally.</li>
         <li>In requesting a review, please be aware of my review policy. This document has been created for transparency over time frames and expectations, and to firmly establish my loyalty is to my viewers above all else. <a href="reviewpolicy.html"><b>Review Policy</b></a></li>
         <li>Please try to give concrete details about your product or service. Too often I receive a vague request for a collaboration or review with no actual information. Please link to text/images/video that communicate your product adequately.</li>