Skip to content

Commit 6bf32a3

Browse files
jaffrepaulcleptric
andauthored
fix incorrect urls (#15400)
<!-- Use this checklist to make sure your PR is ready for merge. You may delete any sections you don't need. --> ## DESCRIBE YOUR PR - Resolve incorrect URLs that were being flagged by the Lint 404s check - Fix typos that were just merged ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [ ] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) --------- Co-authored-by: Michi Hoffmann <[email protected]>
1 parent e5df070 commit 6bf32a3

File tree

7 files changed

+14
-14
lines changed

7 files changed

+14
-14
lines changed

develop-docs/sdk/telemetry/spans/span-api.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ title: Span API
77
</Alert>
88

99
<Alert level="info">
10-
The APIs specified in this documents MUST be implemented by all SDKs that don't use OpenTelemetry as their underlying tracing implementation.
10+
The APIs specified in this document MUST be implemented by all SDKs that don't use OpenTelemetry as their underlying tracing implementation.
1111
SDKs using OTel SHOULD follow their own already established span APIs but MAY orient themselves on this document if applicable.
1212
</Alert>
1313

@@ -19,7 +19,7 @@ This span has no parent span and groups together its children with a representat
1919
The topmost span within a service boundary is called the "Segment Span".
2020
Segment spans have a `parent_span_id` pointing to a "remote" span from the parent service.
2121

22-
For example, a distributed trace from backend to frontend, would have a segment span for the backend, and a segment span for the frotnend.
22+
For example, a distributed trace from backend to frontend, would have a segment span for the backend, and a segment span for the frontend.
2323
The frontend segment span is also the root span of the entire span tree.
2424

2525
SDKs MUST NOT expose names like "segment span" (e.g. in APIs) to users and SHOULD NOT (read "avoid") exposing "root span" if possible.

docs/platforms/dart/guides/flutter/troubleshooting.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ This happens because Dart's async/await implementation can cause stack trace inf
5757
### What Can You Do?
5858

5959
In order to get better debugging information for these cases you can:
60-
- Add relevant context to your Sentry events using [custom tags](/platforms/dart/guides/flutter/data-management/tags/) and [breadcrumbs](/platforms/dart/guides/flutter/data-management/breadcrumbs/) for critical paths in your application
60+
- Add relevant context to your Sentry events using [custom tags](/platforms/dart/guides/flutter/enriching-events/tags/) and [breadcrumbs](/platforms/dart/guides/flutter/enriching-events/breadcrumbs/) for critical paths in your application
6161
- Consider using [Sentry's Structured Logs](/platforms/dart/logs/) to capture additional debugging data alongside your errors
6262

6363
## Support 16 KB Page Sizes on Android

docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ In this guide you will learn how to set up the `@sentry/aws-serverless` SDK for
1111
We recommend starting the SDK automatically via environment variables so that you only have to make minimal code changes to your lambda function.
1212
If you need more control over the SDK setup, you can also [initialize the SDK in in code](#alternative-initialize-the-sdk-in-code).
1313

14-
However, you need to modify your code and deploy the Sentry dependencies alongside your function code. If you're looking for the most simple way to set up Sentry, you might want to use the [Lambda Layer](./layer__v9.x) instead.
14+
However, you need to modify your code and deploy the Sentry dependencies alongside your function code. If you're looking for the most simple way to set up Sentry, you might want to use the [Lambda Layer](./layer__v9.x.mdx) instead.
1515

1616
## 1. Prerequisites
1717

docs/platforms/javascript/guides/aws-lambda/install/index__v9.x.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,11 @@ Note that TypeScript can also be configured to output ESM, in which case you sho
1818

1919
### My Lambda function uses `require`
2020

21-
If you are using `require()` in your function, follow the CommonJS instructions. Choose between [using our Lambda Layer (recommended)](./install/layer__v9.x) or [installing the Sentry AWS NPM package](./install/npm__v9.x).
21+
If you are using `require()` in your function, follow the CommonJS instructions. Choose between [using our Lambda Layer (recommended)](./install/layer__v9.x.mdx) or [installing the Sentry AWS NPM package](./install/npm__v9.x.mdx).
2222

2323
### My Lambda function uses `import`
2424

25-
If you're using `import` syntax in your function and you're _not_ transpiling the code to CommonJS, follow the [ESM instructions](./install/esm-npm__v9.x).
25+
If you're using `import` syntax in your function and you're _not_ transpiling the code to CommonJS, follow the [ESM instructions](./install/esm-npm__v9.x.mdx).
2626

2727
### Can I use the Lambda layer for ESM functions?
2828

docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,13 @@ noindex: true
88
og_image: /og-images/platforms-javascript-guides-aws-lambda-install-layer__v8.x.png
99
---
1010

11-
The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/Lambda/latest/dg/configuration-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](../install/npm).
11+
The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/Lambda/latest/dg/configuration-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](../install/npm.mdx).
1212
If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code.
1313
To actually start the SDK, you can decide between setting up the SDK using environment variables or in your Lambda function code. We recommend using environment variables as it's the easiest way to get started. [Initializing the SDK in code](#alternative-initialize-the-sdk-in-code) instead of setting environment variables gives you more control over the SDK setup if you need it.
1414

1515
<Alert>
1616

17-
This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](../install/npm).
17+
This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](../install/npm.mdx).
1818

1919
</Alert>
2020

docs/platforms/javascript/guides/aws-lambda/install/layer__v9.x.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,13 @@ sidebar_order: 1
77
og_image: /og-images/platforms-javascript-guides-aws-lambda-install-layer__v9.x.png
88
---
99

10-
The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/lambda/latest/dg/adding-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](./npm__v9.x).
10+
The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/lambda/latest/dg/adding-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](./npm__v9.x.mdx).
1111
If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code.
1212
To actually start the SDK, you can decide between setting up the SDK using environment variables or in your Lambda function code. We recommend using environment variables as it's the easiest way to get started. [Initializing the SDK in code](#alternative-initialize-the-sdk-in-code) instead of setting environment variables gives you more control over the SDK setup if you need it.
1313

1414
<Alert>
1515

16-
This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](../npm__v9.x).
16+
This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](../npm__v9.x.mdx).
1717

1818
</Alert>
1919

docs/platforms/javascript/guides/aws-lambda/install/npm__v9.x.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,13 @@ Based on whether your Lambda function runs in CommonJS or ESM, you need to follo
88

99
## My Lambda function is written in TypeScript
1010

11-
If you're using TypeScript, your lambda function is likely transpiled to CommonJS before running it. In this case, follow the [CommonJS instructions](./cjs-npm__v9.x).
12-
Note that TypeScript can also be configured to output ESM, in which case you should follow the [ESM instructions](./esm-npm__v9.x).
11+
If you're using TypeScript, your lambda function is likely transpiled to CommonJS before running it. In this case, follow the [CommonJS instructions](./cjs-npm__v9.x.mdx).
12+
Note that TypeScript can also be configured to output ESM, in which case you should follow the [ESM instructions](./esm-npm__v9.x.mdx).
1313

1414
## My Lambda function uses `require`
1515

16-
If you are using `require()` in your function, follow the [CommonJS instructions](./cjs-npm__v9.x).
16+
If you are using `require()` in your function, follow the [CommonJS instructions](./cjs-npm__v9.x.mdx).
1717

1818
## My Lambda function uses `import`
1919

20-
If you're using `import` syntax in your function and you're _not_ transpiling the code to CommonJS, follow the [ESM instructions](./esm-npm__v9.x).
20+
If you're using `import` syntax in your function and you're _not_ transpiling the code to CommonJS, follow the [ESM instructions](./esm-npm__v9.x.mdx).

0 commit comments

Comments
 (0)