From 80463a4ddb9e68055d8b46b8c61b485b72732890 Mon Sep 17 00:00:00 2001 From: Sonny Piers Date: Fri, 27 Mar 2020 11:39:29 +0100 Subject: [PATCH] XEP-0332: Fix spelling of JavaScript --- xep-0332.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0332.xml b/xep-0332.xml index b1273838..7a012ff4 100644 --- a/xep-0332.xml +++ b/xep-0332.xml @@ -133,7 +133,7 @@

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.

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 +182,7 @@ but is only one example of all types of HTTP-based communication one would desire to transport over XMPP.

  • - &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.