--- a/examples/eg-24-prov-o-html-examples/rdf/create/rdf/class_Involvement.ttl	Tue Jun 05 12:41:47 2012 -0400
+++ b/examples/eg-24-prov-o-html-examples/rdf/create/rdf/class_Involvement.ttl	Tue Jun 05 12:51:04 2012 -0400
@@ -5,20 +5,21 @@
 @prefix :     <http://example.com/> .
 
 # Although a domain extension (e.g. ':wasConductedBy') is not defined by PROV-O,
-# the relation between a surgery and an agent can be qualified
+# the relation between a surgery and an agent can still be qualified
 # by reusing prov:Involvement and one of its three subclasses 
 # (depending on the type of the instance involved):
 # AgentInvolvement, EntityInvolvement, and ActivityInvolement.
+
 my:wasConductedBy rdfs:subPropertyOf prov:wasAssociatedWith .
+
 :conductingSurgery_1
    a prov:Activity;
-   my:wasConductedBy :bob;  # This unqualified involvement is unknown in PROV, this would be a subproperty of wasAssocitedWith
+   my:wasConductedBy :bob;     # This unqualified involvement is unknown in PROV, this would be a subproperty of wasAssocitedWith
    prov:qualifiedAssociation [ # Even though PROV systems do not understand :wasConductedBy, 
-                                             # they can recognize that the unknonw relation is being qualified wtih hadRole.
-      a prov:Association,
+      a prov:Association,      # they can recognize that the unknonw relation is being qualified wtih hadRole.
         prov:AgentInvolvement, # Inferred
-        prov:Involvement;          # Inferred
-      prov:agent   :bob;            # The object of :wasConductedBy
+        prov:Involvement;      # Inferred
+      prov:agent   :bob;       # The object of :wasConductedBy
       prov:hadRole :Surgeon;
    ];
 .