--- a/spec/index-respec.html	Tue Dec 06 16:52:10 2011 +0100
+++ b/spec/index-respec.html	Tue Dec 06 18:23:41 2011 +0100
@@ -342,66 +342,17 @@
 <h1>Introduction</h1>
 
 <p>
-The WebID specification is designed to help alleviate the difficultly that
-remembering different logins, passwords and settings for websites has created.
-It is also designed to provide a universal and extensible mechanism to express
-public and private information about yourself. This section outlines the
-motivation behind the specification and the relationship to other similar
-specifications that are in active use today.
-</p>
-
-<section class='informative'>
-<h1>Motivation</h1>
-
-<p>
-It is a fundamental to the architecture of the Web that anyone - be they an individual and organisation, be  able to participate in publishing resources and enableing services available to all.
- This includes how one expresses their identity, public information and personal details to social networks, Web sites and services.
-</p>
-
-<p>
-Semantic Web vocabularies such as Friend-of-a-Friend (FOAF) permit distributed
-hyperlinked social networks to exist. This vocabulary, along with other
-vocabularies, allow one to add information and services protection to
-distributed social networks.
-</p>
-
-<p>
-One major criticism of open networks is that they seem to have no way of
-protecting the personal information distributed on the web or limiting
-access to resources. Few people are willing to make all their personal
-information public, many would like large pieces to be protected, making
-it available only to a selected group of agents. Giving access to
-information is very similar to giving access to services. There are many
-occasions when people would like services to only be accessible to
-members of a group, such as allowing only friends, family members,
-colleagues to post an article, photo or comment on a blog. How does one do
-this in a flexible way, without requiring a central point of
-access control?
-</p>
-
-<p>
-Using a process made popular by OpenID, we show how one can tie a User
-Agent to a URI by proving that one has write access to the URI.
-WebID is an authentication protocol which uses X.509
-certificates to associate a User Agent (Browser) to a Person identified
-via a URI.
-A WebID profile can also be used for OpenID, WebID provides a few additional
-features such as trust management via digital signatures, and free-form
-extensibility via RDF. By using the existing SSL certificate exchange
-mechanism, WebID integrates smoothly with existing Web browsers, including
-browsers on mobile devices. WebID also permits automated session login
-in addition to interactive session login. Additionally, all data is encrypted
-and guaranteed to only be received by the person or organization that was
-intended to receive it.
-</p>
-
+The WebID protocol enables secure, efficient and maximally user friendly authentication on the Web. 
+It enables People using a Web Brower to authenticate onto any site by simply clicking on one of the certificates proposed to them by their browser. These certificates can be created by any Web Site for their users in one click.
+The identity, known as the <tref>WebID</tref> is a URL pointing into a <tref>Profile Page</tref>, which any Social Network user is currently familiar with. These pointers into the Web then allow Web of trust based authorizations, where services can allow access to resource because of certain properties of an agent, such that the he is known by some relevant people.</p>
+<p>WebID authentication can also be used for automatic authentication by robots, such as web crawlers of linked data repositories, which could be agents working on behalf of users to help them in their daily tasks. WebID is not limited to Web Authentication, but can work with any TLS based protocol.</p>
+<section>
+<h1>Outline</h1>
+<p>This specification is divided in the following sections.</p>
+<p><a href="#introduction">This section</a> gives a high level overview of the WebId Protocol, and presents the organisation of the specification and the conventions used throughout the document.</p>
+<p><a href="#preconditions">Section 2</a> lists the preconditions that need to be in place for any authentication sequence to be successful: which include the creation of a <tref>WebID Profile</tref> and the creation of a <tref>WebID Certificate</tref></p>
+<p><a href="#the-webid-protocol">Section 3</a> on the WebID Protocol describes in detail how a server can authenticate a user.</p>
 </section>
-
-</section>
-
-<section>
-<h1>Preconditions</h1>
-
 <section>
 <h1>Terminology</h1>
 <dl>
@@ -414,8 +365,8 @@
 </dd>
 <dt><tdef>Subject</tdef></dt>
 <dd>The Subject is the Agent that is identified by the <tref>WebID</tref>.
-When used correctly it is the Subject who wishes to authenticate to a <tref>Service</tref>.
-When speaking of a particular agent, and in order to improve lisibility in this spec, we will name him <tref>Bob</tref>.
+When used legally it is the Subject who wishes to authenticate to a <tref>Service</tref>.
+We will name our princiap Subject <tref>Bob</tref> throughout the text, when this helps lisibility.
 The Subject is distinct from the <tref>Client</tref> which is used to connect to the <tref>Server</tref>.
 </dd>
 <dt><tdef>Client</tdef></dt>
@@ -537,6 +488,10 @@
 
 <p>The ex: namespace is a URI that refers to Bob's profile, where Bob is an imaginary charcter well known in security circles.</p>
 </section>
+</section>
+
+<section>
+<h1>Preconditions</h1>
 
 
 <section class='normative'>