Fix 404 links

Author: markstory

develop-docs/application/sentry-vs-getsentry.mdx

@@ -11,7 +11,7 @@ So what's in `getsentry`, then? It implements billing and account management fea
 
 Additionally, `sentry` has many hooks, implemented using Django signals, which `getsentry` subscribes to. For example, there's a Django signal called `event_received` in `sentry` that is triggered when an event is saved. If you're [running self-hosted](/self-hosted/), nothing is subscribed to this hook. But in `getsentry`, we have a counter for billing that runs when that signal fires.
 
-There are also some swappable backends in `sentry` that `getsentry` utilizes, such as `sentry.nodestore`, `sentry.quotas`, and a home-grown feature flagging system. As with hooks, these modular backends are technically available to self-hosted instances, but they're largely undocumented. For example, the feature-flagging system has a hardcoded table of features ([`SENTRY_FEATURES`](https://github.com/getsentry/sentry/blob/master/src/sentry/features/__init__.py)) that [self-hosted installs can use](/feature-flags/) to control feature availability. `getsentry` registers a different feature flag handler that flips flags based on our [billing plans](https://sentry.io/pricing/) and early access program.
+There are also some swappable backends in `sentry` that `getsentry` utilizes, such as `sentry.nodestore`, `sentry.quotas`, and a home-grown feature flagging system. As with hooks, these modular backends are technically available to self-hosted instances, but they're largely undocumented. For example, the feature-flagging system has a hardcoded table of features ([`SENTRY_FEATURES`](https://github.com/getsentry/sentry/blob/master/src/sentry/features/__init__.py)) that [self-hosted installs can use](/backend/feature-flags/) to control feature availability. `getsentry` registers a different feature flag handler that flips flags based on our [billing plans](https://sentry.io/pricing/) and early access program.
 
 ## Notes for Sentry Engineers
 

develop-docs/backend/api/public.mdx

@@ -56,7 +56,7 @@ As a guide, use these questions:
 2. Will the API change substantially in the future?
 
 If your answers are Yes and No, you're in business - make the endpoint public. Head over to the
-[public API checklist](/application/api/checklist/) and ensure that your endpoint conforms to the checklist.
+[public API checklist](/backend/api/checklist/) and ensure that your endpoint conforms to the checklist.
 
 ## Publishing an API
 

develop-docs/backend/feature-flags/index.mdx

@@ -68,7 +68,7 @@ be included in the results of the organization details response.
 
 ### Add your feature to the FeatureManager
 
-If you want to back your feature flag via options, you can do so using the [Flagpole](/feature-flags/flagpole/) library
+If you want to back your feature flag via options, you can do so using the [Flagpole](/backend/feature-flags/flagpole/) library
 by adding the feature to the `FeatureManager` with the `FLAGPOLE` enum set as the feature strategy:
 
 ```python
@@ -185,7 +185,7 @@ SENTRY_FEATURES['organizations:test-feature'] = True
 ```
 
 Alternatively, you can test Flagpole features by setting custom options locally.
-See the [Flagpole Local Development](/feature-flags/flagpole/#testing-a-flagpole-feature-locally) docs for more information on this.
+See the [Flagpole Local Development](/backend/feature-flags/flagpole/#testing-a-flagpole-feature-locally) docs for more information on this.
 
 ## Enabling your feature in production
 
@@ -194,7 +194,7 @@ flags are then configured via `sentry.conf.py`. For Sentry's SaaS deployment,
 you have the choice of using an option backed rollout via Options Automator with Flagpole,
 or by writing a custom feature flag handler.
 
-- [Flagpole](/feature-flags/flagpole/) is Sentry's internal feature flagging library, allowing a feature
+- [Flagpole](/backend/feature-flags/flagpole/) is Sentry's internal feature flagging library, allowing a feature
   with multiple target segments and condition filters to be defined in YAML within Options Automator.
 
 - [Options based features](options-backed-features/) [DEPRECATED] allow a feature

develop-docs/backend/feature-flags/options-backed-features.mdx

@@ -4,7 +4,7 @@ title: Options Backed Features [DEPRECATED]
 
 Options backed features using the `OPTIONS` strategy enum were a temporary stopgap
 that was used to formalize options-backed feature flags. These have since been
-replaced by [Flagpole](/feature-flags/flagpole/), which is Sentry's preferred
+replaced by [Flagpole](/backend/feature-flags/flagpole/), which is Sentry's preferred
 means of setting feature flags now.
 
 

develop-docs/backend/pii/index.mdx

@@ -25,7 +25,7 @@ It reads as "replace all IP addresses in all strings", or "apply `@ip:replace`
 to all `$string` fields".
 
 `@ip:replace` is called a rule, and `$string` is a <Link
-to="/pii/selectors/">selector</Link>.
+to="/backend/pii/selectors/">selector</Link>.
 
 ## Built-in Rules
 

develop-docs/backend/transaction-clustering/index.mdx

@@ -6,8 +6,9 @@ sidebar_order: 60
 Sentry attempts to scrub high-cardinality identifiers from URL transactions
 to aggregate performance data and provide more valuable insights.
 
-In terms of user experience, this feature plays a similar role as [Issue Grouping](/grouping/).
-In terms of technical implementation, it is similar to [Data Scrubbing](/pii/).
+In terms of user experience, this feature plays a similar role as [Issue Grouping](/backend/grouping/).
+In terms of technical implementation, it is similar to [Data
+Scrubbing](/backend/pii/).
 
 ## The Problem
 

develop-docs/development/analytics.mdx

@@ -290,7 +290,7 @@ class ExampleComponent extends React.Component {
 
 ## Metrics
 
-Track aggregrate stats with [Metrics](/services/metrics/). For example, this can be used to track aggregate response codes for an endpoint.
+Track aggregrate stats with [Metrics](/backend/metrics/). For example, this can be used to track aggregate response codes for an endpoint.
 
 Import the metrics library and use the `metrics.inc` function. The key needs to be unique.
 

develop-docs/development/documentation.mdx

@@ -44,4 +44,4 @@ Avoid adjacent code blocks without a paragraph of text in between. A code block
 
 ### Inclusive Language
 
-Sentry is a product used and developed by many people from different cultural backgrounds and we try to avoid language that has been identified as hurtful or insensitive. For detailed recommendations see <Link to="/development/inclusive-language/">Inclusive Language</Link>.
+Sentry is a product used and developed by many people from different cultural backgrounds and we try to avoid language that has been identified as hurtful or insensitive. For detailed recommendations see <Link to="/getting-started/inclusive-language/">Inclusive Language</Link>.

develop-docs/development/environment/index.mdx

@@ -24,7 +24,7 @@ NOTE: After running `devenv sync` you may need to restart your terminal to conti
 
 ## Running the Development Server
 
-The `devservices` ensure that you have all the services required for local development running. See the [devservices docs](/services/devservices/) for more information on managing services.
+The `devservices` ensure that you have all the services required for local development running. See the [devservices docs](/development/devservices/) for more information on managing services.
 When setting up `sentry`, execute the following command in the `sentry` folder:
 
 ```shell

develop-docs/development/testing.mdx

@@ -28,7 +28,7 @@ sentry devservices down --project test && sentry devservices up
 
 When using the `--project` option you can confirm which containers are running
 `docker ps`. Each running container should be prefixed with `test_`. See the
-[devservices docs](/services/devservices/) section for more information on
+[devservices docs](/development/devservices/) section for more information on
 managing services.
 
 ## Python Tests