Apply suggestions from code review

Co-authored-by: Isabel <[email protected]>

Author: Lms24

src/platforms/javascript/common/configuration/tree-shaking/index.mdx

@@ -11,15 +11,15 @@ If you want to minimize the bundle size of the Sentry SDK, we recommend reading
 
 ## Tree Shaking Debug Code
 
-Sentry ships with code that enables you to debug your Sentry configuration, primarily through logging. While this code can be very useful in development environments, it's not typically necessary to include it in your production bundles where it takes up valuable space. The JavaScript SDK includes a special flag in its CommonJS and ESM distributions which can be used to facilitate tree shaking (removal) of such code during the build process.
+Sentry ships with code that enables you to debug your Sentry configuration, primarily through logging. While this code can be very useful in development environments, it's not typically necessary to include it in your production bundles, where it takes up valuable space. The JavaScript SDK includes a special flag in its CommonJS and ESM distributions which can be used to facilitate tree shaking (removal) of such code during the build process.
 
 To make debugging code eligible for tree shaking, you must replace the `__SENTRY_DEBUG__` flag in the Sentry SDK with `false`.
 
 <PlatformSection notSupported={["javascript.nextjs"]}>
 
 ### Tree Shaking Debug Code With Webpack
 
-To tree shake Sentry debug code in your webpack bundles, we recommend using webpack's [DefinePlugin](https://webpack.js.org/plugins/define-plugin/).
+To tree shake Sentry debug code in your webpack bundles, we recommend using webpack's [DefinePlugin](https://webpack.js.org/plugins/define-plugin/):
 
 ```javascript {filename:webpack.config.js}
 const webpack = require("webpack");
@@ -41,7 +41,7 @@ module.exports = {
 
 ### Tree Shaking Debug Code With Rollup
 
-If you're using `rollup.js`, we recommend using [Rollup's `replace` plugin](https://github.com/rollup/plugins/tree/master/packages/replace).
+If you're using `rollup.js`, we recommend using [Rollup's `replace` plugin](https://github.com/rollup/plugins/tree/master/packages/replace):
 
 ```javascript {filename:rollup.config.js}
 import replace from "@rollup/plugin-replace";
@@ -89,9 +89,9 @@ For more information on custom webpack configurations in Next.js, see [Custom We
 ## Tree Shaking Default Integrations
 
 By default, the Sentry SDK sets up a list of [default integrations](../integrations/default) that extend your
-SDK functionality. Furthermore, you can also add [additional](../integrations/plugin) or [custom](../integrations/custom)
+SDK functionality. You can also add [additional](../integrations/plugin) or [custom](../integrations/custom)
 integrations to your SDK configuration.
-In case you do not want to include default integrations in your config, you can [disable](../options/#integration-configuration)
+If you don't want to include default integrations in your config, you can [disable](../options/#integration-configuration)
 them and add your custom array of integrations.
 However, if you also want to tree shake the unused default integrations, you can do so by creating a `Client` yourself.
 By doing this, you essentially bypass `Sentry.init` which normally creates a `Client` for you.
@@ -126,5 +126,9 @@ const client = new BrowserClient({
 getCurrentHub().bindClient(client);
 ```
 
-Note that in contrast to `Sentry.init`, the `Client` constructor expects options of type `ClientOptions` instead of `Options`.
+<Note>
+
+In contrast to `Sentry.init`, the `Client` constructor expects options of type `ClientOptions` instead of `Options`.
 This means that the `ClientOptions.integrations` property is the final array of integrations that will be used.
+
+</Note>