header indent fix

docs/installation.rst

@@ -6,11 +6,11 @@ Installation
     :depth: 1
     :local:
 
-        Madcore lives across 5 Github repositories: https://github.com/madcore-ai  All are being actively
-        developed across many branches. `development` branch is always kept stable and merged into master
-        when features align at which point a Python PIP package is created. This page will explain on how
-        to perform a development installation so you have control over branch and commit id's used to pin
-        your installation into a known working state.
+Madcore lives across 5 Github repositories: https://github.com/madcore-ai  All are being actively
+developed across many branches. `development` branch is always kept stable and merged into master
+when features align at which point a Python PIP package is created. This page will explain on how
+to perform a development installation so you have control over branch and commit id's used to pin
+your installation into a known working state.
 
 
 Bitbucket Account

docs/technology.rst

@@ -6,15 +6,15 @@ Technology
     :depth: 1
     :local:
 
-    Docker Container is the common denominator and this is where your code ends up.
-    Docker Registries holds containers. Kubernetes is managing runtime of containers and Kubernetes Charts (Helm)
-    are persisting details of infrastructure required to launch your container (scaling, storage, run types,
-    variables, secrets). AWS with Ubuntu Xenial infrastructure is used to provide flexible organization of
-    Kubernetes layer. Madcore focus is within Kubernetes realm primarily. Cloud and OS
-    layer was required since Madcore concept is surrounded by infrastructure elements, however as more cloud providers
-    offer Kubernetes-As-Service, we will be able to attach Madcore Project to any of them providing they meet
-    project requirements. In what seems an unlimited amount of choices on how to do this we selected one Cloud and
-    one OS to stay in focus of mission statement. Below is an incomplete list of credits:
+Docker Container is the common denominator and this is where your code ends up.
+Docker Registries holds containers. Kubernetes is managing runtime of containers and Kubernetes Charts (Helm)
+are persisting details of infrastructure required to launch your container (scaling, storage, run types,
+variables, secrets). AWS with Ubuntu Xenial infrastructure is used to provide flexible organization of
+Kubernetes layer. Madcore focus is within Kubernetes realm primarily. Cloud and OS
+layer was required since Madcore concept is surrounded by infrastructure elements, however as more cloud providers
+offer Kubernetes-As-Service, we will be able to attach Madcore Project to any of them providing they meet
+project requirements. In what seems an unlimited amount of choices on how to do this we selected one Cloud and
+one OS to stay in focus of mission statement. Below is an incomplete list of credits:
 
 
 Containers Selection