Fix grammar and typos in OTEL docs (vercel#48235)

I ran a grammar check on OTEL docs to get any remaining issues that
spell check didn't fix.

---------

Co-authored-by: Steven <steven@ceriously.com>

Author: jankaifer

.vscode/settings.json

@@ -71,8 +71,15 @@
   "cSpell.words": [
     "Entrypoints",
     "napi",
+    "nextjs",
     "opentelemetry",
     "Threadsafe",
     "zipkin"
+  ],
+  "grammarly.selectors": [
+    {
+      "language": "markdown",
+      "scheme": "file"
+    }
   ]
 }

docs/advanced-features/instrumentation.md

@@ -1,5 +1,5 @@
 ---
-description: Learn how to instrument your Next.js app.
+description: Learn how to use instrumentation to run code at server startup in your Next.js app
 ---
 
 > **Note**: This feature is experimental. To use it, you must explicitly opt in by defining `experimental.instrumentationHook = true;` in your `next.config.js`.
@@ -35,7 +35,7 @@ export const register() {
 
 By doing this, you can colocate all of your side effects in one place in your code, and avoid any unintended consequences from importing files.
 
-We call `register` in all environments, so it's necessary to conditionally require any code that doesn't support both `edge` and `nodejs`. You can use environment variable `NEXT_RUNTIME` to get the current environment. Importing environment specific code would look like this:
+We call `register` in all environments, so it's necessary to conditionally require any code that doesn't support both `edge` and `nodejs`. You can use the environment variable `NEXT_RUNTIME` to get the current environment. Importing an environment-specific code would look like this:
 
 ```ts
 // /instrumentation.ts

docs/advanced-features/open-telemetry.md

@@ -1,5 +1,5 @@
 ---
-description: Learn how instrument your Next.js app with OpenTelemetry.
+description: Learn how to instrument your Next.js app with OpenTelemetry.
 ---
 
 > **Note**: This feature is experimental, you need to explicitly opt-in by providing `experimental.instrumentationHook = true;` in your `next.config.js`.
@@ -11,13 +11,13 @@ Observability is crucial for understanding and optimizing the behavior and perfo
 As applications become more complex, it becomes increasingly difficult to identify and diagnose issues that may arise. By leveraging observability tools, such as logging and metrics, developers can gain insights into their application's behavior and identify areas for optimization. With observability, developers can proactively address issues before they become major problems and provide a better user experience. Therefore, it is highly recommended to use observability in your Next.js applications to improve performance, optimize resources, and enhance user experience.
 
 We recommend using OpenTelemetry for instrumenting your apps.
-It's a platform agnostic way to instrument apps that allows you to change your observability provider without changing your code.
+It's a platform-agnostic way to instrument apps that allows you to change your observability provider without changing your code.
 Read [Official OpenTelemetry docs](https://opentelemetry.io/docs/) for more information about OpenTelemetry and how it works.
 
 This documentation uses terms like _Span_, _Trace_ or _Exporter_ throughout this doc, all of which can be found in [the OpenTelemetry Observability Primer](https://opentelemetry.io/docs/concepts/observability-primer/).
 
-Next.js supports OpenTelemetry instrumentation out of the box, that means that we already instrumented Next.js itself.
-When you enable OpenTelemetry you we will automatically wrap all your code like `getStaticProps` in a _spans_ with helpful attributes.
+Next.js supports OpenTelemetry instrumentation out of the box, which means that we already instrumented Next.js itself.
+When you enable OpenTelemetry we will automatically wrap all your code like `getStaticProps` in _spans_ with helpful attributes.
 
 > **Note:** We currently support OpenTelemetry bindings only in serverless functions.
 > We don't provide any for `edge` or client side code.
@@ -61,7 +61,7 @@ npm install @opentelemetry/sdk-node @opentelemetry/resources @opentelemetry/sema
 ```
 
 Now you can initialize `NodeSDK` in your `instrumentation.ts`.
-OpenTelemetry APIs are not compatible with edge runtime, so you need to make sure that you are importing them only when `process.end.NEXT_RUNTIME === "nodejs"`. Conditionally importing with an `require` doesn't play well with typescript. We recommend using a conditionally `require`ing new file `instrumentation.node.ts` which can use normal `import`s:
+OpenTelemetry APIs are not compatible with edge runtime, so you need to make sure that you are importing them only when `process.env.NEXT_RUNTIME === 'nodejs'`. Conditionally importing with an `require` doesn't play well with typescript. We recommend using a conditionally `require`ing new file `instrumentation.node.ts` which can use normal `import`s:
 
 ```ts
 // instrumentation.ts
@@ -91,11 +91,11 @@ sdk.start()
 ```
 
 Doing this is equivalent to using `@vercel/otel`, but it's possible to modify and extend.
-For example you could use `@opentelemetry/exporter-trace-otlp-grpc` instead of `@opentelemetry/exporter-trace-otlp-http`.
+For example, you could use `@opentelemetry/exporter-trace-otlp-grpc` instead of `@opentelemetry/exporter-trace-otlp-http`.
 
 ## Testing your instrumentation
 
-You need a OpenTelemetry collector with a compatible backend to test OpenTelemetry traces locally.
+You need an OpenTelemetry collector with a compatible backend to test OpenTelemetry traces locally.
 We recommend using our [OpenTelemetry dev environment](https://github.com/vercel/opentelemetry-collector-dev-setup).
 
 If everything works well you should be able to see the root server span labeled as `GET /requested/pathname`.
@@ -132,7 +132,7 @@ If that is not possible on your platform, you can use a custom OpenTelemetry exp
 
 ## Custom Spans
 
-You can add your own span with [OpenTelemetry APIs](https://opentelemetry.io/docs/instrumentation/js/instrumentation).
+You can add a custom span with [OpenTelemetry APIs](https://opentelemetry.io/docs/instrumentation/js/instrumentation).
 
 ```bash
 npm install @opentelemetry/api
@@ -166,12 +166,12 @@ Next.js automatically instruments several spans for you to provide useful insigh
 Attributes on spans follow [OpenTelemetry semantic conventions](https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/). We also add some custom attributes under the `next` namespace:
 
 - `next.span_name` - duplicates span name
-- `next.span_type` - each span type has unique identifier
+- `next.span_type` - each span type has a unique identifier
 - `next.route` - The route pattern of the request (e.g., `/[param]/user`).
 - `next.page`
   - This is an internal value used by an app router.
   - You can think about it as a route to a special file (like `page.ts`, `layout.ts`, `loading.ts` and others)
-  - It can be used as an unique identifier only when paired with `next.route` because `/layout` can be used to identify both `/(groupA)/layout.ts` and `/(groupB)/layout.ts`
+  - It can be used as a unique identifier only when paired with `next.route` because `/layout` can be used to identify both `/(groupA)/layout.ts` and `/(groupB)/layout.ts`
 
 ### `[http.method] [next.route]`
 
@@ -195,7 +195,7 @@ Attributes:
 
 - `next.span_type`: `AppRender.getBodyResult`.
 
-This span represents the process of rendering a route in app router.
+This span represents the process of rendering a route in the app router.
 
 Attributes:
 
@@ -224,7 +224,7 @@ Attributes:
 
 - `next.span_type`: `AppRouteRouteHandlers.runHandler`.
 
-This span represents the execution of an API route handler in app router.
+This span represents the execution of an API route handler in the app router.
 
 Attributes:
 
@@ -272,7 +272,7 @@ Attributes:
 
 - `next.span_type`: `ResolveMetadata.generateMetadata`.
 
-This span represents the process of generating metadata for a specific page (single route can have multiple of these spans).
+This span represents the process of generating metadata for a specific page (a single route can have multiple of these spans).
 
 Attributes: