From 20a9621036b514b405253572ad17cf831067be09 Mon Sep 17 00:00:00 2001
From: Eric Lippmann <eric.lippmann@netways.de>
Date: Fri, 22 May 2015 15:30:37 +0200
Subject: [PATCH] doc: Add filenames to anchor links

This allows other markdown viewers like to follow those links.
---
 doc/authentication.md | 8 ++++----
 doc/preferences.md    | 6 +++---
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/doc/authentication.md b/doc/authentication.md
index 06ab4c13d..39e0caf3c 100644
--- a/doc/authentication.md
+++ b/doc/authentication.md
@@ -63,7 +63,7 @@ with Icinga Web 2 (e.g. an alias) no matter what the primary user id might actua
 Directive               | Description
 ------------------------|------------
 **backend**             | `ad`
-**resource**            | The name of the LDAP resource defined in [resources.ini](#resources).
+**resource**            | The name of the LDAP resource defined in [resources.ini](resources.md#resources).
 
 **Example:**
 
@@ -76,13 +76,13 @@ resource = my_ad
 ### <a id="authentication-configuration-db-authentication"></a> Database Authentication
 
 If you want to authenticate against a MySQL or a PostgreSQL database, you have to define a
-[database resource](#resources-configuration-database) which will be referenced as data source for the database
+[database resource](resources.md#resources-configuration-database) which will be referenced as data source for the database
 authentication method.
 
 Directive               | Description
 ------------------------|------------
 **backend**             | `db`
-**resource**            | The name of the database resource defined in [resources.ini](#resources).
+**resource**            | The name of the database resource defined in [resources.ini](resources.md#resources).
 
 **Example:**
 
@@ -99,7 +99,7 @@ For authenticating against a database, you have to import one of the following d
 * **etc/schema/preferences.mysql.sql** (for **MySQL** database)
 * **etc/schema/preferences.pgsql.sql** (for **PostgreSQL** databases)
 
-After that you have to define the [database resource](#resources-configuration-database).
+After that you have to define the [database resource](resources.md#resources-configuration-database).
 
 **Manually Creating Users**
 
diff --git a/doc/preferences.md b/doc/preferences.md
index 4ece5edf6..ca26b66b0 100644
--- a/doc/preferences.md
+++ b/doc/preferences.md
@@ -27,13 +27,13 @@ type = ini
 ### <a id="preferences-configuration-db"></a> Store Preferences in a Database
 
 In order to be more flexible in distributed setups you can store preferences in a MySQL or in a PostgreSQL database.
-For storing preferences in a database, you have to define a [database resource](#resources-configuration-database)
+For storing preferences in a database, you have to define a [database resource](resources.md#resources-configuration-database)
 which will be referenced as resource for the preferences storage.
 
 Directive               | Description
 ------------------------|------------
 **type**                | `db`
-**resource**            | The name of the database resource defined in [resources.ini](resources).
+**resource**            | The name of the database resource defined in [resources.ini](resources.md#resources).
 
 **Example:**
 
@@ -50,4 +50,4 @@ For storing preferences in a database, you have to import one of the following d
 * **etc/schema/preferences.mysql.sql** (for **MySQL** database)
 * **etc/schema/preferences.pgsql.sql** (for **PostgreSQL** databases)
 
-After that you have to define the [database resource](#resources-configuration-database).
+After that you have to define the [database resource](resources.md#resources-configuration-database).