fix links

developer_manual/app/classloader.rst

@@ -1,3 +1,4 @@
+===========
 Classloader
 ===========
 

developer_manual/app/filesystem.rst

@@ -1,3 +1,4 @@
+==========
 Filesystem
 ==========
 

developer_manual/app/filesystembackend.rst

@@ -1,3 +1,4 @@
+===================
 Filesystem Backends
 ===================
 

developer_manual/app/hooks.rst

@@ -1,3 +1,4 @@
+=====
 Hooks
 =====
 

developer_manual/app/main.rst

@@ -1,3 +1,4 @@
+====================================
 Navigation and Pre-App configuration
 ====================================
 
@@ -37,7 +38,7 @@ The :file:`appinfo/app.php` is the first file that is loaded and executed in own
     \OCP\Util::connectHook('OC_User', 'pre_deleteUser', 'OCA\MyApp\Hooks\User', 'deleteUser');
 
 
-It is also possible to include :doc:`javascript` or :doc:`css` for other apps by placing the **addScript** or **addStyle** functions inside this file.
+It is also possible to include :doc:`js` or :doc:`css` for other apps by placing the **addScript** or **addStyle** functions inside this file.
 
 .. code-block:: php
     

developer_manual/app/request.rst

@@ -1,3 +1,4 @@
+=================
 Request lifecycle
 =================
 
@@ -13,7 +14,7 @@ A typical HTTP request consists of the following:
 The following sections will present an overview over how that request is being processed to provide an in depth view over how ownCloud works. If you are not interested in the internals or don't want to execute anything before and after your controller, feel free to skip this section and continue directly with defining :doc:`your app's routes <routes>`.
 
 Front controller
-----------------
+================
 In the beginning, all requests are sent to ownCloud's :file:`index.php` which in turn executes :file:`lib/base.php`. This file inspects the HTTP headers and abstracts away differences between different webservers and initializes the basic classes. Afterwards the basic apps are being loaded in the following order:
 
 * Authentication backends
@@ -30,11 +31,11 @@ Afterwards the following steps are performed:
 * Execute the router
 
 Router
-------
+======
 The router parses the :doc:`app's routing files <routes>` (:file:`appinfo/routes.php`), inspects the request's **method** and **url**, queries the controller from the :doc:`container` and then passes control to the dispatcher. The dispatcher is responsible for running the hooks (called Middleware) before and after the controller, executing the controller method and rendering the output.
 
 Middleware
-----------
+==========
 A :doc:`Middleware <middleware>` is a convenient way to execute common tasks such as custom authentication before or after a :doc:`controller method <controllers>` is being run. You can execute code at the following locations:
 
 * before the call of the controller method
@@ -43,11 +44,11 @@ A :doc:`Middleware <middleware>` is a convenient way to execute common tasks suc
 * before the output is rendered
 
 Container
----------
-The :doc:`container` is the place where you define all of your classes and in particular all of your controllers. The container is responsible for assembling all of your objects (newing your classes) that should only have one single instance without relying on globals or singletons. If you want to know more about why you should use it and what the benefits are, read up on the topic :doc:`../general/dependencyinjection`
+=========
+The :doc:`container` is the place where you define all of your classes and in particular all of your controllers. The container is responsible for assembling all of your objects (newing your classes) that should only have one single instance without relying on globals or singletons. If you want to know more about why you should use it and what the benefits are, read up on the topic in :doc:`container`.
 
 Controller
-----------
+==========
 
 The :doc:`controller <controllers>` contains the code that you actually want to run after a request has come in. Think of it like a callback that is executed if everything before went fine. 
 

developer_manual/app/schema.rst

@@ -1,3 +1,4 @@
+===============
 Database Schema
 ===============
 

developer_manual/app/testing.rst

@@ -1,3 +1,4 @@
+=======
 Testing
 =======
 

developer_manual/app/tutorial.rst

@@ -1,3 +1,4 @@
+========
 Tutorial
 ========
 

developer_manual/app/userbackend.rst

@@ -1,3 +1,4 @@
+=============
 User backends
 =============
 

developer_manual/app/users.rst

@@ -1,3 +1,4 @@
+=========================
 User & Session Management
 =========================