--- GLUE-2.0-security-0.3	2008-11-21 10:26:32.000000000 +0100
+++ GLUE-2.0-security-0.4	2008-11-21 10:33:51.000000000 +0100
@@ -1,7 +1,8 @@
-This version 0.3:
+This version 0.4:
   v0.1 initial version
   v0.2 with changes from Maarten.
   v0.3 with changes from Stephen.
+  v0.4 with changes from Maarten.
 
 
 
@@ -31,7 +32,7 @@
 
 9.1.1 Confidentiality.
 
-GLUE information schema contains information that may be personal or
+The GLUE conceptual model contains information that may be personal or
 confidential in nature.  Contact details and indications of end-user
 activity may fall into this category.
 
@@ -45,8 +46,8 @@
 
 The information within GLUE has many potential uses, from operational
 to accounting.  How accurate the information is may depend on many
-factors, including the integrity software agents that publish data and
-the transport used to propagate information.
+factors, including the integrity of software agents that publish data
+and the transport used to propagate information.
 
 The software used to provide an information service may cache GLUE
 information.  If so, these caches provide additional points where data
@@ -55,9 +56,10 @@
 
 9.1.3 Peer Entity authentication.
 
-No explicit description of the agents that publish GLUE information is
-included within the GLUE schema.  This prevents authentication
-information from being included within the abstract model.
+No explicit description of the agents that publish information is
+included within the GLUE conceptual model.  This prevents
+authentication information from being included within the abstract
+model.
 
 In general, support for peer-entity authentication is delegated to the
 concrete data model or the underpinning software.  In many cases the
@@ -134,10 +136,10 @@
 
 9.4.1 Eavesdropping
 
-Some information described in the GLUE schema may be sensitive in
-nature; this may include contact details and descriptions of user
-activity.  Appropriate care should be taken to prevent unintended
-access or disclosure to an unintended audience.
+Some information described in the GLUE conceptual model may be
+sensitive in nature; this may include contact details and descriptions
+of user activity.  Appropriate care should be taken to prevent
+unintended access or disclosure to an unintended audience.
 
 
 9.4.2 Replay
@@ -147,7 +149,7 @@
 
 If a system implementing the GLUE 2.0 conceptual model is susceptible
 to a replay attack then it is possible for part (possibly all) of the
-information in the conceptial model to be reverted to some previous
+information in the conceptual model to be reverted to some previous
 state as seen by some (possible all) end users.  Please note that this
 is a specific case of the more general modification attack.
 
@@ -174,7 +176,7 @@
 further attacks.
 
 Underlying concrete models and software implementations should ensure
-that an agent's ability to insert information is limited and
+that any agent's ability to insert information is limited and
 appropriate.
 
 
@@ -198,13 +200,13 @@
 The ability for an agent to modify information stored in an
 information service is key to providing accurate information.
 However, concrete data models and software implementation should place
-limits on agents so the agent's ability to modify information is
-controlled and appropriate.
+limits on agents' ability to modify information is controlled and
+appropriate.
 
 
 9.4.6 Man-in-the-middle.
 
-For a system implementing the GLUE 2.0 information mode, a successful
+For a system implementing the GLUE conceptual model, a successful
 man-in-the-middle attack may lead to arbitrary modification of data
 (see 9.4.5).  It may also allow deleting existing data (see 9.4.4) or
 adding additional data (see 9.4.3).  This may have severe influence on