Merge pull request killbill#337 from reshmabidikar/work-for-333

Update links to Auth API

Author: reshmabidikar

source/includes/_aviate-catalog.md

@@ -20,7 +20,7 @@ At the time of writing, the aviate catalog plugin does not expose any endpoints
 
 ### Authentication
 
-The Aviate Plugin uses a JWT based authentication mechanism. Thus, all the APIs listed in this document require a valid token. This can be obtained via the [Auth API](aviate_auth.html). 
+The Aviate Plugin uses a JWT based authentication mechanism. Thus, all the APIs listed in this document require a valid token. This can be obtained via the [Auth API](aviate-auth.html). 
 
 ## Resources
 

source/includes/_aviate-health.md

@@ -6,7 +6,7 @@ The [Aviate Health feature](https://docs.killbill.io/latest/aviate-health) provi
 
 ### Authentication
 
-The Aviate Plugin uses a JWT based authentication mechanism. Thus, all the APIs listed in this document require a valid token. This can be obtained via the [Auth API](aviate_auth.html).
+The Aviate Plugin uses a JWT based authentication mechanism. Thus, all the APIs listed in this document require a valid token. This can be obtained via the [Auth API](aviate-auth.html).
 
 ## Resources
 

source/includes/_aviate-metering.md

@@ -6,7 +6,7 @@ The Aviate plugin offers a metering feature that allows performing usage aggrega
 
 ### Authentication
 
-The Aviate Plugin uses a JWT based authentication mechanism. Thus, all the APIs listed in this document require a valid token. This can be obtained via the [Auth API](aviate_auth.html).
+The Aviate Plugin uses a JWT based authentication mechanism. Thus, all the APIs listed in this document require a valid token. This can be obtained via the [Auth API](aviate-auth.html).
 
 ## Resources