diff --git a/docs/OTA.md b/docs/OTA.md
index 70b74c2..5f9795d 100644
--- a/docs/OTA.md
+++ b/docs/OTA.md
@@ -18,7 +18,7 @@ This is because HomeSpan checks that a sketch has been compiled with OTA partiti
 
 * The name of the device HomeSpan uses for OTA is the same as the name you assigned in your call to `homeSpan.begin()`.  If you have multiple devices you intend to maintain with OTA, use `homeSpan.begin()` to give them each different names so you can tell them apart when selecting which one to connect to from the Arduino IDE.
 
-* Use the `homeSpan.setSketchVersion()` method to set a version name or number for your sketch.  If specified, HomeSpan will include the sketch version name/number as part of its HAP MDNS broadcast.  This allows you determine which version of a sketch is running on a remote HomeSpan device, even if you can't plug it into a serial port for use with the Arduino Serial Monitor.  In addition to the sketch version name/number, HomeSpan also broadcasts two other useful fields: the version number of the HomeSpan library used when the sketch was compiled, and field indicating whether or not OTA is enabled for the sketch.  See [HomeSpan MDNS](MDNS.md) for details on this broadcast and how to browse the data.
+* Use the `homeSpan.setSketchVersion()` method to set a version name or number for your sketch.  If specified, HomeSpan will include the sketch version name/number as part of its HAP MDNS broadcast.  This allows you determine which version of a sketch is running on a remote HomeSpan device, even if you can't plug it into a serial port for use with the Arduino Serial Monitor.  In addition to the sketch version name/number, HomeSpan also broadcasts two other useful fields: the version number of the HomeSpan library used when the sketch was compiled, and a field indicating whether or not OTA is enabled for the sketch.  See [HomeSpan MDNS](MDNS.md) for details on this broadcast and how to browse its data.
 
 * Always test out a new sketch on a local device connected to your computer before uploading it to a remote device via OTA.  If the sketch doesn't operate as * expected, you can always upload the previous version, unless the new sketch causes crashes that continously reboot HomeSpan.  If HomeSpan can't run the OTA code, you won't be able to upload any sketches via OTA and you'll need to connect the device to a computer for programming via the serial port instead.