SWI-1920 Add trailing slashes to relative links (#965)

* Add trailing slashes to relative links

* replace leading slashes

* fix duplicate slashes and accidental leading slashes

* leading slashes

* remove ruby guide

* fix relative links

Author: ckoegel

site/docs/account/about.mdx

@@ -19,9 +19,9 @@ Your Bandwidth account is your entrypoint into using Bandwidth's products and se
 
 | Guide | Description |
 |:------|:------------|
-| [Credentials](./credentials) | How to properly configure API credentials |
-| [Structure](./structure) | An overview of Bandwidth's account structure |
-| [Setup](./dashboard-setup) | How to set up your Bandwidth Dashboard account |
-| [Applications](./applications) | How to configure Applications to receive messaging and voice event webhooks |
-| [Subscriptions](./subscriptions) | How to configure Subscriptions to receive number management and porting event webhooks |
+| [Credentials](/docs/account/credentials/) | How to properly configure API credentials |
+| [Structure](/docs/account/structure/) | An overview of Bandwidth's account structure |
+| [Setup](/docs/account/dashboard-setup/) | How to set up your Bandwidth Dashboard account |
+| [Applications](/docs/account/applications/) | How to configure Applications to receive messaging and voice event webhooks |
+| [Subscriptions](/docs/account/subscriptions/) | How to configure Subscriptions to receive number management and porting event webhooks |
 

site/docs/account/applications.mdx

@@ -30,13 +30,13 @@ export const Highlight = ({children, color}) => (
 
 Bandwidth uses HTTP webhooks to send message & voice events to any publicly addressable url.
 
-In order to successfully use the Voice & Messaging APIs, you need to configure an `Application` for **both** the [Voice](../../voice) & the [Messaging](../../messaging) APIs.
+In order to successfully use the Voice & Messaging APIs, you need to configure an `Application` for **both** the [Voice](/docs/voice/) & the [Messaging](/docs/messaging/) APIs.
 
 Applications are where you configure webhook URLs for Bandwidth to send either message or voice events to your service.
 
 Each application can be assigned to as many Locations (Sip-Peers) as needed.  However, each **Location** can only be associated with a single **Application** per service type (Voice or Messaging).
 
-The remainder of this guide covers how to create applications via the API. For a detailed guide to using the UI, please see our [account setup guide](/docs/account/dashboard-setup).
+The remainder of this guide covers how to create applications via the API. For a detailed guide to using the UI, please see our [account setup guide](/docs/account/dashboard-setup/).
 
 ## Create an Application
 
@@ -62,9 +62,9 @@ This operation will create an active application.
 | `OutboundCallbackCreds.Password`      | Messaging | No, but highly recommended         | Basic auth `Password`|
 | `RequestedCallbackTypes`              | Messaging | No                                 | List containing the `CallbackTypes` you wish to receive at the `OutboundCallbackUrl`. |
 | `RequestedCallbackTypes.CallbackType` | Messaging | No                                 | `message-delivered`, `message-sending`, `message-failed` |
-| `CallInitiatedCallbackUrl`            | Voice     | Yes, for `Voice-V2`                | Url to receive [initiate events](../voice/webhooks/initiate.mdx) for inbound calls |
+| `CallInitiatedCallbackUrl`            | Voice     | Yes, for `Voice-V2`                | Url to receive [initiate events](/docs/voice/webhooks/initiate/) for inbound calls |
 | `CallInitiatedMethod`                 | Voice     | No                                 | HTTP method for events sent to the `CallInitiatedCallbackUrl`.<br/> <Highlight color="#079CEE">POST</Highlight> or <Highlight color="#00bf8c">GET</Highlight><br/><br/>Default is <Highlight color="#079CEE">POST</Highlight> |
-| `CallStatusCallbackUrl`               | Voice     | No                                 | Url to receive [disconnect events](../voice/webhooks/disconnect.mdx) for inbound calls |
+| `CallStatusCallbackUrl`               | Voice     | No                                 | Url to receive [disconnect events](/docs/voice/webhooks/disconnect/) for inbound calls |
 | `CallStatusMethod`                    | Voice     | No                                 | HTTP method for events sent to the `CallStatusCallbackUrl`.<br/> <Highlight color="#079CEE">POST</Highlight> or <Highlight color="#00bf8c">GET</Highlight><br/><br/>Default is <Highlight color="#079CEE">POST</Highlight> |
 | `CallbackCreds`                       | Voice     | No, but highly recommended         | Basic auth credentials to apply to your message & voice events |
 | `CallbackCreds.UserId`                | Voice     | No, but highly recommended         | Basic auth `UserId` |

site/docs/account/dashboard-setup.mdx

@@ -15,13 +15,13 @@ keywords:
 image: '@site/static/img/bw-icon.svg'
 ---
 
-This walks through how to setup and configure your Bandwidth account through the [Bandwidth Dashboard](https://dashboard.bandwidth.com) for use with our [Number Management](../../numbers), [HTTP Voice](../../voice), and [HTTP Messaging](../../messaging) APIs.
+This walks through how to setup and configure your Bandwidth account through the [Bandwidth Dashboard](https://dashboard.bandwidth.com) for use with our [Number Management](/docs/numbers/), [HTTP Voice](/docs/voice/), and [HTTP Messaging](/docs/messaging/) APIs.
 
 Now that we’ve covered the [hierarchical structure](structure.md) of your Bandwidth Dashboard account, let’s talk about how to complete your set-up.
 
 Bandwidth recommends that all new users complete their account set-up using the Bandwidth Dashboard user interface to best get acquainted with our unique account structure.
 
-After you’ve familiarized yourself with these concepts, you may want to automate your set-up and [programmatically configure](../programmatic-setup) your Sub-Accounts, Locations & Applications.
+After you’ve familiarized yourself with these concepts, you may want to automate your set-up and [programmatically configure](/docs/account/programmatic-setup/) your Sub-Accounts, Locations & Applications.
 
 ## Assumptions
 * You have been contracted and given access to your Bandwidth Dashboard Account
@@ -85,7 +85,7 @@ For a self-guided training tutorial, click on **Learning Lab & Support** in the
 ![Account Setup 2](@site/static/img/docs-diagrams/account/setup-2.png)
 
 :::info
-For more information about our applications API, check out our [Applications Guide](../applications).
+For more information about our applications API, check out our [Applications Guide](/docs/account/applications/).
 :::
 
 ### Create a Voice Application
@@ -212,11 +212,11 @@ Now that your Account is set up, you’re ready to order a phone number and begi
 
 For a guide on ordering phone numbers in the Bandwidth Dashboard, [click here](https://support.bandwidth.com/hc/en-us/articles/360011094753-How-do-I-search-and-order-phone-numbers-)!
 
-For a guide on ordering phone numbers via the Bandwidth Dashboard API, [click here](/docs/numbers/guides/searchingForNumbers)!
+For a guide on ordering phone numbers via the Bandwidth Dashboard API, [click here](/docs/numbers/guides/searchingForNumbers/)!
 
 ## Next steps
 ### Create an API-only User
-Create an [API-only user](../credentials) to validate your API calls. Unlike user accounts that can access the Bandwidth Dashboard User Interface, users restricted to API only access won’t require periodic password resets.
+Create an [API-only user](/docs/account/credentials/) to validate your API calls. Unlike user accounts that can access the Bandwidth Dashboard User Interface, users restricted to API only access won’t require periodic password resets.
 
 
 ### Start Developing to Our Voice and Messaging APIs

site/docs/account/programmatic-setup.mdx

@@ -35,8 +35,8 @@ export const Highlight = ({children, color}) => (
   );
 
 
-This walks through how to setup and configure your Bandwidth account via Bandwidth's [Number Management API](../../numbers) for use with our [HTTP Voice](../../voice), and [HTTP Messaging](../../messaging) APIs.
-Unless you are already comfortable with our Number Management API and Bandwidth account structures, it is recommended that you follow our [Dashboard UI Setup Guide](../dashboard-setup) for the Bandwidth Dashboard instead of using this programmatic guide.
+This walks through how to setup and configure your Bandwidth account via Bandwidth's [Number Management API](/docs/numbers/) for use with our [HTTP Voice](/docs/voice/), and [HTTP Messaging](/docs/messaging/) APIs.
+Unless you are already comfortable with our Number Management API and Bandwidth account structures, it is recommended that you follow our [Dashboard UI Setup Guide](/docs/account/dashboard-setup/) for the Bandwidth Dashboard instead of using this programmatic guide.
 
 ## Assumptions
 * You have been contracted and given access to your Bandwidth Dashboard Account
@@ -376,14 +376,14 @@ Ordering a phone number and assigning it to a location is necessary to get an ap
 
 For a guide on ordering phone numbers in the Bandwidth Dashboard, [click here](https://support.bandwidth.com/hc/en-us/articles/360011094753-How-do-I-search-and-order-phone-numbers-)!
 
-For a guide on ordering phone numbers via the Bandwidth Dashboard API, [click here](/docs/numbers/guides/searchingForNumbers)!
+For a guide on ordering phone numbers via the Bandwidth Dashboard API, [click here](/docs/numbers/guides/searchingForNumbers/)!
 
 
 
 ## Create an Application
 After assigning the phone number you've ordered to a location, you must create a messaging or voice application and assign it to the location that has the phone number you would like to use.
 :::info
-For more information about our applications API, check out our [Applications Guide](../applications).
+For more information about our applications API, check out our [Applications Guide](/docs/account/applications/).
 :::
 
 ### Create a Messaging Application
@@ -663,4 +663,4 @@ Content-Type: application/xml
 ```
 
 </TabItem>
-</Tabs>
+</Tabs>

site/docs/emergency/about.mdx

@@ -31,7 +31,7 @@ Please be sure to select the correct APIs & login for the services for which you
 
 | Guide | Description |
 |:------|:------------|
-| [About Emergency Notifications](/docs/emergency/dashboard/notifications) | Learn about Emergency Notifications |
+| [About Emergency Notifications](/docs/emergency/dashboard/notifications/) | Learn about Emergency Notifications |
 
 ## 911 Access Dashboard (DASH)
 
@@ -43,5 +43,5 @@ Please be sure to select the correct APIs & login for the services for which you
 
 | API Reference | Description |
 |:------|:------------|
-| [DASH API Reference](/apis/dash) | DASH Emergency API Reference |
-| [DASH Notifications API Reference](/apis/dash-notifications) | DASH Emergency Notifications API Reference |
+| [DASH API Reference](/apis/dash/) | DASH Emergency API Reference |
+| [DASH Notifications API Reference](/apis/dash-notifications/) | DASH Emergency Notifications API Reference |

site/docs/emergency/dash/about.mdx

@@ -21,9 +21,9 @@ The [911 Access Dashboard](https://dashboard.dashcs.com/) allows you to easily p
 ## 911 Access Dashboard Overview
 | Guide | Description |
 |:------|:------------|
-| [DASH API Reference](/apis/dash) | The 911 Access Dashboard API Reference |
-| [Emergency Notifications API Reference](/apis/dash-notifications) | The 911 Access Dashboard Emergency Notifications API Reference |
-| [SOAP Overview](/docs/emergency/dash/soap) | The SOAP reference for the 911 Access Dashboard |
+| [DASH API Reference](/apis/dash/) | The 911 Access Dashboard API Reference |
+| [Emergency Notifications API Reference](/apis/dash-notifications/) | The 911 Access Dashboard Emergency Notifications API Reference |
+| [SOAP Overview](/docs/emergency/dash/soap/) | The SOAP reference for the 911 Access Dashboard |
 
 Bandwidth’s API is a set of programming instructions and standards for accessing Bandwidth’s web-based application – the [911 Access Dashboard](http://dashboard.dashcs.com/). The API provides a quick and efficient way to manage endpoint configuration.
 

site/docs/emergency/dash/errors.mdx

@@ -34,11 +34,11 @@ Unable to provision DID. Contact Bandwidth Support for assistance.
 
 We ask our customers to self-limit requests to 3 per second. By default, Bandwidth will automatically limit requests for some resource-intensive API operations to 5 requests per second so that the activities of one customer don't impact other customers. The operations that are throttled are:
 
-  * [validateLocation](/apis/dash#operation/validateLocation)
-  * [addLocation](/apis/dash#operation/addLocation)
-  * [provisionLocation](/apis/dash#operation/provisionLocation)
-  * [removeLocation](/apis/dash#operation/removeLocation)
-  * [removeUri](/apis/dash#operation/removeUri)
+  * [validateLocation](/apis/dash#operation/validateLocation/)
+  * [addLocation](/apis/dash#operation/addLocation/)
+  * [provisionLocation](/apis/dash#operation/provisionLocation/)
+  * [removeLocation](/apis/dash#operation/removeLocation/)
+  * [removeUri](/apis/dash#operation/removeUri/)
 
 Both SOAP and REST versions of these operations are rate-limited.
 

site/docs/emergency/dash/usage.mdx

@@ -16,12 +16,12 @@ image: '@site/static/img/bw-icon.svg'
 
 The sequence diagram below shows a hypothetical usage scenario.
 
-  * Add some locations by calling the [addLocation](/apis/dash#operation/addLocation) method. You can have multiple locations for one URI. The maximum number of locations for one URI is configured in the system. Contact Bandwidth Support if you need to add more locations than the default three. Each call to [addLocation](/apis/dash#operation/addLocation) returns a Location that has status information so you can see if the location was GEOCODED, and an ID (locationId) that can be used later to uniquely provision or remove the location.
-  * After calling [addLocation](/apis/dash#operation/addLocation) a few times, use [provisionLocation](/apis/dash#operation/provisionLocation) to set the active location. Send in the locationId to specify what location to provision out of the locations added to the URI. The [provisionLocation](/apis/dash#operation/provisionLocation) call will return another status. A successful call will return PROVISIONED status.
+  * Add some locations by calling the [addLocation](/apis/dash#operation/addLocation/) method. You can have multiple locations for one URI. The maximum number of locations for one URI is configured in the system. Contact Bandwidth Support if you need to add more locations than the default three. Each call to [addLocation](/apis/dash#operation/addLocation/) returns a Location that has status information so you can see if the location was GEOCODED, and an ID (locationId) that can be used later to uniquely provision or remove the location.
+  * After calling [addLocation](/apis/dash#operation/addLocation/) a few times, use [provisionLocation](/apis/dash#operation/provisionLocation/) to set the active location. Send in the locationId to specify what location to provision out of the locations added to the URI. The [provisionLocation](/apis/dash#operation/provisionLocation/) call will return another status. A successful call will return PROVISIONED status.
   * From this point, at any time you can ask the system what locations are associated with a URI, and the API will send back a collection of locations. If one of them is provisioned, it will have the status of PROVISIONED.
-  * In this example, we remove a location by sending the locationId to [removeLocation](/apis/dash#operation/removeLocation). The results will come back with a status of REMOVED.
+  * In this example, we remove a location by sending the locationId to [removeLocation](/apis/dash#operation/removeLocation/). The results will come back with a status of REMOVED.
   * Next another location is provisioned. If the locationId is different than what was used before then the system automatically handles unprovisioning the original location.
-  * Finally, if the number is no longer used, call [removeURI](/apis/dash#operation/removeLocation) to unprovision any active location that is associated with the URI. The method will remove all the locations and the URI from the system.
+  * Finally, if the number is no longer used, call [removeURI](/apis/dash#operation/removeLocation/) to unprovision any active location that is associated with the URI. The method will remove all the locations and the URI from the system.
 
 ![Account Setup 1](@site/static/img/docs-diagrams/emergency/dash-usage-scenario.png)
 

site/docs/emergency/dashboard/about.mdx

@@ -22,5 +22,5 @@ The [Bandwidth Dashboard](Https://dashboard.bandwidth.com), used for many functi
 
 | Guide | Description |
 |:------|:------------|
-| [Dynamic Location Routing](/docs/emergency/dashboard/dlr) | 911 Dynamic Location Routing Integration Guide |
-| [Emergency Notifications](/docs/emergency/dashboard/notifications) | Configure Emergency Notifications |
+| [Dynamic Location Routing](/docs/emergency/dashboard/dlr/) | 911 Dynamic Location Routing Integration Guide |
+| [Emergency Notifications](/docs/emergency/dashboard/notifications/) | Configure Emergency Notifications |

site/docs/emergency/dashboard/dlr.mdx

@@ -236,7 +236,7 @@ Address validation happens asynchronously and usually takes just a few seconds.
 Order Processing times can vary and are not guaranteed, please account for this if you choose to poll the `/e911s/{orderId}` endpoint for status.
 :::
 
-If you don’t want to poll for order status, you can set up an HTTP endpoint on your own servers and [subscribe](/docs/account/subscriptions) to `e911s` order status changes. Once that’s done, Bandwidth will send order events to the endpoint you specify. This removes the pain of rechecking an order to see if it’s been updated, although it does require you to run a web service. Please see “/accounts /{accountId}/subscriptions” in our dev docs for more information.
+If you don’t want to poll for order status, you can set up an HTTP endpoint on your own servers and [subscribe](/docs/account/subscriptions/) to `e911s` order status changes. Once that’s done, Bandwidth will send order events to the endpoint you specify. This removes the pain of rechecking an order to see if it’s been updated, although it does require you to run a web service. Please see “/accounts /{accountId}/subscriptions” in our dev docs for more information.
 
 For any addresses that were determined to be invalid, please refer to the ErrorList section in the response body of the GET request. If no ErrorList is present, then all addresses are valid in the order. For any valid address, Bandwidth may adjust the address you passed and convert it to a standardized version. If this happens, the response body in the GET request will indicate for each address whether it was adjusted or not. If you expect to pass the address as location-by-value in the SIP INVITE (see the Making a 933 call with a location value section below), you must use Bandwidth’s version of the standardized address in the SIP INVITE.