From 554d58a5efecb9a4d6200759fbba279ea0079be9 Mon Sep 17 00:00:00 2001
From: Allan Bowe <>
Date: Mon, 9 Jul 2018 11:47:03 +0200
Subject: [PATCH] removing deprecated line in yaml (site_favicon) and adding
 links to the overview page

---
 docs/dc-overview.md | 4 ++--
 mkdocs.yml          | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/dc-overview.md b/docs/dc-overview.md
index b6aeef3..893495c 100644
--- a/docs/dc-overview.md
+++ b/docs/dc-overview.md
@@ -41,5 +41,5 @@ There are 5 roles identified for users of the Data Controller:
 1. *Viewer*.  A viewer uses the Data Controller as a means to explore data without risk of locking datasets. By using the Data Controller to view data, it also becomes possible to 'link' to data (share a url to share a table with a colleague, for instance).
 2. *Editor*.  An editor makes changes to data in a table (add, modify, delete) and submits those changes to the approver(s) for acceptance.
 3. *Approver*.  An approver accepts / rejects proposed changes to data under their control. If accepted, the change is applied to the target table.
-4. *Auditor*.  An auditor has the ability to review the history of changes to a particular table.
-5. *Administrator*.  An administrator has the ability to add new tables to the Data Controller, and to configure the security settings (at metadata group level) as required.
+4. *Auditor*.  An auditor has the ability to review the [history](dc-userguide.md#history) of changes to a particular table.
+5. *Administrator*.  An administrator has the ability to add new [tables](dcc-tables.md) to the Data Controller, and to configure the security settings (at metadata group level) as required.
diff --git a/mkdocs.yml b/mkdocs.yml
index 8d5e4e9..c257987 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -19,7 +19,7 @@ markdown_extensions:
  - fontawesome_markdown
 
 extra_css: ['font-awesome.css']
-site_favicon: img/favicon.ico
+
 theme: 
   name: material 
   logo: 'img/favicon.ico'