update all ParamFields

Author: ethanpalm

authentication-personalization/personalization-setup.mdx

@@ -59,21 +59,24 @@ type User = {
 <ParamField
   path="expiresAt"
   type="number"
+  optional
 >
   Session expiration time in **seconds since epoch**. If the user loads a page after this time, their stored data is automatically deleted and they must reauthenticate.
   <Warning><b>For JWT handshakes:</b> This differs from the JWT's `exp` claim, which determines when a JWT is considered invalid. Set the JWT `exp` claim to a short duration (10 seconds or less) for security. Use `expiresAt` for the actual session length (hours to weeks).</Warning>
 </ParamField>
 <ParamField
   path="groups"
   type="string[]"
+  optional
 >
-  A list of groups that the user belongs to. Pages with a matching `groups` field in their metadata will be visible to this user.
+  List of groups the user belongs to. Pages with matching `groups` in their frontmatter are visible to this user.
 
   **Example**: User with `groups: ["admin", "engineering"]` can access pages tagged with either the `admin` or `engineering` groups.
 </ParamField>
 <ParamField
   path="content"
   type="object"
+  optional
 >
   Custom data accessible in your `MDX` content via the `user` variable. Use this for dynamic personalization throughout your documentation.
 
@@ -100,21 +103,22 @@ type User = {
   ```
 
   <Note>
-    The information in `user` is only available for logged-in users. For logged-out users, the value of `user` will be `{}`. To prevent the page from crashing for logged out users, always use optional chaining on your `user` fields. For example, `{user.org?.plan}`.
+    The information in `user` is only available for logged-in users. For logged-out users, the value of `user` will be `{}`. To prevent the page from crashing for logged-out users, always use optional chaining on your `user` fields. For example, `{user.org?.plan}`.
   </Note>
 </ParamField>
 <ParamField
   path="apiPlaygroundInputs"
   type="object"
+  optional
 >
-  User-specific values that will be prefilled in the API playground if supplied. Save users time when testing your APIs with their own data.
+  User-specific values that prefill API playground fields. Saves users time by auto-populating their data when testing APIs.
 
   **Example**:
   ```json
   {
-  "header": { "X-API-Key": "user_api_key_123" },
-  "server": { "subdomain": "foo" },
-  "query": { "org_id": "12345" }
+    "header": { "X-API-Key": "user_api_key_123" },
+    "server": { "subdomain": "foo" },
+    "query": { "org_id": "12345" }
   }
   ```
   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.