From 7ef6dbe89a851a16d8204bbe084cdb4a2a05e864 Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@stpeter.im>
Date: Tue, 29 May 2012 10:18:56 -0600
Subject: [PATCH] typo

---
 xep-0300.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 mode change 100644 => 100755 xep-0300.xml

diff --git a/xep-0300.xml b/xep-0300.xml
old mode 100644
new mode 100755
index fd0af94d..27b33957
--- a/xep-0300.xml
+++ b/xep-0300.xml
@@ -56,7 +56,7 @@
 </header>
 
 <section1 topic='Introduction' anchor='intro'>
-  <p>Various XMPP extensions make use of cryptographic hash functions, but they do so in different ways (e.g., some define XML elements and some define XML attributes) and often mandate support for different algorthms. The lack of a consistent approach to the use of cryptographic hash functions in XMPP extensions can lead to interoperability problems and security vulnerabilities. Therefore, this document recommends a common approach and XML element that can be re-used in any XMPP protocol extension.</p>
+  <p>Various XMPP extensions make use of cryptographic hash functions, but they do so in different ways (e.g., some define XML elements and some define XML attributes) and often mandate support for different algorithms. The lack of a consistent approach to the use of cryptographic hash functions in XMPP extensions can lead to interoperability problems and security vulnerabilities. Therefore, this document recommends a common approach and XML element that can be re-used in any XMPP protocol extension.</p>
 </section1>
 
 <section1 topic='Requirements' anchor='reqs'>