diff --git a/docs/platforms/dotnet/common/configuration/disable-integrations.mdx b/docs/platforms/dotnet/common/configuration/disable-integrations.mdx index a339774f820c1..cc3e32233be92 100644 --- a/docs/platforms/dotnet/common/configuration/disable-integrations.mdx +++ b/docs/platforms/dotnet/common/configuration/disable-integrations.mdx @@ -4,7 +4,7 @@ sidebar_order: 200 description: "Learn more about the methods that disable integrations." --- -All of Sentry’s SDKs provide integrations, which extend functionality of the SDK. Most integrations are enabled by default, though you can disable them if needed. +The SDK provides integrations, which extend functionality of the SDK. Most integrations are enabled by default, though you can disable them if needed. # Options diff --git a/docs/platforms/dotnet/common/configuration/draining.mdx b/docs/platforms/dotnet/common/configuration/draining.mdx index 18f4f92ac74db..0f9f54a357a23 100644 --- a/docs/platforms/dotnet/common/configuration/draining.mdx +++ b/docs/platforms/dotnet/common/configuration/draining.mdx @@ -11,7 +11,6 @@ notSupported: - unreal --- -The default behavior of most SDKs is to send out events over the network -asynchronously in the background. This means that some events might be lost if the application shuts down unexpectedly. The SDKs provide mechanisms to cope with this. +By default the SDK sends out events over the network on a background thread. This means that some events might be lost if the application shuts down unexpectedly. The SDK provides mechanisms to cope with this. diff --git a/docs/platforms/dotnet/common/configuration/filtering.mdx b/docs/platforms/dotnet/common/configuration/filtering.mdx index ccfb6cdf672a6..76a1a75666cf4 100644 --- a/docs/platforms/dotnet/common/configuration/filtering.mdx +++ b/docs/platforms/dotnet/common/configuration/filtering.mdx @@ -6,7 +6,7 @@ sidebar_order: 60 When you add Sentry to your app, you get a lot of valuable information about errors and performance. And lots of information is good -- as long as it's the right information, at a reasonable volume. -The Sentry SDKs have several configuration options to help you filter out events. +The SDK has several configuration options to help you filter out events. We also offer [Inbound Filters](/concepts/data-management/filtering/) to filter events in sentry.io. We recommend filtering at the client level though, because it removes the overhead of sending events you don't actually want. Learn more about the [fields available in an event](https://develop.sentry.dev/sdk/data-model/event-payloads/). @@ -16,7 +16,7 @@ To prevent certain errors from being reported to Sentry, use the -All Sentry SDKs support the callback method. Because it's called immediately before the event is sent to the server, this is your last chance to decide not to send data or to edit it. receives the event object as a parameter, which you can use to either modify the event’s data or drop it completely by returning `null`, based on custom logic and the data available on the event. +The SDK supports the callback method. Because it's called immediately before the event is sent to the server, this is your last chance to decide not to send data or to edit it. receives the event object as a parameter, which you can use to either modify the event's data or drop it completely by returning `null`, based on custom logic and the data available on the event. diff --git a/docs/platforms/dotnet/common/configuration/options.mdx b/docs/platforms/dotnet/common/configuration/options.mdx index 94040e2ff2d83..2f3224bd3746f 100644 --- a/docs/platforms/dotnet/common/configuration/options.mdx +++ b/docs/platforms/dotnet/common/configuration/options.mdx @@ -109,7 +109,7 @@ Sets the distribution of the application. Distributions are used to disambiguate -Sets the release. Some SDKs will try to automatically configure a release out of the box but it's a better idea to manually set it to guarantee that the release is in sync with your deploy integrations or source map uploads. Release names are strings, but some formats are detected by Sentry and might be rendered differently. Learn more about how to send release data so Sentry can tell you about regressions between releases and identify the potential source in [the releases documentation](/product/releases/) or the sandbox. +Sets the release. The SDK will try to automatically configure a release out of the box but it's a better idea to manually set it to guarantee that the release is in sync with your deploy integrations or source map uploads. Release names are strings, but some formats are detected by Sentry and might be rendered differently. Learn more about how to send release data so Sentry can tell you about regressions between releases and identify the potential source in [the releases documentation](/product/releases/) or the sandbox. By default the SDK will try to read this value from the `SENTRY_RELEASE` environment variable (in the browser SDK, this will be read off of the `window.SENTRY_RELEASE.id` if available). @@ -139,7 +139,7 @@ This variable controls the total amount of breadcrumbs that should be captured. -The maximum number of [envelopes](https://develop.sentry.dev/sdk/data-model/envelopes/) to keep in cache. The SDKs use envelopes to send data, such as events, attachments, user feedback, and sessions to sentry.io. An envelope can contain multiple items, such as an event with a session and two attachments. Depending on the usage of the SDK, the size of an envelope can differ. If the number of envelopes in the local cache exceeds `max-cache-items`, the SDK deletes the oldest envelope and migrates the sessions to the next envelope to maintain the integrity of your release health stats. The default is `30`. +The maximum number of [envelopes](https://develop.sentry.dev/sdk/data-model/envelopes/) to keep in cache. The SDK uses envelopes to send data, such as events, attachments, user feedback, and sessions to sentry.io. An envelope can contain multiple items, such as an event with a session and two attachments. Depending on the usage of the SDK, the size of an envelope can differ. If the number of envelopes in the local cache exceeds `max-cache-items`, the SDK deletes the oldest envelope and migrates the sessions to the next envelope to maintain the integrity of your release health stats. The default is `30`. @@ -198,7 +198,7 @@ This option can be overridden using . This parameter controls whether integrations should capture HTTP request bodies. It can be set to one of the following values: - `none`: **default** Request bodies are never sent. -- `small`: Only small request bodies will be captured. The cutoff for small depends on the SDK (typically 4KB). +- `small`: Only small request bodies will be captured (typically 4KB). - `medium`: Medium and small requests will be captured (typically 10KB). - `always`: The SDK will always capture the request body as long as Sentry can make sense of it. @@ -235,7 +235,7 @@ These options can be used to hook the SDK in various ways to customize the repor -This function is called with an SDK-specific message or error event object, and can return a modified event object, or `null` to skip reporting the event. This can be used, for instance, for manual PII stripping before sending. +This function is called with the event payload, and can return a modified event object, or `null` to skip reporting the event. This can be used, for instance, for manual PII stripping before sending. By the time is executed, all scope data has already been applied to the event. Further modification of the scope won't have any effect. @@ -245,14 +245,14 @@ When filtering based on exception types, the original exception (including any ` -This function is called with an SDK-specific breadcrumb object before the breadcrumb is added to the scope. When nothing is returned from the function, the breadcrumb is dropped. To pass the breadcrumb through, return the first argument, which contains the breadcrumb object. +This function is called with a breadcrumb object before the breadcrumb is added to the scope. When `null` is returned from the function, the breadcrumb is dropped. To pass the breadcrumb through, return the first argument, which contains the breadcrumb object. The callback typically gets a second argument (called a "hint") which contains the original object from which the breadcrumb was created to further customize what the breadcrumb should look like. -This function is called with an SDK-specific transaction object, and can return a modified transaction object, or `null` to skip reporting the transaction. This can be used, for instance, for manual PII-stripping before sending. +This function is called with a transaction object, and can return a modified transaction object, or `null` to skip reporting the transaction. This can be used, for instance, for manual PII-stripping before sending. By the time is executed, all scope data has already been applied to the event and further modification of the scope won't have any effect. @@ -264,13 +264,13 @@ Transports are used to send events to Sentry. Transports can be customized to so -Switches out the transport used to send events. How this works depends on the SDK. It can, for instance, be used to capture events for unit-testing or to send it through some more complex setup that requires proxy authentication. +Switches out the transport used to send events. It can, for instance, be used to capture events for unit-testing or to send it through some more complex setup that requires proxy authentication. -When set, a proxy can be configured that should be used for outbound requests. This is also used for HTTPS requests unless a separate `https-proxy` is configured. However, not all SDKs support a separate HTTPS proxy. SDKs will attempt to default to the system-wide configured proxy, if possible. For instance, on Unix systems, the `http_proxy` environment variable will be picked up. +When set, a proxy can be configured that should be used for outbound requests. This is also used for HTTPS requests. A separate HTTPS proxy is currently not supported. The SDK will attempt to default to the system-wide configured proxy, if possible. For instance, on Unix systems, the `http_proxy` environment variable will be picked up. @@ -320,7 +320,7 @@ The default is `1` (one) second. -Controls how many seconds to wait before shutting down. Sentry SDKs send events from a background queue. This queue is given a certain amount to drain pending events. The default is SDK specific but typically around two seconds. Setting this value too low may cause problems for sending events from command line applications. Setting the value too high will cause the application to block for a long time for users experiencing network connectivity problems. +Controls how many seconds to wait before shutting down. The SDK sends events from a background queue. This queue is given a certain amount to drain pending events. Setting this value too low may cause problems for sending events from command line applications. Setting the value too high will cause the application to block for a long time for users experiencing network connectivity problems. diff --git a/docs/platforms/dotnet/common/configuration/releases.mdx b/docs/platforms/dotnet/common/configuration/releases.mdx index 9b216705b1750..4b08068dd7871 100644 --- a/docs/platforms/dotnet/common/configuration/releases.mdx +++ b/docs/platforms/dotnet/common/configuration/releases.mdx @@ -33,7 +33,7 @@ In order to monitor release health, the SDK sends session data. ### Sessions -A session represents the interaction between the user and the application. Sessions contain a timestamp, a status (if the session was OK or if it crashed), and are always linked to a release. Most Sentry SDKs can manage sessions automatically. +A session represents the interaction between the user and the application. Sessions contain a timestamp, a status (if the session was OK or if it crashed), and are always linked to a release. The SDK can manage sessions automatically. diff --git a/docs/platforms/dotnet/common/configuration/sampling.mdx b/docs/platforms/dotnet/common/configuration/sampling.mdx index e714c315cfb2b..5e0493660882f 100644 --- a/docs/platforms/dotnet/common/configuration/sampling.mdx +++ b/docs/platforms/dotnet/common/configuration/sampling.mdx @@ -31,7 +31,7 @@ Choose a sampling rate with the goal of finding a balance between performance an ## Configuring the Transaction Sample Rate -The Sentry SDKs have two configuration options to control the volume of transactions sent to Sentry, allowing you to take a representative sample: +The SDK has two configuration options to control the volume of transactions sent to Sentry, allowing you to take a representative sample: 1. Uniform sample rate (): @@ -58,8 +58,6 @@ By default, none of these options are set, meaning no transactions will be sent ### Default Sampling Context Data -The information contained in the object passed to the when a transaction is created varies by platform and integration. - ### Custom Sampling Context Data diff --git a/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx b/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx index 0dccdba9c0713..c22f78a19eb8d 100644 --- a/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx @@ -19,7 +19,7 @@ These are some great examples for data scrubbing that every company should think We offer the following options depending on your legal and operational needs: -- filtering or scrubbing sensitive data within the SDK, so that data is _not sent to_ Sentry. Different SDKs have different capabilities, and configuration changes require a redeployment of your application. +- filtering or scrubbing sensitive data within the SDK, so that data is _not sent to_ Sentry. Configuration changes require a redeployment of your application. - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events. - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying. @@ -33,7 +33,7 @@ If you are using Sentry in your mobile app, read our [frequently asked questions ## Personally Identifiable Information (PII) -Our newer SDKs do not purposefully send PII to stay on the safe side. This behavior is controlled by an option called [`send-default-pii`](../../configuration/options/#SendDefaultPii). +The SDK purposefully does not send PII to stay on the safe side. This behavior is controlled by an option called [`SendDefaultPii`](../../configuration/options/#SendDefaultPii). Turning this option on is required for certain features in Sentry to work, but also means you will need to be even more careful about what data is being sent to Sentry (using the options below). @@ -43,7 +43,7 @@ If you _do not_ wish to use the default PII behavior, you can also choose to ide ### & -SDKs provide a hook, which is invoked before an error or message event is sent and can be used to modify event data to remove sensitive information. Some SDKs also provide a hook which does the same thing for transactions. We recommend using and in the SDKs to **scrub any data before it is sent**, to ensure that sensitive data never leaves the local environment. +The SDK provides a hook, which is invoked before an error or message event is sent and can be used to modify event data to remove sensitive information. The SDK also provide a hook which does the same thing for transactions. We recommend using and in the SDK to **scrub any data before it is sent**, to ensure that sensitive data never leaves the local environment. diff --git a/docs/platforms/dotnet/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/dotnet/common/enriching-events/breadcrumbs/index.mdx index 95a268ad88192..2ae98d34252bf 100644 --- a/docs/platforms/dotnet/common/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/dotnet/common/enriching-events/breadcrumbs/index.mdx @@ -29,8 +29,8 @@ Manually record a breadcrumb: ## Customize Breadcrumbs -SDKs allow you to customize breadcrumbs through the hook. +The SDK allows you to customize breadcrumbs through the hook. -This hook is passed an already assembled breadcrumb and, in some SDKs, an optional hint. The function can modify the breadcrumb or decide to discard it entirely by returning `null`: +This hook is passed an already assembled breadcrumb and, optionally, a `hint` object containing extra metadata. The function can modify the breadcrumb or decide to discard it entirely by returning `null`: diff --git a/docs/platforms/dotnet/common/enriching-events/context/index.mdx b/docs/platforms/dotnet/common/enriching-events/context/index.mdx index 3c36bc77e1f8b..4df453834379f 100644 --- a/docs/platforms/dotnet/common/enriching-events/context/index.mdx +++ b/docs/platforms/dotnet/common/enriching-events/context/index.mdx @@ -29,7 +29,7 @@ Learn more about conventions for common contexts in the [contexts interface deve When sending context, _consider payload size limits_. Sentry does not recommend sending the entire application state and large data blobs in contexts. If you exceed the maximum payload size, Sentry will respond with HTTP error `413 Payload Too Large` and reject the event. -The Sentry SDK will try its best to accommodate the data you send and trim large context payloads. Some SDKs can truncate parts of the event; for more details, see the [developer documentation on SDK data handling](https://develop.sentry.dev/sdk/expected-features/data-handling/). +The Sentry SDK will try its best to accommodate the data you send and trim large context payloads. The SDK may truncate parts of the event; for more details, see the [developer documentation on SDK data handling](https://develop.sentry.dev/sdk/expected-features/data-handling/). ## Additional Data diff --git a/docs/platforms/dotnet/common/enriching-events/identify-user/index.mdx b/docs/platforms/dotnet/common/enriching-events/identify-user/index.mdx index 242b1077788c4..35b2a863cfd53 100644 --- a/docs/platforms/dotnet/common/enriching-events/identify-user/index.mdx +++ b/docs/platforms/dotnet/common/enriching-events/identify-user/index.mdx @@ -28,11 +28,9 @@ An alternative, or addition, to the username. Sentry is aware of email addresses ### `ip_address` The user's IP address. If the user is unauthenticated, Sentry uses the IP address as a unique identifier for the user. -Serverside SDKs that instrument incoming requests will attempt to pull the IP address from the HTTP request data (`request.env.REMOTE_ADDR` field in JSON), if available. That might require set to `true` in the SDK options. +The SDK will attempt to pull the IP address from the HTTP request data on incoming requests (`request.env.REMOTE_ADDR` field in JSON), if available. That requires set to `true` in the SDK options. -If the user's `ip_address` is set to `"{{auto}}"`, Sentry will infer the IP address from the connection between your app and Sentry's server. - -If the field is omitted, the default value is `null`. However, due to backwards compatibility concerns, certain platforms (in particular JavaScript) have a different default value for `"{{auto}}"`. SDKs and other clients should not rely on this behavior and should set IP addresses or `"{{auto}}"` explicitly. +If the user's `ip_address` is set to `"{{auto}}"`, Sentry will infer the IP address from the connection between your app and Sentry's server. If the field is omitted, the default value is `null`. To opt out of storing users' IP addresses in your event data, you can go to your project settings, click on "Security & Privacy", and enable "Prevent Storing of IP Addresses" or use Sentry's [server-side data](/security-legal-pii/scrubbing/) scrubbing to remove `$user.ip_address`. Adding such a rule ultimately overrules any other logic. diff --git a/docs/platforms/dotnet/common/enriching-events/scopes/index.mdx b/docs/platforms/dotnet/common/enriching-events/scopes/index.mdx index c70db4f1f633c..3472e45ed57d6 100644 --- a/docs/platforms/dotnet/common/enriching-events/scopes/index.mdx +++ b/docs/platforms/dotnet/common/enriching-events/scopes/index.mdx @@ -1,16 +1,15 @@ --- title: Scopes and Hubs -description: "SDKs will typically automatically manage the scopes for you in the framework integrations. Learn what a scope is and how you can use it to your advantage." +description: "The SDK will in most cases automatically manage the scopes for you in the framework integrations. Learn what a scope is and how you can use it to your advantage." --- -When an event is captured and sent to Sentry, SDKs will merge that event data with extra -information from the current scope. SDKs will typically automatically manage the scopes -for you in the framework integrations and you don't need to think about them. However, +When an event is captured and sent to Sentry, the SDK will merge that event data with extra +information from the current scope. The SDK will in most cases automatically manage the scopes for you in the framework integrations and you don't need to think about them. However, you should know what a scope is and how you can use it for your advantage. ## What's a Scope, What's a Hub -You can think of the hub as the central point that our SDKs use to route an +You can think of the hub as the central point that the SDK uses to route an event to Sentry. When you call `init()` a hub is created and a client and a blank scope are created on it. That hub is then associated with the current thread and will internally hold a stack of scopes. diff --git a/docs/platforms/dotnet/common/tracing/instrumentation/performance-metrics.mdx b/docs/platforms/dotnet/common/tracing/instrumentation/performance-metrics.mdx index 7115f88f18c31..8955adc964609 100644 --- a/docs/platforms/dotnet/common/tracing/instrumentation/performance-metrics.mdx +++ b/docs/platforms/dotnet/common/tracing/instrumentation/performance-metrics.mdx @@ -4,7 +4,7 @@ description: "Learn how to attach performance metrics to your transactions." sidebar_order: 20 --- -Sentry's SDKs support sending performance metrics data to Sentry. These are numeric values attached to transactions that are aggregated and displayed in Sentry. +The SDK supports sending performance metrics data to Sentry. These are numeric values attached to transactions that are aggregated and displayed in Sentry. ## Custom Measurements diff --git a/docs/platforms/dotnet/common/usage/index.mdx b/docs/platforms/dotnet/common/usage/index.mdx index fe3b5bc407b66..cba2a1562fa25 100644 --- a/docs/platforms/dotnet/common/usage/index.mdx +++ b/docs/platforms/dotnet/common/usage/index.mdx @@ -28,7 +28,7 @@ While capturing an event, you can also record the breadcrumbs that lead up to th ## Capturing Messages -Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually. +Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDK doesn't automatically capture messages, but you can capture them manually. Messages show up as issues on your issue stream, with the message as the issue name. diff --git a/docs/platforms/dotnet/common/usage/sdk-fingerprinting/index.mdx b/docs/platforms/dotnet/common/usage/sdk-fingerprinting/index.mdx index 9bc4a4d4b772c..1ad207b349b4e 100644 --- a/docs/platforms/dotnet/common/usage/sdk-fingerprinting/index.mdx +++ b/docs/platforms/dotnet/common/usage/sdk-fingerprinting/index.mdx @@ -11,7 +11,7 @@ By default, Sentry will run one of our built-in grouping algorithms to generate 1. In your SDK, using SDK Fingerprinting, as documented below 2. In your project, using [Fingerprint Rules](/concepts/data-management/event-grouping/fingerprint-rules/) or [Stack Trace Rules](/concepts/data-management/event-grouping/stack-trace-rules/) -In supported SDKs, you can override Sentry's default grouping that passes the fingerprint attribute as an array of strings. The length of a fingerprint's array is not restricted. This works similarly to the [fingerprint rules functionality](/concepts/data-management/event-grouping/fingerprint-rules/), which is always available and can achieve similar results. +You can override Sentry's default grouping that passes the fingerprint attribute as an array of strings. The length of a fingerprint's array is not restricted. This works similarly to the [fingerprint rules functionality](/concepts/data-management/event-grouping/fingerprint-rules/), which can achieve similar results. ## Basic Example diff --git a/docs/platforms/dotnet/guides/aspnetcore/index.mdx b/docs/platforms/dotnet/guides/aspnetcore/index.mdx index a97db264a3479..e6c242f283f9f 100644 --- a/docs/platforms/dotnet/guides/aspnetcore/index.mdx +++ b/docs/platforms/dotnet/guides/aspnetcore/index.mdx @@ -218,7 +218,7 @@ Methods that take precedence over `IHostingEnvironment` are: This parameter controls whether integrations should capture HTTP request bodies. It can be set to one of the following values: - `None`: Request bodies are never sent. -- `Small`: Only small request bodies will be captured. The cutoff for small depends on the SDK (typically 4KB). +- `Small`: Only small request bodies will be captured (typically 4KB). - `Medium`: Medium and small requests will be captured (typically 10KB). - `Always`: The SDK will always capture the request body as long as Sentry can make sense of it. diff --git a/docs/platforms/dotnet/guides/xamarin/data-management/apple-privacy-manifest.mdx b/docs/platforms/dotnet/guides/xamarin/data-management/apple-privacy-manifest.mdx index cabb53ef660b6..54b8734a05f5f 100644 --- a/docs/platforms/dotnet/guides/xamarin/data-management/apple-privacy-manifest.mdx +++ b/docs/platforms/dotnet/guides/xamarin/data-management/apple-privacy-manifest.mdx @@ -8,7 +8,7 @@ sidebar_order: 50 This guide requires [@sentry/xamarin@2.1.0](https://github.com/getsentry/sentry-xamarin/releases/tag/2.1.0) or newer. -Sentry's SDKs provide error and tracing for mobile applications running on Apple devices. To do this, the SDK needs to access certain information about the device and the application. Some of the APIs required for this are considered privacy-relevant by Apple. In order to submit apps to the App Store, Apple requires all apps - and libraries used within these apps - to provide privacy manifest files stating which APIs are used under which allowed reasons. For more details, read Apple's guidelines on [Describing use of required reason API](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api). +The Sentry SDK provides error and tracing for mobile applications running on Apple devices. To do this, the SDK needs to access certain information about the device and the application. Some of the APIs required for this are considered privacy-relevant by Apple. In order to submit apps to the App Store, Apple requires all apps - and libraries used within these apps - to provide privacy manifest files stating which APIs are used under which allowed reasons. For more details, read Apple's guidelines on [Describing use of required reason API](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api). The information and steps in this guide are still being worked on and might change because of new tools or updated [Apple requirements](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files). @@ -18,7 +18,7 @@ During the build process, the SDK will provide your project a privacy manifest f ## Before You Start -Note that the application privacy manifest covers all data usages (via `NSPrivacyCollectedDataTypes`) and API usages (via `NSPrivacyAccessedAPITypes`) for the *whole application* and *all included libraries*. The examples below reflect the current requirements for the Sentry SDKs alone. If you are using other libraries that access privacy-relevant APIs, you need to include them in the privacy manifest as well. +Note that the application privacy manifest covers all data usages (via `NSPrivacyCollectedDataTypes`) and API usages (via `NSPrivacyAccessedAPITypes`) for the *whole application* and *all included libraries*. The examples below reflect the current requirements for the Sentry SDK alone. If you are using other libraries that access privacy-relevant APIs, you need to include them in the privacy manifest as well. ## Create a Privacy Manifest diff --git a/docs/platforms/dotnet/guides/xamarin/index.mdx b/docs/platforms/dotnet/guides/xamarin/index.mdx index 4dd41a94aad02..fd69358494348 100644 --- a/docs/platforms/dotnet/guides/xamarin/index.mdx +++ b/docs/platforms/dotnet/guides/xamarin/index.mdx @@ -19,7 +19,7 @@ The SDK is compatible with the following versions or higher: ## Configure -After you’ve completed setting up a project in Sentry, Sentry will give you a value which we call a DSN or Data Source Name. It looks a lot like a standard URL, but it’s just a representation of the configuration required by the Sentry SDKs. It consists of a few pieces, including the protocol, public key, the server address, and the project identifier. +After you've completed setting up a project in Sentry, Sentry will give you a value which we call a DSN or Data Source Name. It looks a lot like a standard URL, but it's just a representation of the configuration required by the Sentry SDK. It consists of a few pieces, including the protocol, public key, the server address, and the project identifier. @@ -49,7 +49,7 @@ SentryXamarin.Init(options => ## Verify -Great! Now that you’ve completed setting up the SDK, maybe you want to quickly test out how Sentry works. Start by capturing an exception: +Great! Now that you've completed setting up the SDK, maybe you want to quickly test out how Sentry works. Start by capturing an exception: diff --git a/platform-includes/performance/default-sampling-context-platform/dotnet.mdx b/platform-includes/performance/default-sampling-context-platform/dotnet.mdx index be8f228ebd716..42a37fa53f385 100644 --- a/platform-includes/performance/default-sampling-context-platform/dotnet.mdx +++ b/platform-includes/performance/default-sampling-context-platform/dotnet.mdx @@ -1 +1 @@ -For .NET-based SDKs, it includes a [Transaction Context](https://github.com/getsentry/sentry-dotnet/blob/main/src/Sentry/TransactionContext.cs) and a custom sampling context (`string` to `object` dictionary). +The information contained in the object passed to the when a transaction is created includes a [Transaction Context](https://github.com/getsentry/sentry-dotnet/blob/main/src/Sentry/TransactionContext.cs) and a custom sampling context (`string` to `object` dictionary).