--- a/spec/latest/index.html	Sun Sep 11 17:20:05 2011 -0400
+++ b/spec/latest/index.html	Sun Sep 11 21:09:19 2011 -0400
@@ -616,8 +616,9 @@
   fashion. This is described later in this document. </p>
 
 <p>
-  The semantic web uses a special type of document called a
-  <em>Web Vocabulary</em> to define <tref>term</tref>s.
+  The semantic web uses a special type of machine-readable document called a
+  <tdef>Web Vocabulary</tdef> to define <tref>term</tref>s that are then used
+  to describe concepts and "things" in the world.
   Typically, these Web Vocabulary documents have <tref>prefix</tref>es associated
   with them and contain a number of <tref>term</tref> declarations. A
   <tdef>prefix</tdef>, like a <tref>term</tref>, is a short word that expands
@@ -632,7 +633,7 @@
 <p>
 
 <p>For example, the IRI <code>http://xmlns.com/foaf/0.1/</code>
-specifies a Web Vocabulary which may be represented using the
+specifies a <tref>Web Vocabulary</tref> which may be represented using the
 <code>foaf</code> <tref>prefix</tref>. The <code>foaf</code> Web Vocabulary
 contains a term called <strong>name</strong>. If you join the
 <code>foaf</code> <tref>prefix</tref> with the <strong>name</strong> suffix,
@@ -1355,7 +1356,7 @@
     <tref>prefix</tref> mechanism is introduced.</p>
   <p>
     A <tdef>prefix</tdef> is a compact way of expressing a base 
-    <tref>IRI</tref> to a Web vocabulary.
+    <tref>IRI</tref> to a <tref>Web Vocabulary</tref>.
     Generally, these prefixes are used by concatenating the <em>prefix</em> and 
     a <em>term</em> separated by a colon (<code>:</code>).
     The prefix is a short string that identifies a particular Web vocabulary.
@@ -1379,7 +1380,7 @@
     remember <code>foaf:name</code> than it is to remember
     <code>http://xmlns.com/foaf/0.1/name</code>. The use of prefixes also
     ensures that a context document does not have to be updated in lock-step
-    with an externally defined Web Vocabulary. Without prefixes, a developer
+    with an externally defined <tref>Web Vocabulary</tref>. Without prefixes, a developer
     would need to keep their application context terms in lock-step with an
     externally defined Web Vocabulary. Rather, by just declaring the
     Web Vocabulary prefix, one can use new terms as they're declared
@@ -4165,8 +4166,8 @@
 
 <p>Developers would also benefit by allowing other vocabularies to be used
 automatically with their JSON API. There are over 200
-Vocabulary Documents that are available for use on the Web today. Some
-of these vocabularies are:
+<tref>Web Vocabulary</tref> Documents that are available for use on the Web 
+today. Some of these vocabularies are:
 </p>
 
 <ul>
@@ -4222,7 +4223,7 @@
 is detected. In the example above, "<code>myvocab:personality</code>" would
 expand to "<code>http://example.org/myvocab#personality</code>".</p>
 
-<p>This mechanism is a short-hand, called a Web Vocabulary <tref>prefix</tref>, 
+<p>This mechanism is a short-hand, called a <tref>Web Vocabulary</tref> <tref>prefix</tref>, 
 and provides developers an unambiguous way to map any JSON value to RDF.<p>
 
 </section>