use correct headers

Author: KieranHayes

guides/php-app/deployment.md

@@ -133,7 +133,7 @@ set :remote_web_root_path, 'web'
 cap dev php:clear_opcache
 {% endhighlight %}
 
-#### Output
+### Output
 
 {% highlight shell-session%}
 00:00 php:clear_opcache
@@ -154,7 +154,3 @@ In our **deploy.rb** we add the following lines:
 after 'deploy:finished', 'php:clear_opcache'
 {% endhighlight %}
 
-
-## Customizing group and file permissions
-
-## 

rake/dkdeploy-core/assets.md

@@ -5,7 +5,7 @@ section: "rake"
 layout: default
 ---
 
-#### Configuration
+### Configuration
 
 Add these variables in your deploy.rb file before using any of the tasks below.
 
@@ -78,7 +78,7 @@ Empty asset folders.
 
 Compiles sass files in a css file.
 
-#### Configuration
+### Configuration
 
 Set your sass file paths or whole directory paths from your project in **:compass_sources**.
 Possible values for `:compass_compile_arguments` are `['--boring', '--environment', 'production']`.

rake/dkdeploy-core/bower.md

@@ -68,8 +68,6 @@ See [bower.io](http://bower.io/) for details about bower.
 
 ### Configuration
 
-#### Variables
-
 By default dkdeploy will assume the `:bower_paths` path as directories of your bower.json files. You can overwrite this by setting the variable `:bower_paths` in your Capistrano configuration. By default, the  `:bower_paths` variable fetches from the `:copy_source` variable.
 
 Again, the multiple directories are relative the current working directory.

rake/dkdeploy-core/current_folder.md

@@ -11,13 +11,13 @@ htdocs contains three subdirectories (**current**, **releases** and **shared**)
 If no deployment was done before, **current** is a directory. If there already was a deployment earlier, it is a symlink.
 This task deletes the **current** directory, unless it is a symlink.
 
-#### Usage
+### Usage
 
 in **config/deploy.rb**:
 {% highlight ruby %}
 before 'deploy:publishing', 'current_folder:remove_unlesss_symlinked'
 {% endhighlight %}
 
-#### Output
+### Output
 
 There is no output generated if the current directory is removed, if nothing is done, an event **info.ignoring_current_folder** is logged.

rake/dkdeploy-core/db.md

@@ -192,7 +192,7 @@ db_settings.{{site.data.constants.deploy.stage}}.yaml
 
 There are no variables that need to be configured.
 
-#### Usage
+### Usage
 
 This task is used internally when
 
@@ -207,7 +207,7 @@ $ cap {{site.data.constants.deploy.stage}} db:read_db_settings
 This task raises an error if the configuration file does not exists on the target stage.
 </div>
 
-#### Output
+### Output
 
 There is no output on the screen.
 The Yaml file is available in the temp directory.

rake/dkdeploy-core/enhanced_symlinks.md

@@ -10,7 +10,7 @@ layout: default
 
 **deploy.rb** contains a hash of `:enhanced_linked_dirs`. The linked_dirs task reads this hash and creates the directories listed in the key of this hash, if they do not exist.
 
-#### Configuration
+### Configuration
 
 Listing of `:enhanced_linked_dirs` in **deploy.rb:**
 {% highlight ruby %}

rake/dkdeploy-core/fail.md

@@ -9,7 +9,7 @@ layout: default
 
 Raises internal failure condition.
 
-#### Usage
+### Usage
 
 Use this function within your own ruby tasks to raise errors during the execution.
 
@@ -21,7 +21,7 @@ end
 {% endhighlight %}
 
 
-#### Output
+### Output
 
 The output will be the provided errors.<br/>
 The deployment will be aborted.

rake/dkdeploy-core/file_access.md

@@ -9,34 +9,34 @@ layout: default
 
 Sets owner and group of the shared and release path. This task invokes **set_owner_group_of_shared_path** and **set_owner_group_of_release_path**.
 
-#### Usage
+### Usage
 
 {% highlight shell %}
 $ cap {{site.data.constants.deploy.stage}} file_access:set_owner_group
 {% endhighlight %}
 
-#### Output
+### Output
 
 See outputs in tasks **set_owner_group_of_shared_path** and **set_owner_group_of_release_path**.
 
 ## set_owner_group_of_shared_path
 
 Sets owner and group of the shared path.
 
-#### Configuration
+### Configuration
 
 {% highlight ruby %}
 set :default_file_access_owner_of_shared_path, "{{site.data.constants.deploy.user}}"
 set :default_file_access_group_of_shared_path, "{{site.data.constants.deploy.group}}"
 {% endhighlight %}
 
-#### Usage
+### Usage
 
 {% highlight shell %}
 $ cap {{site.data.constants.deploy.stage}} file_access:set_owner_group_of_shared_path
 {% endhighlight %}
 
-#### Output
+### Output
 
 {% highlight shell %}
 $ sudo chown {{site.data.constants.deploy.user}}:{{site.data.constants.deploy.group}} [project_path]/shared

rake/dkdeploy-core/maintenance.md

@@ -9,67 +9,66 @@ layout: default
 
 Creates a maintenance.json file.
 
-#### Configuration
+### Configuration
 
 none
 
-#### Usage
+### Usage
 
 {% highlight shell %}
 $ cap {{site.data.constants.deploy.stage}} maintenance:enable
 {% endhighlight %}
 
 
-#### Output
+### Output
 
 Creates the file **shared_path/config/maintenance.json** with no content
 
 ## enable_permanent
 
 Creates a maintenance.json file.
 
-#### Configuration
+### Configuration
 
 none
 
-#### Usage
+### Usage
 
 {% highlight shell %}
 $ cap {{site.data.constants.deploy.stage}} maintenance:enable_permanent
 {% endhighlight %}
 
 
-#### Output
+### Output
 
 Creates the file **shared_path/config/maintenance.json** with enabled_permanent: true
 
 ## disable
 
 Removes a maintenance.json file. Ony works if the maintenance mode wasnt set with enable_permanent, if so use disable_permanent.
 
-#### Configuration
+### Configuration
 
 none
 
-#### Usage
+### Usage
 
 {% highlight shell %}
 $ cap {{site.data.constants.deploy.stage}} maintenance:disable
 {% endhighlight %}
 
-
 ## disable_permanent
 
 Removes a maintenance.json file.
 
-#### Usage
+### Usage
 
 {% highlight shell %}
 $ cap {{site.data.constants.deploy.stage}} maintenance:disable_permanent
 {% endhighlight %}
 
 
-#### Output
+### Output
 
 none
 

rake/dkdeploy-core/new_release_path.md

@@ -39,8 +39,6 @@ $ BUILD_TAG=1 JOB_NAME=foo BUILD_NUMBER=bar cap {{site.data.constants.deploy.sta
 
 = **{{site.data.constants.deploy.release2_folder}}**
 
-
-
 ## failed
 
 Handle deployment errors
@@ -59,17 +57,17 @@ Remove and archive rolled-back release.
 
 This task simulates a failing deployments. It is used for the tests - especially for testing the Rollback Manager.
 
-#### Configuration
+### Configuration
 
 There is nothing to configure, the task simply raises an exception.
 
-#### Usage
+### Usage
 
 Example usage: 
 {% highlight shell %}
 $ cap {{site.data.constants.deploy.stage}} deploy:fail
 {% endhighlight %}
 
-#### Output
+### Output
 
 A console output that the deployment has failed.