chore: Correct 'JavaScript' casing (#12569)

* chore: Correct JavaScript case

* some more codeblock casing

Author: ryan953

develop-docs/sdk/expected-features/setup-wizards/index.mdx

@@ -142,7 +142,7 @@ If you create a new prompt, make sure you wrap it with the [`abortIfCancelled`](
 This will take care of correctly handling Cmd+C inputs, flushing Sentry events (if using [telemetry](#telemetry)) and exiting the process.
 For example:
 
-```TypeScript
+```typescript
 const continueWithoutGit = await abortIfCancelled(
   clack.confirm({
     message:
@@ -236,7 +236,7 @@ This helps us understand how our users use the wizard, which actions they take a
 
 It's easiest to use the `withTelemetery` wrapper function that's available in the `@sentry/wizard` package:
 
-```TypeScript
+```typescript
 export async function runSourcemapsWizard(
   options: WizardOptions,
 ): Promise<void> {
@@ -254,7 +254,7 @@ This will create a minimal Sentry client and send events, such as sessions, tran
 
 If you want to add spans to individual steps within a wizard flow, you can use the `traceStep` helper function:
 
-```TypeScript
+```typescript
 const res = await traceStep('npm-script-setup', () => setupNpmScriptInCI());
 ```
 

develop-docs/sdk/platform-specifics/serverless-sdks/aws-lambda.mdx

@@ -3,9 +3,9 @@ title: AWS Lambda
 sidebar_order: 10
 ---
 
-Lambda functions can be written in numerous programming languages (Javascript,
+Lambda functions can be written in numerous programming languages (JavaScript,
 Python, Ruby, Java, Go, ...). Sentry is currently supporting automatic
-instrumentation of Lambda functions written in Javascript and Python.
+instrumentation of Lambda functions written in JavaScript and Python.
 
 See the [Sentry Documentation](https://docs.sentry.io/product/integrations/cloud-monitoring/) on how to set up serverless instrumentation.
 
@@ -29,7 +29,7 @@ like the Sentry SDK to your Lambda function.
 With the AWS Lambda Integrations users can add Sentry functionality to their
 Lambda function without changing the code of the Lambda function.
 
-Sentry is providing a Lambda Layer including the Javascript SDK (or Python
+Sentry is providing a Lambda Layer including the JavaScript SDK (or Python
 SDK).
 
 See the documentation to learn how customers can instrument their Lambda
@@ -42,7 +42,7 @@ Sentry is deploying one Lambda Layer for Node-based Lambda functions
 functions (`SentryPythonServerlessSDK`). Those Lambda layers are distributed
 to various AWS regions to be close to the users.
 
-Both these layers include the latest Sentry Javascript SDK (or Python SDK).
+Both these layers include the latest Sentry JavaScript SDK (or Python SDK).
 
 ### Building of the Python Layer
 
@@ -62,20 +62,20 @@ this can be found [here](https://github.com/getsentry/sentry-python/blob/master/
 To deploy a new version of the Lambda layer to AWS, you need to trigger a new
 release of the Python SDK.
 
-### Building of the Javascript/Node Layer
+### Building of the JavaScript/Node Layer
 
-The contents of the Layer directory for the Javascript/Node layer are built during the
+The contents of the Layer directory for the JavaScript/Node layer are built during the
 "Build & Test" workflow in Github actions. The steps necessary can be found
 [here](https://github.com/getsentry/sentry-javascript/blob/master/.github/workflows/build.yml).
 
 This will prepare the Lambda layer directory, compress everything and upload the resulting zip file as
 an artifact to GitHub.
 
-### Deployment of the Javascript/Node Layer
+### Deployment of the JavaScript/Node Layer
 
 The zip file prepared in the previous step will be deployed to AWS Lambda by
 [Craft](https://github.com/getsentry/craft). The configuration of craft for doing
 this can be found [here](https://github.com/getsentry/sentry-javascript/blob/master/.craft.yml).
 
 To deploy a new version of the Lambda layer to AWS, you need to trigger a new
-release of the Javascript SDK.
+release of the JavaScript SDK.

develop-docs/sdk/telemetry/traces/tracing-without-performance.mdx

@@ -22,7 +22,7 @@ This means that SDKs by default always:
 TwP is active by default if users don't specify sampling options that enable span collection and sending (i.e. [regular tracing](#enable-regular-tracing)).
 For example, the following trivial SDK setup (note the absence of sampling options) enables TwP:
 
-```JavaScript
+```javascript
 Sentry.init({
   dsn: "___PUBLIC_DSN___",
 });

docs/platforms/javascript/common/configuration/filtering.mdx

@@ -227,7 +227,7 @@ Learn more about <PlatformLink to="/configuration/sampling/">configuring the sam
 
 ## Filtering Spans
 
-Available since Javascript SDK version `8.2.0`.
+Available since JavaScript SDK version `8.2.0`.
 
 To prevent certain spans from being reported to Sentry, use the <PlatformIdentifier name="before-send-span" /> configuration option which allows you to provide a function to modify and drop a child span.
 This function is only called for child spans of the root span. If you want to modify or drop the root span, including its child spans, use [`beforeSendTransaction`](#using-beforesendtransaction) instead.

docs/platforms/javascript/common/configuration/integrations/inboundfilters.mdx

@@ -9,11 +9,11 @@ This integration is enabled by default. If you'd like to modify your default int
 
 This integration allows you to ignore specific errors based on the type, message, or URLs in a given exception.
 
-By default, it'll ignore errors that start with `Script error` or `Javascript error: Script error`.
+By default, it'll ignore errors that start with `Script error` or `JavaScript error: Script error`.
 
 To configure this integration, use the `ignoreErrors`, `ignoreTransactions`, `denyUrls`, and `allowUrls` SDK options directly. For example:
 
-```JavaScript
+```javascript
 Sentry.init({
   ignoreErrors: ["ignore-this-error"],
 });

docs/platforms/javascript/common/profiling/browser-profiling.mdx

@@ -80,4 +80,4 @@ What does Sentry's JavaScript browser profile offer that Chrome DevTools does no
 
 Please note, that since the browser profiling API is currently only implemented in Chromium-based browsers, the profiles collected with Sentry's JavaScript browser profiling will inherently be biased toward that demographic. This is something that you'll need to consider if you're basing your decisions on the data collected.
 
-We hope that as the Javascript browser profiling API gains adoption, other browsers will implement it as well. If you find the browser profiling feature helpful and would like to see it gain further adoption, please consider supporting the spec at the official WICG repository.
+We hope that as the JavaScript browser profiling API gains adoption, other browsers will implement it as well. If you find the browser profiling feature helpful and would like to see it gain further adoption, please consider supporting the spec at the official WICG repository.

docs/platforms/react-native/integrations/default.mdx

@@ -14,7 +14,7 @@ _Import name: `Sentry.inboundFiltersIntegration`_
 This integration allows you to ignore specific errors based on the type,
 message, or URLs in a given exception.
 
-By default, it'll ignore errors that start with `Script error` or `Javascript error: Script error`.
+By default, it'll ignore errors that start with `Script error` or `JavaScript error: Script error`.
 
 To configure this integration, use the `ignoreErrors`, `ignoreTransactions`, `denyUrls`,
 and `allowUrls` SDK options directly. Keep in mind that `denyURLs` and `allowURLs`

docs/platforms/react-native/manual-setup/native-init.mdx

@@ -35,7 +35,7 @@ you have to [configure the sample rate](/platforms/apple/tracing/#configure-the-
 
 <Alert>
 
-Initializing with this method uses a Content Provider. Because the Javascript engine for React Native is also initialized using a Content Provider, we cannot guarantee that Sentry will always initialize before the JavaScript engine.
+Initializing with this method uses a Content Provider. Because the JavaScript engine for React Native is also initialized using a Content Provider, we cannot guarantee that Sentry will always initialize before the JavaScript engine.
 
 </Alert>
 

docs/platforms/react-native/migration/before-v5.mdx

@@ -100,7 +100,7 @@ See the JS SDK migration guide [here](https://github.com/getsentry/sentry-javasc
 
 ## From 3.x to 4.x
 
-By bumping Sentry JavaScript to v7, new breaking changes were introduced, to learn more about what was changed, check out the [breaking changes changelog](https://github.com/getsentry/sentry-javascript/blob/7.0.0/CHANGELOG.md#breaking-changes) from Sentry Javascript.
+By bumping Sentry JavaScript to v7, new breaking changes were introduced, to learn more about what was changed, check out the [breaking changes changelog](https://github.com/getsentry/sentry-javascript/blob/7.0.0/CHANGELOG.md#breaking-changes) from Sentry JavaScript.
 
 By bumping Sentry Android to v6, new breaking changes were introduced, to learn more about what was changed, check out the [migration guide](/platforms/android/migration/#migrating-from-iosentrysentry-android-5x-to-iosentrysentry-android-600).
 

docs/platforms/react-native/sourcemaps/uploading/expo-advanced.mdx

@@ -154,7 +154,7 @@ npx sentry-cli sourcemaps upload \
 
 ## Manual Upload for JSC Release
 
-After the Sentry Expo Plugin and Sentry Metro plugin are added to the application configuration, generate and upload Javascript Core source maps.
+After the Sentry Expo Plugin and Sentry Metro plugin are added to the application configuration, generate and upload JavaScript Core source maps.
 
 ### Generate Bundle