diff --git a/README.md b/README.md
index 6b07019..645bae2 100644
--- a/README.md
+++ b/README.md
@@ -1,45 +1,57 @@
 # NAME
 
-     Catalyst::Controller::Swagger
+    Catalyst::Controller::Swagger
 
 # SYNOPSIS
 
-     package MyApp::Controller::Root;
-     use base 'Catalyst::Controller::Swagger';
-     use Swagger qw(add_meta);
+    package MyApp::Controller::Root;
+    use base 'Catalyst::Controller::Swagger';
+    use Swagger qw(add_meta);
 
     __PACKAGE__->config(
-       swagger => {
-         api_version  => '2.2.3',
-         info          => {
-           title       => 'test project',
-           description => 'test description',
-         },
-       }
-     };
-
-
-     add_meta {
+        swagger => {
+            api_version => '2.2.3',
+            ##  base_path is required
+            base_path   => 'https//my.swagger.host/demo',
+            info        => {
+                title       => 'test project',
+                description => 'test description',
+            },
+        }
+    );
+
+    add_meta {
         action => 'test_one',
         params => [
-          { name => 'start', type => 'integer' }
+            { name => 'start', type => 'integer' }
         ],
-     };
+    };
 
     sub test_one_base :Chained('/') :PathPart('test_one') :CaptureArgs(2) {
-      my ( $self, $c ) = @_;
+        my ($self, $c, $arg1, $arg2) = @_;
     }
 
+    # A swagger route can be flagged to be swagger with the :Swagger attribute
     sub test_one :Chained('test_one_base') :PathPart('foo') :Args(1) :Swagger {
-      my ($self, $c) = @_;
-      $c->response->body("test_one");
+        my ($self, $c, $arg1) = @_;
+        $c->response->body("test_one");
     }
-    # A swagger route can be flagged to be swagger with the :Swagger attribute
+
     sub test_two :Local :Swagger {
-      my ($self, $c) = @_;
-      $c->response->body('test_two');
+        my ($self, $c) = @_;
+        $c->response->body('test_two');
     }
 
+If the controller has to be configured by a configfile you have to provide a
+`swagger` section, here a YAML file:
+
+    ---
+    ...
+    Contoller::Root:
+        swagger:
+            base_path: https//my.swagger.host/demo
+    ...
+
 # DESCRIPTION
 
 Add swagger metadata to any Catalyst route. This module will expose an "api\_docs" route
@@ -47,61 +59,58 @@ which will contain JSON that is Swagger 1.2 compatible.
 
 ## :Swagger Attribute
 
-When this attribute is applied to an action metadata that is implicit to the route will 
+When this attribute is applied to an action metadata that is implicit to the route will
 be exposed to the api\_docs route. The data that is exposed include the following: path, method,
-and route nickname. Any additional metadata that would need to be exposed would need to use 
+and route nickname. Any additional metadata that would need to be exposed would need to use
 the Swagger::add\_meta function to associate it.
 
 Here is an example of what the default swagger output looks like:
 
-      {
-        path         => '/test_two',
-        operations   => [{
-          method     => 'GET',
-          summary    => '',
-          notes      => '',
-          type => '',
-          nickname   => 'GET_/test_two',
-          summary    => '',
+    {
+        path       => '/test_two',
+        operations => [{
+            method   => 'GET',
+            summary  => '',
+            notes    => '',
+            type     => '',
+            nickname => 'GET_/test_two',
+            summary  => '',
         }],
-      }
+    }
 
 ## api\_docs route
 
 This is a route that is exposed that will output a JSON data structure that is Swagger 1.2
-compatible. 
+compatible.
 
 ## Swagger::add\_meta
 
 The add\_meta function allows a developer to associate other allowed swagger metadata. For example
 params would specify what sort of parameters a route would accept:
 
-     add_meta {
+    add_meta {
         action => 'test_one', # name of route
         params => [
-          { name => 'start', type => 'integer' }
+            { name => 'start', type => 'integer' }
         ],
-     };
+    };
 
 # Swagger
 
-For further information on Swagger and what it is see: http://www.swagger.io
+For further information on Swagger and what it is see [swagger.io](https://swagger.io).
 
 # CONTRIBUTING
 
 The code for \`catalyst-controller-swagger\` is hosted on GitHub at:
 
-      https://github.com/mediamath/catalyst-controller-swagger/
-    
+    https://github.com/mediamath/catalyst-controller-swagger/
 
 If you would like to contribute code, documentation, tests, or bugfixes, follow these steps:
 
-     1. Fork the project on GitHub.
-     2. Clone the fork to your local machine.
-     3. Make your changes and push them back up to your GitHub account.
-     4. Send a "pull request" with a brief description of your changes, and a link to a JIRA 
-     ticket if there is one.
-    
+1. Fork the project on GitHub.
+2. Clone the fork to your local machine.
+3. Make your changes and push them back up to your GitHub account.
+4. Send a "pull request" with a brief description of your changes, and a link to a JIRA ticket if there is one.
 
 If you are unfamiliar with GitHub, start with their excellent documentation here:
 
diff --git a/lib/Catalyst/Controller/Swagger.pm b/lib/Catalyst/Controller/Swagger.pm
index e41d477..cd406e0 100644
--- a/lib/Catalyst/Controller/Swagger.pm
+++ b/lib/Catalyst/Controller/Swagger.pm
@@ -72,124 +72,142 @@ sub api_docs : Local {
 
 =head1 NAME
 
-     Catalyst::Controller::Swagger
+    Catalyst::Controller::Swagger
 
 =head1 SYNOPSIS
 
-     package MyApp::Controller::Root;
-     use base 'Catalyst::Controller::Swagger';
-     use Swagger qw(add_meta);
+    package MyApp::Controller::Root;
+    use base 'Catalyst::Controller::Swagger';
+    use Swagger qw(add_meta);
 
     __PACKAGE__->config(
-       swagger => {
-         api_version  => '2.2.3',
-         info          => {
-           title       => 'test project',
-           description => 'test description',
-         },
-       }
-     };
-
-
-     add_meta {
+        swagger => {
+            api_version => '2.2.3',
+            ##  base_path is required
+            base_path   => 'https//my.swagger.host/demo',
+            info        => {
+                title       => 'test project',
+                description => 'test description',
+            },
+        }
+    );
+
+    add_meta {
         action => 'test_one',
         params => [
-          { name => 'start', type => 'integer' }
+            { name => 'start', type => 'integer' }
         ],
-     };
+    };
 
     sub test_one_base :Chained('/') :PathPart('test_one') :CaptureArgs(2) {
-      my ( $self, $c ) = @_;
+        my ($self, $c, $arg1, $arg2) = @_;
     }
 
+    # A swagger route can be flagged to be swagger with the :Swagger attribute
     sub test_one :Chained('test_one_base') :PathPart('foo') :Args(1) :Swagger {
-      my ($self, $c) = @_;
-      $c->response->body("test_one");
+        my ($self, $c, $arg1) = @_;
+        $c->response->body("test_one");
     }
-    # A swagger route can be flagged to be swagger with the :Swagger attribute
+
     sub test_two :Local :Swagger {
-      my ($self, $c) = @_;
-      $c->response->body('test_two');
+        my ($self, $c) = @_;
+        $c->response->body('test_two');
     }
 
+If the controller has to be configured by a configfile you have to provide a
+C<swagger> section, here a YAML file:
+
+    ---
+    ...
+    Contoller::Root:
+        swagger:
+            base_path: https//my.swagger.host/demo
+    ...
 
 =head1 DESCRIPTION
 
-Add swagger meta data to any Catalyst route. This module will expose an "api_docs" route
+Add swagger metadata to any Catalyst route. This module will expose an "api_docs" route
 which will contain JSON that is Swagger 1.2 compatible.
 
 =head2 :Swagger Attribute
 
-When this attribute is applied to an action meta data that is implicit to the route will 
+When this attribute is applied to an action metadata that is implicit to the route will
 be exposed to the api_docs route. The data that is exposed include the following: path, method,
-and route nickname. Any additional meta data that would need to be exposed would need to use 
+and route nickname. Any additional metadata that would need to be exposed would need to use
 the Swagger::add_meta function to associate it.
 
 Here is an example of what the default swagger output looks like:
 
-      {
-        path         => '/test_two',
-        operations   => [{
-          method     => 'GET',
-          summary    => '',
-          notes      => '',
-          type => '',
-          nickname   => 'GET_/test_two',
-          summary    => '',
+    {
+        path       => '/test_two',
+        operations => [{
+            method   => 'GET',
+            summary  => '',
+            notes    => '',
+            type     => '',
+            nickname => 'GET_/test_two',
+            summary  => '',
         }],
-      }
+    }
 
 =head2 api_docs route
 
 This is a route that is exposed that will output a JSON data structure that is Swagger 1.2
-compatible. 
+compatible.
 
 =head2 Swagger::add_meta
 
-The add_meta function allows a developer to associate other allowed swagger meta data. For example
+The add_meta function allows a developer to associate other allowed swagger metadata. For example
 params would specify what sort of parameters a route would accept:
-  
-     add_meta {
+
+    add_meta {
         action => 'test_one', # name of route
         params => [
-          { name => 'start', type => 'integer' }
+            { name => 'start', type => 'integer' }
         ],
-     };
-
-=cut
+    };
 
 =head1 Swagger
 
-For further information on Swagger and what it is see: http://www.swagger.io
-
-=cut
+For further information on Swagger and what it is see L<swagger.io|https://swagger.io>.
 
 =head1 CONTRIBUTING
 
 The code for `catalyst-controller-swagger` is hosted on GitHub at:
- 
-   https://github.com/mediamath/catalyst-controller-swagger/
- 
+
+    https://github.com/mediamath/catalyst-controller-swagger/
+
 If you would like to contribute code, documentation, tests, or bugfixes, follow these steps:
- 
-  1. Fork the project on GitHub.
-  2. Clone the fork to your local machine.
-  3. Make your changes and push them back up to your GitHub account.
-  4. Send a "pull request" with a brief description of your changes, and a link to a JIRA 
-  ticket if there is one.
- 
+
+=over
+
+=item 1.
+
+Fork the project on GitHub.
+
+=item 2.
+
+Clone the fork to your local machine.
+
+=item 3.
+
+Make your changes and push them back up to your GitHub account.
+
+=item 4.
+
+Send a "pull request" with a brief description of your changes, and a link to a JIRA ticket if there is one.
+
+=back
+
 If you are unfamiliar with GitHub, start with their excellent documentation here:
- 
-  https://help.github.com/articles/fork-a-repo
 
-=cut
+    https://help.github.com/articles/fork-a-repo
 
 =head1 COPYRIGHT & LICENSE
- 
+
 Copyright 2015, Logan Bell & John Napiorkowski / MediaMath
- 
+
 This program is free software; you can redistribute it and/or modify
 it under the same terms as Perl itself.
- 
-=cut
 
+=cut