Apply suggestions from code review

Co-authored-by: Sarah Mischinger <[email protected]>

Author: TkDodo

docs/platforms/javascript/guides/tanstackstart-react/index.mdx

@@ -110,7 +110,7 @@ export const getRouter = () => {
 
 ### Configure Server-side Sentry
 
-Create an instrument file `instrument.server.mjs` in the root of your project. In this file, initialize the Sentry SDK for your server.
+Create an instrument file `instrument.server.mjs` in the root of your project. In this file, initialize the Sentry SDK for your server:
 
 ```tsx {filename:instrument.server.mjs}
 import * as Sentry from "@sentry/tanstackstart-react";
@@ -140,9 +140,9 @@ Sentry.init({
 
 #### Moving the Sentry server config file for production usage
 
-For production monitoring, the Sentry server config file needs to be moved to your build output. Since [TanStack Start is designed to work with any hosting provider](https://tanstack.com/start/latest/docs/framework/react/guide/hosting), the exact location will depend on where your build artifacts are deployed (for example, `"/dist"`, `".output/server"` or a platform-specific directory).
+For production monitoring, you need to move the Sentry server config file to your build output. Since [TanStack Start is designed to work with any hosting provider](https://tanstack.com/start/latest/docs/framework/react/guide/hosting), the exact location will depend on where your build artifacts are deployed (for example, `"/dist"`, `".output/server"` or a platform-specific directory).
 
-For example, when using [nitro](https://nitro.build/), copy the instrumentation file to `".output/server"`.
+For example, when using [Nitro](https://nitro.build/), copy the instrumentation file to `".output/server"`:
 
 ```json {diff}  {filename:package.json}
 {