diff --git a/io/serialport/README.md b/io/serialport/README.md
index 73266ff3..dbadfd3f 100644
--- a/io/serialport/README.md
+++ b/io/serialport/README.md
@@ -96,7 +96,7 @@ changes the serial port and the configuration on the fly.
 <p>When the `enable` property is not present, it will default to `true`</p>
 <p>
 `{"enable":true}` or `{"enable":false}` will start or stop the communication.</p>
-<p> If `enable` is passed along wiht other parameters, the configuration will be changed and either be started or just stopped and ready to start depending on the value.  </p>
+<p> If `enable` is passed along wiht other parameters, the configuration will be changed and either be started or just be ready to be started(ie. stopped ) depending on its value.  </p>
 
 **Here is the serial control node usage example flow**
 
diff --git a/io/serialport/locales/en-US/25-serial.html b/io/serialport/locales/en-US/25-serial.html
index a2836be5..db0de1b8 100644
--- a/io/serialport/locales/en-US/25-serial.html
+++ b/io/serialport/locales/en-US/25-serial.html
@@ -136,7 +136,7 @@
         <p>When the <code>enable</code> property is not present, it will default to <code>true</code></p>
         <p>
             <code>{"enable":true}</code> or <code>{"enable":false}</code> will start or stop the communication.</p>
-            <p> If <code>enable</code> is passed along wiht other parameters, the configuration will be changed and either be started or just stopped and ready to start depending on the value.  </p>
+            <p> If <code>enable</code> is passed along with other parameters, the configuration will be changed and either be started or just be ready to be started(ie. stopped ) depending on its value.  </p>
 
     <h3>Outputs</h3>
     <p><code>msg.payload</code> is the response. It contains the serial port configuration</p>