fix: typos in sdks and llm rules (#15149)

<!-- Use this checklist to make sure your PR is ready for merge. You may
delete any sections you don't need. -->

## DESCRIBE YOUR PR

I basically went over couple of docs and saw minor typos.

## 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 -->
- [x] 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/)

Author: JPeer264

develop-docs/sdk/miscellaneous/hub_and_scope_refactoring.mdx

@@ -31,7 +31,7 @@ Hubs and scopes is a complicated system, that can easily be misused (also see [h
 
 ## B) What Is the Outcome of the Refactoring?
 
-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).
+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).
 2. The new Scopes API is implemented in the API and can be used.
 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.
 

develop-docs/sdk/philosophy.mdx

@@ -49,7 +49,7 @@ At no point should a customer upgrade the library and find themselves in a situa
 
 ## Enable Customers
 
-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.
+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.
 
 ## Handle PII and Sensitive Data with Care
 

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

@@ -15,7 +15,7 @@ These examples should be used as guidance when configuring Sentry functionality
 
 # Tracing Examples
 
-- Spans should be created for meaningful actions within an applications like button clicks, API calls, and function calls
+- Spans should be created for meaningful actions within applications like button clicks, API calls, and function calls
 - Use the `Sentry.startSpan` function to create a span
 - Child spans can exist within a parent span
 

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

@@ -15,7 +15,7 @@ These examples should be used as guidance when configuring Sentry functionality
 
 # Tracing Examples
 
-- Spans should be created for meaningful actions within an applications like button clicks, API calls, and function calls
+- Spans should be created for meaningful actions within applications like button clicks, API calls, and function calls
 - Use the `Sentry.startSpan` function to create a span
 - Child spans can exist within a parent span
 

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

@@ -15,7 +15,7 @@ These examples should be used as guidance when configuring Sentry functionality
 
 # Tracing Examples
 
-- Spans should be created for meaningful actions within an applications like button clicks, API calls, and function calls
+- Spans should be created for meaningful actions within applications like button clicks, API calls, and function calls
 - Ensure you are creating custom spans with meaningful names and operations
 - Use the `Sentry.startSpan` function to create a span
 - Child spans can exist within a parent span

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

@@ -15,7 +15,7 @@ These examples should be used as guidance when configuring Sentry functionality
 
 # Tracing Examples
 
-- Spans should be created for meaningful actions within an applications like button clicks, API calls, and function calls
+- Spans should be created for meaningful actions within applications like button clicks, API calls, and function calls
 - Ensure you are creating custom spans with meaningful names and operations
 - Use the `Sentry.startSpan` function to create a span
 - Child spans can exist within a parent span