From ba0934f8a89ffbe6583747f0cdfc8b34b9302e03 Mon Sep 17 00:00:00 2001
From: Jack Lukic <jack@quirky.com>
Date: Sat, 20 Apr 2013 13:48:03 -0400
Subject: [PATCH] module language

---
 docs/module.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/module.html b/docs/module.html
index 476de2651..de1f40b53 100755
--- a/docs/module.html
+++ b/docs/module.html
@@ -143,8 +143,8 @@
   </table>
   
   <h3>Exchanging Designs</h3>
-  <p>Semantic creates an exchange format for UI, by defining HTML structures and class names for UI elements that attempt to create a common language and make front end development <a href="http://instruct.westvalley.edu/lafave/DFW_present_tense.html">less prescriptive</a>.</p>
-  <p>Sharing a language for UI releases the burden from developers at being a naming authorities in their own projects. We can share a common visual vocabulary as a community, and design interchangeable interface elements without having to rely on the prescribed standards of a single developer.</p>
+  <p>Semantic defines HTML structures and class names for UI elements that attempt to create a common vernacular to make front end development <a href="http://instruct.westvalley.edu/lafave/DFW_present_tense.html">less prescriptive</a>.</p>
+  <p>Sharing language for UI releases the burden from developers at making arbitrary decisions, like naming conventions, in their own projects, and opens up the ability to swap website designs without having to restructure your codebase.</p>
   
   <h3>What's in an Element?</h3>
   <p>UI elements definitions are made of 4 parts: