Skip to content

Commit dfbfb42

Browse files
committed
fix: typos in sdks and llm rules
1 parent 9857642 commit dfbfb42

File tree

6 files changed

+6
-6
lines changed

6 files changed

+6
-6
lines changed

develop-docs/sdk/miscellaneous/hub_and_scope_refactoring.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Hubs and scopes is a complicated system, that can easily be misused (also see [h
3131

3232
## B) What Is the Outcome of the Refactoring?
3333

34-
1. The SDKs model of Scope forking is aligned with the one from OTel. Paving the way for making it possble to use OTel tooling for performance monitoring and still see their data in Sentry. (And Sentry error events are still connected to the spans captured by OTel).
34+
1. The SDKs model of Scope forking is aligned with the one from OTel. Paving the way for making it possible to use OTel tooling for performance monitoring and still see their data in Sentry. (And Sentry error events are still connected to the spans captured by OTel).
3535
2. The new Scopes API is implemented in the API and can be used.
3636
3. The old `Hub` based API still works as expected for backwards compatibility. After a transition phase the `Hub` will be removed in a major update of the SDK.
3737

develop-docs/sdk/philosophy.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ At no point should a customer upgrade the library and find themselves in a situa
4949

5050
## Enable Customers
5151

52-
While we generally should try to keep the API surfaces of SDKs reasonable small. At the same time we also need to make sure that we enable customers to achieve their goals. Think about cases that the SDK maybe wouldn't be able to solve out of the box. If there are enough APIs that customers can use our SDKs in more creative ways, we generally see this as a added benefit.
52+
While we generally should try to keep the API surfaces of SDKs reasonable small. At the same time we also need to make sure that we enable customers to achieve their goals. Think about cases that the SDK maybe wouldn't be able to solve out of the box. If there are enough APIs that customers can use our SDKs in more creative ways, we generally see this as an added benefit.
5353

5454
## Handle PII and Sensitive Data with Care
5555

platform-includes/llm-rules-platform/_default.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ These examples should be used as guidance when configuring Sentry functionality
1515

1616
# Tracing Examples
1717

18-
- Spans should be created for meaningful actions within an applications like button clicks, API calls, and function calls
18+
- Spans should be created for meaningful actions within applications like button clicks, API calls, and function calls
1919
- Use the `Sentry.startSpan` function to create a span
2020
- Child spans can exist within a parent span
2121

platform-includes/llm-rules-platform/javascript.nextjs.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ These examples should be used as guidance when configuring Sentry functionality
1515

1616
# Tracing Examples
1717

18-
- Spans should be created for meaningful actions within an applications like button clicks, API calls, and function calls
18+
- Spans should be created for meaningful actions within applications like button clicks, API calls, and function calls
1919
- Use the `Sentry.startSpan` function to create a span
2020
- Child spans can exist within a parent span
2121

platform-includes/llm-rules-platform/javascript.node.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ These examples should be used as guidance when configuring Sentry functionality
1515

1616
# Tracing Examples
1717

18-
- Spans should be created for meaningful actions within an applications like button clicks, API calls, and function calls
18+
- Spans should be created for meaningful actions within applications like button clicks, API calls, and function calls
1919
- Ensure you are creating custom spans with meaningful names and operations
2020
- Use the `Sentry.startSpan` function to create a span
2121
- Child spans can exist within a parent span

platform-includes/llm-rules-platform/javascript.react.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ These examples should be used as guidance when configuring Sentry functionality
1515

1616
# Tracing Examples
1717

18-
- Spans should be created for meaningful actions within an applications like button clicks, API calls, and function calls
18+
- Spans should be created for meaningful actions within applications like button clicks, API calls, and function calls
1919
- Ensure you are creating custom spans with meaningful names and operations
2020
- Use the `Sentry.startSpan` function to create a span
2121
- Child spans can exist within a parent span

0 commit comments

Comments
 (0)