Replace remaining link tags with native markdown

Author: dcramer

src/_includes/learn-sdk.md

@@ -1,6 +1,6 @@
 {% capture __alert_content -%}
 This page will provide you with details that are very specific to the platform. To learn how to use our unified 
-SDKs in general, please visit the [Error Reporting]({%- link _documentation/error-reporting/quickstart.md -%}?platform={{ include.platform }}), [Enriching Error Data]({%- link _documentation/enriching-error-data/additional-data.md -%}?platform={{ include.platform }}), [Releases]({%- link _documentation/workflow/releases/index.md -%}?platform={{ include.platform }}),  and [Data Management]({%- link _documentation/data-management/event-grouping/index.md -%}?platform={{ include.platform }}) sections.
+SDKs in general, please visit the [Error Reporting](/error-reporting/quickstart/?platform={{ include.platform }}), [Enriching Error Data](/enriching-error-data/additional-data/?platform={{ include.platform }}), [Releases](/workflow/releases/?platform={{ include.platform }}),  and [Data Management](/data-management/event-grouping/?platform={{ include.platform }}) sections.
 {%- endcapture -%}
 {%- include components/alert.html
   title="Learn about SDK usage"

src/_includes/platforms/configure-releases.md

@@ -7,7 +7,7 @@ A release is a version of your code that you deploy to an environment. When you
 
 After configuring your SDK, setting up releases is a 2-step process:
 
-1. [Create Release and Associate Commits]({%- link _documentation/workflow/releases/index.md -%}#create-release)
-2. [Tell Sentry When You Deploy a Release]({%- link _documentation/workflow/releases/index.md -%}#create-deploy)
+1. [Create Release and Associate Commits](/workflow/releases/#create-release)
+2. [Tell Sentry When You Deploy a Release](/workflow/releases/#create-deploy)
 
 For more information, see [Releases Are Better With Commits](https://blog.sentry.io/2017/05/01/release-commits.html).

src/_includes/platforms/fingerprints.md

@@ -10,9 +10,7 @@ aggressive, you can do that as well by adding the special
 string `{{default}}` as one of the items.
 {% endraw %}
 
-For code samples, see [Grouping & Fingerprints]({%- link
-_documentation/data-management/event-grouping/index.md
--%}?platform=python#use-cases).
+For code samples, see [Grouping & Fingerprints](/data-management/event-grouping/?platform=python#use-cases).
 
 For more information, see [Aggregate Errors with Custom
 Fingerprints](https://blog.sentry.io/2018/01/18/setting-up-custom-fingerprints).

src/_includes/platforms/upload-debug-info.md

@@ -16,5 +16,4 @@ Unless you are uploading Breakpad symbols, be sure to also include the binaries
 when uploading files to Sentry.
 
 For more information on uploading debug information and their supported formats,
-see [Debug Information Files]({%- link _documentation/workflow/debug-files.md
--%}).
+see [Debug Information Files](/workflow/debug-files/).

src/collections/_dev_components/markdown-styleguide/links.md

@@ -3,5 +3,5 @@ title: Links
 ---
 
 ```liquid
-{% raw %}[Alt text]({%- link _documentation/path/to/document.md -%}){% endraw %}
+{% raw %}[Alt text](/path/to/document/){% endraw %}
 ```

src/collections/_documentation/accounts/pricing.md

@@ -54,7 +54,7 @@ Business and Enterprise plans have the option to configure rate limits for each
 
 ## Managing your event volume
 
-If your projects have a high volume of events, you can control how many errors Sentry receives by reviewing Sentry's guide to [Manage Your Event Stream]({%- link _documentation/accounts/quotas/manage-event-stream-guide.md -%}).
+If your projects have a high volume of events, you can control how many errors Sentry receives by reviewing Sentry's guide to [Manage Your Event Stream](/accounts/quotas/manage-event-stream-guide/).
 
 ## FAQ
 
@@ -90,6 +90,6 @@ Your plan will continue until the end of the current billing cycle. After this,
 
 `Where can I find my previous invoices/receipts?`
 
-Users with the role of [Billing or Owner]({%- link _documentation/accounts/membership.md -%}) can find all previous invoices by going to the Organization dropdown (top-left) > Usage & Billing > Usage & Payments > Receipts.
+Users with the role of [Billing or Owner](/accounts/membership/) can find all previous invoices by going to the Organization dropdown (top-left) > Usage & Billing > Usage & Payments > Receipts.
 
 Note: You must have either `Billing` or `Owner` permissions to access and/or make changes to information on this page. If you don't have those permissions, or you are not a member of the organization in Sentry, please reach out to a Billing member or an Owner to obtain invoices.

src/collections/_documentation/accounts/quotas/index.md

@@ -20,34 +20,34 @@ Sentry completes a thorough evaluation of each event to determine if it counts t
 
 1. **SDK configuration**
 
-      The SDK configuration either allows the event or filters the event out. For more information, see [Outbound Filters in our guide to Manage Your Event Stream]({%- link _documentation/accounts/quotas/manage-event-stream-guide.md -%}#outbound-filters) or [Filtering Events]({%- link _documentation/error-reporting/configuration/filtering.md -%}).
+      The SDK configuration either allows the event or filters the event out. For more information, see [Outbound Filters in our guide to Manage Your Event Stream](/accounts/quotas/manage-event-stream-guide/#outbound-filters) or [Filtering Events](/error-reporting/configuration/filtering/).
 
 2. **SDK sample rate**
 
       If a sample rate is defined for the SDK, the SDK evaluates whether this event should be sent as a representative fraction of events. Setting a sample rate is documented for each SDK. The SDK sample rate is not dynamic; changing it requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project may better suit your needs.
 
 3. **Quota availability**
 
-      Events that exceed your quota are not sent. To add to your quota or review what happens when you exceed it, see [Increasing Quotas]({%- link _documentation/accounts/quotas/index.md -%}#increasing-quotas).
+      Events that exceed your quota are not sent. To add to your quota or review what happens when you exceed it, see [Increasing Quotas](/accounts/quotas/#increasing-quotas).
 
 4. **Event repetition**
   -   If you have intervened to Delete and Discard an issue, then _future_ events with the same fingerprint do not count toward your quota.
   -   If the previous event was resolved, this event counts toward your quota because it may represent a regression in your code.
-  -   If you have intervened to ignore alerts about events with the same fingerprint, this event counts toward your quota because the event is still occurring. For more information, see [Inbound Filters]({%- link _documentation/accounts/quotas/index.md -%}#inbound-data-filters).
+  -   If you have intervened to ignore alerts about events with the same fingerprint, this event counts toward your quota because the event is still occurring. For more information, see [Inbound Filters](/accounts/quotas/#inbound-data-filters).
 
 5. **Spike protection**
 
-      Sentry’s spike protection prevents huge overages from consuming your event capacity. For more information, see [Spike Protection]({%- link _documentation/accounts/quotas/index.md -%}#spike-protection).
+      Sentry’s spike protection prevents huge overages from consuming your event capacity. For more information, see [Spike Protection](/accounts/quotas/#spike-protection).
 
 In addition, depending on your project’s configuration and the plan you subscribe to, Sentry may also check:
 
 6. **Rate limit for the project**
 
-      If the rate limit for the project has been exceeded, and your subscription allows, the event will not be counted. For more information, see [Rate Limiting in our guide to Manage Your Event Stream]({%- link _documentation/accounts/quotas/manage-event-stream-guide.md -%}#4-rate-limiting) or  [Rate Limiting Projects]({%- link _documentation/accounts/quotas/index.md -%}#id1).
+      If the rate limit for the project has been exceeded, and your subscription allows, the event will not be counted. For more information, see [Rate Limiting in our guide to Manage Your Event Stream](/accounts/quotas/manage-event-stream-guide/#4-rate-limiting) or  [Rate Limiting Projects](/accounts/quotas/#id1).
 
 7. **Inbound filters**
 
-      If any inbound filter is set for this type of event, and your subscription allows, the event will not be counted. For more information, see [Inbound Filters in our guide to Manage Your Event Stream]({%- link _documentation/accounts/quotas/manage-event-stream-guide.md -%}#inbound-data-filters) or [Inbound Data Filter]({%- link _documentation/accounts/quotas/index.md -%}#inbound-data-filters).
+      If any inbound filter is set for this type of event, and your subscription allows, the event will not be counted. For more information, see [Inbound Filters in our guide to Manage Your Event Stream](/accounts/quotas/manage-event-stream-guide/#inbound-data-filters) or [Inbound Data Filter](/accounts/quotas/#inbound-data-filters).
 
 After these checks are processed, the event counts toward your quota. It is accepted into Sentry, where it persists and is stored.
 
@@ -130,15 +130,15 @@ After these checks are processed, the event counts toward your quota. It is acce
 
 Add to your quota at any time during your billing period, either by upgrading to a higher tier or by increasing your on-demand capacity. While the available plans fit most individual and business needs, Sentry is designed to handle large throughput. If your team needs more, we’re happy to help. Reach out to our sales team at [[email protected]](mailto:sales%40sentry.io) to learn more about increasing capacity.
 
-If you’ve exceeded your quota threshold, the server will respond with a 429 HTTP status code. However, if this is your first time exceeding quota, you'll be entered into a one-time grace period. For more information, see this [Help article](https://help.sentry.io/hc/en-us/articles/115000154554-What-happens-when-I-run-out-of-event-capacity-and-a-grace-period-is-triggered-). In addition, you can specify a spending cap for on-demand capacity if you need additional events; for example, if you’re rolling out a new version and anticipate more events this month. For more information, see [On-Demand Spending Cap]({%- link _documentation/accounts/pricing.md -%}#on-demand-cap).
+If you’ve exceeded your quota threshold, the server will respond with a 429 HTTP status code. However, if this is your first time exceeding quota, you'll be entered into a one-time grace period. For more information, see this [Help article](https://help.sentry.io/hc/en-us/articles/115000154554-What-happens-when-I-run-out-of-event-capacity-and-a-grace-period-is-triggered-). In addition, you can specify a spending cap for on-demand capacity if you need additional events; for example, if you’re rolling out a new version and anticipate more events this month. For more information, see [On-Demand Spending Cap](/accounts/pricing/#on-demand-cap).
 
 ## Rate Limiting Projects {#id1}
 
 Per-key rate limits allow you to set the maximum volume of events a key will accept during a period of time.
 
 For example, you may have a project in production that generates a lot of noise. A rate limit allows you to set the maximum amount of data to “500 events per minute”. Additionally, you can create a second key for the same project for your staging environment, which is unlimited, ensuring your QA process is still untouched.
 
-To set up rate limits, navigate to **[Project] » Client Keys » Configure**. Select an individual key or create a new one, then you’ll be able to define a rate limit as well as view a breakdown of events received by that key. For additional information and examples, see [Rate Limiting in our guide to Manage Your Event Stream]({%- link _documentation/accounts/quotas/manage-event-stream-guide.md -%}#4-rate-limiting).
+To set up rate limits, navigate to **[Project] » Client Keys » Configure**. Select an individual key or create a new one, then you’ll be able to define a rate limit as well as view a breakdown of events received by that key. For additional information and examples, see [Rate Limiting in our guide to Manage Your Event Stream](/accounts/quotas/manage-event-stream-guide/#4-rate-limiting).
 
 {% include components/alert.html
     title="Note"
@@ -158,7 +158,7 @@ In some cases, the data you’re receiving in Sentry is hard to filter, or you d
 -     From specific release versions of your code
 -     From certain IP addresses.
 
-Explore these by navigating to **[Project] » Project Settings » Inbound Filters**. Commonly-set filters are discussed here for your quick reference. For additional information and examples, see [Inbound Data Filters in our guide to Manage Your Event Stream]({%- link _documentation/accounts/quotas/manage-event-stream-guide.md -%}#inbound-data-filters). Commonly-set filters include:
+Explore these by navigating to **[Project] » Project Settings » Inbound Filters**. Commonly-set filters are discussed here for your quick reference. For additional information and examples, see [Inbound Data Filters in our guide to Manage Your Event Stream](/accounts/quotas/manage-event-stream-guide/#inbound-data-filters). Commonly-set filters include:
 
 *IP Filters.* If you have a rogue client, Sentry supports blocking an IP from sending data. Navigate to **[Project] » Project Settings » Inbound Filters** to add the IP addresses (or subnets) to **Filter errors from these IP addresses**.
 

src/collections/_documentation/accounts/sso.md

@@ -98,4 +98,4 @@ When prompted with the Rippling Metadata URL, copy this into the Sentry Rippling
 
 #### Custom SAML2 Integration
 
-For other SAML2 SSO providers not listed above, Sentry provides  generic connectors for [SAML2 based authentication]({%- link _documentation/accounts/saml2.md -%}), which may be configured manually.
+For other SAML2 SSO providers not listed above, Sentry provides  generic connectors for [SAML2 based authentication](/accounts/saml2/), which may be configured manually.

src/collections/_documentation/api/events/index.md

@@ -5,17 +5,17 @@ title: Events
 ---
 
 
-- [List a Project's Events]({%- link _documentation/api/events/get-project-events.md -%})
-- [Retrieve an Event for a Project]({%- link _documentation/api/events/get-project-event-details.md -%})
-- [List a Project's Issues]({%- link _documentation/api/events/get-project-group-index.md -%})
-- [Bulk Mutate a List of Issues]({%- link _documentation/api/events/put-project-group-index.md -%})
-- [Bulk Remove a List of Issues]({%- link _documentation/api/events/delete-project-group-index.md -%})
-- [Retrieve an Issue]({%- link _documentation/api/events/get-group-details.md -%})
-- [Update an Issue]({%- link _documentation/api/events/put-group-details.md -%})
-- [Remove an Issue]({%- link _documentation/api/events/delete-group-details.md -%})
-- [List an Issue's Events]({%- link _documentation/api/events/get-group-events.md -%})
-- [Retrieve the Latest Event for an Issue]({%- link _documentation/api/events/get-group-events-latest.md -%})
-- [Retrieve the Oldest Event for an Issue]({%- link _documentation/api/events/get-group-events-oldest.md -%})
-- [List an Issue's Hashes]({%- link _documentation/api/events/get-group-hashes.md -%})
-- [Retrieve Tag Details]({%- link _documentation/api/events/get-group-tag-key-details.md -%})
-- [List a Tag's Values]({%- link _documentation/api/events/get-group-tag-key-values.md -%})
+- [List a Project's Events](/api/events/get-project-events/)
+- [Retrieve an Event for a Project](/api/events/get-project-event-details/)
+- [List a Project's Issues](/api/events/get-project-group-index/)
+- [Bulk Mutate a List of Issues](/api/events/put-project-group-index/)
+- [Bulk Remove a List of Issues](/api/events/delete-project-group-index/)
+- [Retrieve an Issue](/api/events/get-group-details/)
+- [Update an Issue](/api/events/put-group-details/)
+- [Remove an Issue](/api/events/delete-group-details/)
+- [List an Issue's Events](/api/events/get-group-events/)
+- [Retrieve the Latest Event for an Issue](/api/events/get-group-events-latest/)
+- [Retrieve the Oldest Event for an Issue](/api/events/get-group-events-oldest/)
+- [List an Issue's Hashes](/api/events/get-group-hashes/)
+- [Retrieve Tag Details](/api/events/get-group-tag-key-details/)
+- [List a Tag's Values](/api/events/get-group-tag-key-values/)