Correct screenshot origin and title in markdown

docs/Permissions.md

@@ -1,4 +1,4 @@
-## Permissions ##
+## Permissions
 
 SCM-Manager knows three different types of repository permissions:
 
@@ -11,19 +11,19 @@ OWNER | The user is able to read, write and to manager permissions
 Repository permissions can be assigned to users and groups. The permissions can be assigned
 to only one repository or to each repository. Administrators have owner permissions on every repository.
 
-### Repository permissions ###
+### Repository permissions
 
 Repository permissions can be managed by administrators and by repository owners. 
 The permissions can be managed on the permission tab of each repository.
 
-![repository permissions](https://bytebucket.org/sdorra/scm-manager/wiki/screenshots/permissions_repository.png "repository permissions")
+![repository permissions](screenshots/permissions_repository.png "repository permissions")
 
-### Global permissions ###
+### Global permissions
 
 Global permissions are only manageable by administrators. They can be managed at *Security -> Users* or *Security -> Groups*.
 
-![global permissions](https://bytebucket.org/sdorra/scm-manager/wiki/screenshots/permissions_global.png "global permissions")
+![global permissions](screenshots/permissions_global.png "global permissions")
 
-### Administrators ###
+### Administrators
 
-Administrators can mark other users as administrators at *Security -> Users*.
+Administrators can mark other users as administrators at *Security -> Users*.

docs/healthchecks/svn-incompatible-dbformat.md

@@ -1,4 +1,4 @@
-# Incompatible subversion db format #
+# Incompatible subversion db format
 
 SCM-Manager versions prior to 1.36 are creating incompatible subversion repositories, if the subversion option "with 1.7 Compatible" is enabled. This subversion repositories are neither compatible with svn 1.7 nor svn 1.8. These repositories are marked as unhealthy by SCM-Manager version 1.36 and above.
 

docs/v2/State of SCM-Manager 2 development.md

@@ -1,8 +1,8 @@
 The development of SCM-Manager 2.0.0 is organised in [Trello Boards](https://trello.com/scmmanager).
 
-## [Milestone 1](https://trello.com/b/oit1MD92/scm-manager-2-0-0-milestone-1) ##
+## [Milestone 1](https://trello.com/b/oit1MD92/scm-manager-2-0-0-milestone-1)
 
-### Main goals ###
+### Main goals
 * remove deprecated and unused stuff
 * remove old style listeners
 * replace [guava eventbus](https://code.google.com/p/guava-libraries/wiki/EventBusExplained) with [legman](https://github.com/sdorra/legman)
@@ -12,25 +12,25 @@ The development of SCM-Manager 2.0.0 is organised in [Trello Boards](https://tre
 * use of [annotation processors](http://docs.oracle.com/javase/7/docs/api/javax/annotation/processing/Processor.html) instead of classpath scanning
 * move non core modules (plugin-backend, maven plugins, etc.) to separate repositories
 
-## [Milestone 2](https://trello.com/b/Afb3hoJ9/scm-manager-2-0-0-milestone-2) ##
+## [Milestone 2](https://trello.com/b/Afb3hoJ9/scm-manager-2-0-0-milestone-2)
 
-### Main goals ###
+### Main goals
 * use [apache shiro](http://shiro.apache.org/) everywhere
 * improve authentication
 * improve user and group management
 * use permission instead of roles
 
-## [Milestone 3](https://trello.com/b/eLvqTGGe/scm-manager-2-0-0-milestone-3) ##
+## [Milestone 3](https://trello.com/b/eLvqTGGe/scm-manager-2-0-0-milestone-3)
 
-### Main goals ###
+### Main goals
 * completely new designed rest api
 
-## Milestone 4 ##
+## Milestone 4
 
-### Main goals ###
+### Main goals
 * completely new user interface
 
-## Milestone 5 ##
+## Milestone 5
 
-### Main goals ###
-* improve repository api
+### Main goals
+* improve repository api

docs/v2/UI Additions or Changes to ui-components or ui-types.md

@@ -1,10 +1,11 @@
-# Changes to `ui-components`/`ui-types` #
-## Dev ##
+# Changes to `ui-components`/`ui-types` 
+
+## Dev
 If you want (or need) to add components to the `ui-components`-Packages (or types to the `ui-types`-Package) and use them in `scm-ui`; you have to link the packages using yarn link (since your changes will not have been pushed to npm.js). To do so, cd to the `scm-ui` directory and type
 
 ```yarn link @scm-manager/ui-components```
 resp.
 ```yarn linl @scm-manager/ui-types```.
 
-## Releasing changes to npm.js ##
-**TODO**
+## Releasing changes to npm.js
+**TODO**