From 17a872325869557362bb1e86e4d8ac488b8de980 Mon Sep 17 00:00:00 2001 From: paulj Date: Tue, 4 Nov 2025 11:03:26 -0500 Subject: [PATCH 1/2] fix incorrect urls --- docs/platforms/dart/guides/flutter/troubleshooting.mdx | 2 +- .../guides/aws-lambda/install/cjs-npm__v9.x.mdx | 2 +- .../javascript/guides/aws-lambda/install/index__v9.x.mdx | 4 ++-- .../javascript/guides/aws-lambda/install/layer__v8.x.mdx | 4 ++-- .../javascript/guides/aws-lambda/install/layer__v9.x.mdx | 4 ++-- .../javascript/guides/aws-lambda/install/npm__v9.x.mdx | 8 ++++---- 6 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/platforms/dart/guides/flutter/troubleshooting.mdx b/docs/platforms/dart/guides/flutter/troubleshooting.mdx index c7fb9d4b96dbf..adfe85ed7d22e 100644 --- a/docs/platforms/dart/guides/flutter/troubleshooting.mdx +++ b/docs/platforms/dart/guides/flutter/troubleshooting.mdx @@ -57,7 +57,7 @@ This happens because Dart's async/await implementation can cause stack trace inf ### What Can You Do? In order to get better debugging information for these cases you can: -- 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 +- 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 - Consider using [Sentry's Structured Logs](/platforms/dart/logs/) to capture additional debugging data alongside your errors ## Support 16 KB Page Sizes on Android diff --git a/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx index 10b3beff0a552..1418e777f7d9d 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx @@ -11,7 +11,7 @@ In this guide you will learn how to set up the `@sentry/aws-serverless` SDK for We recommend starting the SDK automatically via environment variables so that you only have to make minimal code changes to your lambda function. If you need more control over the SDK setup, you can also [initialize the SDK in in code](#alternative-initialize-the-sdk-in-code). -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. +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. ## 1. Prerequisites diff --git a/docs/platforms/javascript/guides/aws-lambda/install/index__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/index__v9.x.mdx index a1be846aba719..27303bf92530b 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/index__v9.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/index__v9.x.mdx @@ -18,11 +18,11 @@ Note that TypeScript can also be configured to output ESM, in which case you sho ### My Lambda function uses `require` -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). +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). ### My Lambda function uses `import` -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). +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). ### Can I use the Lambda layer for ESM functions? diff --git a/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx index a46d75759425c..ab5246299ff56 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx @@ -8,13 +8,13 @@ noindex: true og_image: /og-images/platforms-javascript-guides-aws-lambda-install-layer__v8.x.png --- -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). +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). If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code. 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. -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). +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). diff --git a/docs/platforms/javascript/guides/aws-lambda/install/layer__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/layer__v9.x.mdx index 1d4ab9da52ac3..56b72c91a802c 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/layer__v9.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/layer__v9.x.mdx @@ -7,13 +7,13 @@ sidebar_order: 1 og_image: /og-images/platforms-javascript-guides-aws-lambda-install-layer__v9.x.png --- -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). +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). If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code. 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. -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). +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). diff --git a/docs/platforms/javascript/guides/aws-lambda/install/npm__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/npm__v9.x.mdx index b6fec3a516705..ecbc8c578957c 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/npm__v9.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/npm__v9.x.mdx @@ -8,13 +8,13 @@ Based on whether your Lambda function runs in CommonJS or ESM, you need to follo ## My Lambda function is written in TypeScript -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). -Note that TypeScript can also be configured to output ESM, in which case you should follow the [ESM instructions](./esm-npm__v9.x). +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). +Note that TypeScript can also be configured to output ESM, in which case you should follow the [ESM instructions](./esm-npm__v9.x.mdx). ## My Lambda function uses `require` -If you are using `require()` in your function, follow the [CommonJS instructions](./cjs-npm__v9.x). +If you are using `require()` in your function, follow the [CommonJS instructions](./cjs-npm__v9.x.mdx). ## My Lambda function uses `import` -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). +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). From a26f4d7ad8e708f048e31dad6c181fc0d7ee33da Mon Sep 17 00:00:00 2001 From: paulj Date: Tue, 4 Nov 2025 11:13:09 -0500 Subject: [PATCH 2/2] fix typos --- develop-docs/sdk/telemetry/spans/span-api.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/develop-docs/sdk/telemetry/spans/span-api.mdx b/develop-docs/sdk/telemetry/spans/span-api.mdx index 4993fcaae1a4b..d86797c9949b3 100644 --- a/develop-docs/sdk/telemetry/spans/span-api.mdx +++ b/develop-docs/sdk/telemetry/spans/span-api.mdx @@ -7,7 +7,7 @@ title: Span API - The APIs specified in this documents MUST be implemented by all SDKs that don't use OpenTelemetry as their underlying tracing implementation. + The APIs specified in this document MUST be implemented by all SDKs that don't use OpenTelemetry as their underlying tracing implementation. SDKs using OTel SHOULD follow their own already established span APIs but MAY orient themselves on this document if applicable. @@ -19,7 +19,7 @@ This span has no parent span and groups together its children with a representat The topmost span within a service boundary is called the "Segment Span". Segment spans have a `parent_span_id` pointing to a "remote" span from the parent service. -For example, a distributed trace from backend to frontend, would have a segment span for the backend, and a segment span for the frotnend. +For example, a distributed trace from backend to frontend, would have a segment span for the backend, and a segment span for the frontend. The frontend segment span is also the root span of the entire span tree. SDKs MUST NOT expose names like "segment span" (e.g. in APIs) to users and SHOULD NOT (read "avoid") exposing "root span" if possible. @@ -52,7 +52,7 @@ interface Span { When implementing the span interface, consider the following guidelines: - SDKs MAY implement additional APIs, such as getters/setters for properties (e.g. `span.getStatus()`), or additional methods for convenience (e.g. `Span::spanContext()`). -- SDK implementers SHOULD dissalow direct mutation (without setters) of span properties such as the span name, depending on the plaform and the challenges involved. +- SDK implementers SHOULD disallow direct mutation (without setters) of span properties such as the span name, depending on the platform and the challenges involved. - SDK implementers MAY disallow direct read access to span properties, depending on the platform and the challenges involved. ## Span Starting APIs