diff --git a/xep-0332.xml b/xep-0332.xml
index b1273838..9904f02e 100644
--- a/xep-0332.xml
+++ b/xep-0332.xml
@@ -28,6 +28,12 @@
         <supersededby/>
         <shortname>NOT_YET_ASSIGNED</shortname>
         &peterwaher;
+  <revision>
+    <version>0.5.1</version>
+    <date>2020-03-31</date>
+    <initials>@sonnyp</initials>
+    <remark>Fix spelling error</remark>
+  </revision>
   <revision>
     <version>0.5</version>
     <date>2017-09-11</date>
@@ -133,7 +139,7 @@
     <section1 topic='Introduction' anchor='intro'>
         <p>
             Many documents have been written on how to transport XMPP datagrams using HTTP. The motivation behind such solutions has often been to be able to use XMPP in
-            scripting languages such as Java Script running in web browsers.
+            scripting languages such as JavaScript running in web browsers.
         </p>
         <p>
             But up to this point very little has been written about the reverse: How to transport HTTP methods and HTTP responses over an XMPP-based peer-to-peer network.
@@ -182,7 +188,7 @@
                 but is only one example of all types of HTTP-based communication one would desire to transport over XMPP.
             </li>
             <li>
-                &xep0124;: This specification handles XMPP-based communication over HTTP sessions (BOSH), allowing for instance, XMPP communication in java script using the
+                &xep0124;: This specification handles XMPP-based communication over HTTP sessions (BOSH), allowing for instance, XMPP communication in JavaScript using the
                 XML HTTP Request object. This is in some way the reverse of what this document proposes to do.
             </li>
             <li>