copyedit sending data

Author: ethanpalm

authentication-personalization/sending-data.mdx

@@ -44,12 +44,12 @@ type User = {
   Custom data accessible in your `MDX` content via the `user` variable. Use this for dynamic personalization throughout your documentation.
 
   **Example**:
-  ```JSON
+  ```json
   { "firstName": "Ronan", "company": "Acme Corp", "plan": "Enterprise" }
   ```
 
   **Usage in `MDX`**:
-  ```MDX
+  ```mdx
   Welcome back, {user.firstName}! Your {user.plan} plan includes...
   ```
   With the example `user` data, this would render as: Welcome back, Ronan! Your Enterprise plan includes...
@@ -70,7 +70,7 @@ type User = {
   ```
   If a user makes requests at a specific subdomain, you can send `{ server: { subdomain: 'foo' } }` as an `apiPlaygroundInputs` field. This value will be prefilled on any API page with the `subdomain` value.
 
-  <Note>The`header`, `query`, and `cookie` fields will only prefill if they are part of your [OpenAPI security scheme](https://swagger.io/docs/specification/authentication/). If a field is in either the `Authorization` or `Server` sections, it will prefill. Creating a standard header parameter named `Authorization` will not enable this feature.</Note>
+  <Note>The `header`, `query`, and `cookie` fields will only prefill if they are part of your [OpenAPI security scheme](https://swagger.io/docs/specification/authentication/). If a field is in either the `Authorization` or `Server` sections, it will prefill. Creating a standard header parameter named `Authorization` will not enable this feature.</Note>
 </ParamField>
 
 ## Example user data