diff --git a/INDEX.md b/INDEX.md
index 5736c12..1864fc1 100644
--- a/INDEX.md
+++ b/INDEX.md
@@ -1,6 +1,5 @@
 ---
-title: wwwrite
-author: gauthiier
+title: WWWRITING WITH WIT
 bibliography: wwwrite.bib
 cover: img/DSP6.png
 ---
@@ -16,14 +15,14 @@ The idea in compiling this site-lesson is two fold:
 
 (1) Present an alternative to the use of proprietary software for writing academic texts:
 
->Considering the hegemonic use of proprietary software to write academic and non-academic texts (MS Word, Google Docs, Apple Pages, etc.) it is important to underline alternatives as these software not only “hide” their inner workings to scrutiny but most importantly may fall short in providing writers with adequate functionality required in writing academic texts [^1]. Obfuscation is impractical (and problematic) obviously so for academics in the Humanities. 
+	Considering the hegemonic use of proprietary software to write academic and non-academic texts (MS Word, Google Docs, Apple Pages, etc.) it is important to underline alternatives as these software not only “hide” their inner workings to scrutiny but most importantly may fall short in providing writers with adequate functionality required in writing academic texts [^1]. Obfuscation is impractical (and problematic) obviously so for academics in the Humanities. 
 
 
->We believe in texts that we can read, that is, we will utilise (as much as possible) software which is made “open” for us to read the source code and formats that are [human-readable](https://en.wikipedia.org/wiki/Human-readable_medium) as opposed to solely [machine-readable](https://en.wikipedia.org/wiki/Machine-readable_data). Hence, throughout the lessons, we will be inspecting files and writing ones that are augmented with special codes that machines can understand. This idea of writing "meta-data" into the text or more precisely _markup_ text in a file is very important in making sure the text is human _and_ machine readable. 
+	We believe in texts that we can read, that is, we will utilise (as much as possible) software which is made “open” for us to read the source code and formats that are [human-readable](https://en.wikipedia.org/wiki/Human-readable_medium) as opposed to solely [machine-readable](https://en.wikipedia.org/wiki/Machine-readable_data). Hence, throughout the lessons, we will be inspecting files and writing ones that are augmented with special codes that machines can understand. This idea of writing "meta-data" into the text or more precisely _markup_ text in a file is very important in making sure the text is human _and_ machine readable. 
 
 (2) Offer a glimpse into methods, practices and systems of software writing:
 
->As you may already know, writing software is primarily a textual-based practice. Writing code is all about text, keyboards, text editors, line count, syntax and the likes. Hence an important amount of systems and technologies have been devised for the composition of software (as text). From syntax highlighting to version control, these systems have a long history and can possibly provide academic writers with powerful literary tools that can enable them to bolster their prose.[^2] In exposing (and historicising) these systems our objective is for the reader to relate to modern software writing systems not as merely a tool but as system with a culture. In no way we expect readers to become "programmers", far from this, we would rather present them the basics of writing text using (modern) computer systems while hoping that they'll develop a critical stance on these systems' genesis, conditions, limitations and capabilites.  
+	As you may already know, writing software is primarily a textual-based practice. Writing code is all about text, keyboards, text editors, line count, syntax and the likes. Hence an important amount of systems and technologies have been devised for the composition of software (as text). From syntax highlighting to version control, these systems have a long history and can possibly provide academic writers with powerful literary tools that can enable them to bolster their prose.[^2] In exposing (and historicising) these systems our objective is for the reader to relate to modern software writing systems not as merely a tool but as system with a culture. In no way we expect readers to become "programmers", far from this, we would rather present them the basics of writing text using (modern) computer systems while hoping that they'll develop a critical stance on these systems' genesis, conditions, limitations and capabilites.  
 
 # Scheme
 
@@ -31,27 +30,27 @@ The current site is segmented in six lessons covering the (very) basics of writi
 
 * [Lesson 1: Text Encoding](/)
 
->Covers fundamentals of representation of text looking up how text is encoded/decoded as data.
+	Covers fundamentals of representation of text looking up how text is encoded/decoded as data.
 
-* [Lesson 2: Terminal](/)
+* [Lesson 2: "Terminal" or Cmd Prompt](/)
 
->Presents how one can manipulate files and issue computing commands using what is known as a terminal.
+	Presents how one can manipulate files and issue computing commands using what is known as a terminal.
 
 * [Lesson 3: Markup / Markdown](/)
 
->Introduces a markup language ([Markdown](http://daringfireball.net/projects/markdown/)) that is used to format and annotate text.
+	Introduces a markup language ([Markdown](http://daringfireball.net/projects/markdown/)) that is used to format and annotate text.
 
-* [Lesson 4: (Text) Processor](/)
+* [Lesson 4: (Text/Document) Processor](/)
 
->Introduces a text / document processor ([Pandoc](http://johnmacfarlane.net/pandoc/)) which converts files written in a format into another.
+	Introduces a text / document processor ([Pandoc](http://johnmacfarlane.net/pandoc/)) which converts files written in a format into another.
 
 * [Lesson 5: Bibliographer](/)
 
->Looks at how to compile and maintain a bibliography using open source software ([Zotero](https://www.zotero.org)) and export references into a document
+	Looks at how to compile and maintain a bibliography using open source software ([Zotero](https://www.zotero.org)) and export references into a document
 
 * [Lesson 6: Styling](/)
 
->Discuss how to style (colour, margins, cover image, etc.) a given output from the text / document processor
+	Discuss how to style (colour, margins, cover image, etc.) a given output from the text / document processor
 
 As a final note worth mentioning (before delving further): all the lessons of this site, including this page, have been (are) written using the aforementioned encodings and systems. Hence, for the curious, the reader can lookup the files, modify and compile them to bootstrap their writing project. Whatever you see on this site is made available for you to read, modify, etc.
 
diff --git a/style/style.css b/style/style.css
index 01b242c..751ab56 100644
--- a/style/style.css
+++ b/style/style.css
@@ -107,9 +107,16 @@ p {}
 
 /* Main container for the whole content / body section -- html5 */
 content {
-    width: 70%;
-    display: inline-block;
+    padding: 0.9em;
+    max-width: 45em;    
+    display: block;
+    text-align: justify;
     margin: auto;
+    word-wrap: break-word;
+}
+
+.references {
+    text-align: left;
 }
 
 blockquote
diff --git a/style/template.html5 b/style/template.html5
index 76babb1..3b50433 100644
--- a/style/template.html5
+++ b/style/template.html5
@@ -39,16 +39,16 @@ $include-before$
 $endfor$
 <content>
 $if(title)$
-$if(cover)$
-<figure>
-  <img src="$cover$"/>
-</figure>
-$endif$
 <header>
 <h1 class="title">$title$</h1>
 $if(subtitle)$
 <h1 class="subtitle">$subtitle$</h1>
 $endif$
+$if(cover)$
+<figure>
+  <img src="$cover$"/>
+</figure>
+$endif$
 $for(author)$
 <h2 class="author">$author$</h2>
 $endfor$